We’re excited to announce the public preview of the new App Service quota self-service experience, designed to give you more visibility, control, and flexibility when managing your App Service resources in Azure.
Updated Oct 30, 2025
Version 6.0Can I get list of all providers covered under microsoft quota (Micrososft.Capacity) api
Microsoft does not publish a clean, official static list of all providers covered by the Microsoft Quota (Capacity) API.
The only reliable source is discovery via the API itself.
That said, there is a well-known, practical list of providers that actually work with Az.Quota today.
These providers expose quotas via Microsoft.Capacity and work with Az.Quota.
| Resource Provider | Notes |
|---|---|
| Microsoft.Compute | vCPUs, VM family quotas, regional cores |
| Microsoft.Network | Public IPs, NAT gateways (limited) |
| Microsoft.Storage | Storage account limits (partial) |
| Resource Provider | Reality Check |
|---|---|
| Microsoft.ContainerService | AKS node VM quotas (via Compute) |
| Microsoft.MachineLearningServices | ML compute quotas (select SKUs) |
| Microsoft.Batch | Batch cores |
| Microsoft.HDInsight | Cluster cores (region dependent) |
| Microsoft.Databricks | Backed by Compute quotas |
| Microsoft.SqlVirtualMachine | Uses Compute quotas |
These do NOT work with Az.Quota:
| Provider | Why |
|---|---|
| Microsoft.Web | App Service = SKU-based |
| Microsoft.Sql | DTU / vCore limits = service-managed |
| Microsoft.DocumentDB | RU/s limits = account-level |
| Microsoft.ServiceBus | SKU constrained |
| Microsoft.EventHub | Throughput units |
| Microsoft.KeyVault | Soft service limits |
| Microsoft.CognitiveServices | Per-SKU throttles |
| Microsoft.ContainerRegistry | SKU-based |
| Microsoft.ApiManagement | SKU-based |