back to home

Azure / azure-rest-api-specs

The source for REST API specifications for Microsoft Azure.

3,035 stars
5,671 forks
3,607 issues
TypeSpecTypeScriptPowerShell

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing Azure/azure-rest-api-specs in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/Azure/azure-rest-api-specs)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

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. Examples These examples provide a starting point for how a library should be structured, as well as the expected options that libraries should use: • Data plane: https://aka.ms/azsdk/tspconfig-sample-dpg • Management plane (ARM): https://aka.ms/azsdk/tspconfig-sample-mpg 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 opencode@microsoft.com with any additional questions or comments._