Skip to content

Azure/azure-rest-api-specs

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date
Oct 2, 2024
May 25, 2024
Jan 14, 2025
Jan 6, 2025
Oct 23, 2024
Aug 1, 2024
Dec 12, 2024
Jan 10, 2025
Nov 17, 2021
Sep 18, 2021
Nov 1, 2023
Jan 17, 2025
May 31, 2019
Aug 8, 2023
Dec 10, 2024
Jun 6, 2024
Oct 3, 2024
Sep 7, 2023
Nov 13, 2023
Feb 6, 2017
Apr 8, 2024
May 19, 2022
Oct 2, 2024
Jan 14, 2025
Dec 18, 2024
Jan 9, 2025
Jan 8, 2025
Oct 9, 2024
Jan 24, 2024

Repository files navigation

Azure REST API Specifications

Description

This repository is the canonical source for REST API specifications for Microsoft Azure. You can learn more about it here.

Getting started

If you're a Microsoft employee looking for information about all of the repositories and steps for Azure SDK Libraries Releases, go to the aka.ms/azsdk/join.

External Contributors can read Getting Started with OpenAPI Specifications.

Terminology

  • Offerings, Skus, and Features - These are distinct entities represented in Eco Manager and Service Tree. While the Offering/Sku/Feature entities and hierarchy represent the externally marketed product, service/components entities in service tree represent corresponding engineering entities that together power these external products. Refer to Product Taxonomy for details.

  • Resource Provider - When a service onboards new functionality onto ARM, it is required to complete Resource Provider Registration. For existing Resource Provider to Service Mapping, refer to Match resource provider to service*

Directory Structure

See aka.ms/azsdk/spec-dirs.

Next steps

The next step in the process after a spec is completed is to generate SDKs and API reference documentation. If you're a Microsoft employee, go to the Azure SDK - Internal Wiki for more information.

External Contributors can read Getting Started with OpenAPI Specifications.


This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.