Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This document lists some of the most common Microsoft Azure limits, which are also sometimes called quotas.
- To learn more about Azure pricing, see the Azure pricing overview and details page.
- The Azure pricing page provides details for specific services; for example, Windows Virtual Machines.
- You can also use the Azure pricing calculator to estimate your costs.
- See What is Microsoft Billing? for tips to help manage your costs.
How to manage limits
Note
Some services have adjustable limits.
When the limit can be adjusted, the tables include Default limit and Maximum limit headers. The limit can be raised above the default limit but not above the maximum limit. Some services with adjustable limits use different headers with information about adjusting the limit.
When a service doesn't have adjustable limits, the following tables use the header Limit without any additional information about adjusting the limit. In those cases, the default and the maximum limits are the same.
If you want to raise the limit or quota above the default limit, open an online customer support request at no charge.
The terms soft limit and hard limit are often used informally to describe the current, adjustable limit (soft limit) and the maximum limit (hard limit). If a limit isn't adjustable, there won't be a soft limit but only a hard limit.
Free Azure trial subscriptions aren't eligible for limit or quota increases. If you have this type of subscription, you can upgrade to a Pay-as-you-go one. For more information, see Upgrade your Azure account and the overviews for Try Azure for free or pay as you go.
Some limits are managed at a regional level. You decide what your quotas must be for your workload in any one region, and then request that amount for each region into which you want to deploy.
For example, with virtual central processing unit (vCPU) quotas:
- To request a quota increase with support for vCPUs, you decide how many vCPUs to use in which regions.
- You then request an increase in vCPU quotas for the amounts and regions that you want.
- If you need to use 30 vCPUs in West Europe to run your application there, you specifically request 30 vCPUs in West Europe.
- Your vCPU quota doesn't increase in any other region; only West Europe has the 30-vCPU quota.
See Resolve errors for resource quotas for more information about how to determine quotas for specific regions.
General limits
- See Naming rules and restrictions for Azure resources for limits on resource names.
- See Understand how Azure Resource Manager throttles requests to learn about Resource Manager API read and write limits.
Azure management group limits
The following limits apply to Azure management groups.
| Resource | Limit |
|---|---|
| Management groups per Microsoft Entra tenant | 10,000 |
| Subscriptions per management group | Unlimited. |
| Levels of management group hierarchy | Root level plus 6 levels1 |
| Direct parent management group per management group | One |
| Management group level deployments per location | 8002 |
| Locations of Management group level deployments | 10 |
| Deployments per management group in the deployment history | 8003 |
1The 6 levels don't include the subscription level.
2If you reach the limit of 800 deployments, delete deployments from the history that are no longer needed. To delete management group level deployments, use Remove-AzManagementGroupDeployment or az deployment mg delete.
3Deployments are automatically deleted from the history as you near the limit. Deleting an entry from the deployment history doesn't affect the deployed resources. For more information, see Automatic deletions from deployment history.
Azure subscription limits
The following limits apply when you use Azure Resource Manager and Azure resource groups.
| Resource | Limit |
|---|---|
| Azure subscriptions associated with a Microsoft Entra tenant | Unlimited |
| Coadministrators per subscription | Unlimited |
| Resource groups per subscription | 980 |
| Azure Resource Manager API request size | 4,194,304 bytes |
| Tags per subscription1 | 50 |
| Unique tag calculations per subscription2 | 80,000 |
| Subscription-level deployments per location | 8003 |
| Locations of Subscription-level deployments | 10 |
1You can apply up to 50 tags directly to a subscription. Within the subscription, each resource or resource group is also limited to 50 tags. However, the subscription can contain an unlimited number of tags that are dispersed across resources and resource groups.
2Resource Manager returns a list of tag name and values in the subscription only when the number of unique tags is 80,000 or less. A unique tag is defined by the combination of resource ID, tag name, and tag value. For example, two resources with the same tag name and value would be calculated as two unique tags. You still can find a resource by tag when the number exceeds 80,000.
3Deployments are automatically deleted from the history as you near the limit. For more information, see Automatic deletions from deployment history.
Note that subscription IDs must be non-empty GUIDs.
Azure resource group limits
| Resource | Limit |
|---|---|
| Resources per resource group | Resources aren't limited by resource group. Instead, they're limited by resource type in a resource group. See next row. |
| Resources per resource group, per resource type | 800 - Some resource types can exceed the 800 limit. See Resources not limited to 800 instances per resource group. |
| Deployments per resource group in the deployment history | 8001 |
| Resources per deployment | 800 |
| Management locks per unique scope | 20 |
| Number of tags per resource or resource group | 50 |
| Tag key length | 512 |
| Tag value length | 256 |
1Deployments are automatically deleted from the history as you near the limit. Deleting an entry from the deployment history doesn't affect the deployed resources. For more information, see Automatic deletions from deployment history.
Template limits
| Value | Limit |
|---|---|
| Parameters | 256 |
| Variables | 256 |
| Resources (including copy count) | 800 |
| Outputs | 64 |
| Template expression | 24,576 chars |
| Resources in exported templates | 200 |
| Template size | 4 MB |
| Resource definition size | 1 MB |
| Parameter file size | 4 MB |
You can exceed some template limits by using a nested template. For more information, see Use linked templates when you deploy Azure resources. To reduce the number of parameters, variables, or outputs, you can combine several values into an object. For more information, see Objects as parameters.
You may get an error with a template or parameter file of less than 4 MB, if the total size of the request is too large. For more information about how to simplify your template to avoid a large request, see Resolve errors for job size exceeded.
Azure API Center limits
| Resource | Free plan1 | Standard plan2 |
|---|---|---|
| APIs | 200 | 10,000 |
| Versions per API | 5 | 100 |
| Definitions per version | 5 | 5 |
| Deployments per API | 10 | 10 |
| Environments | 20 | 20 |
| Workspaces | 1 (Default) | 1 (Default) |
| Custom metadata properties per entity3 | 10 | 20 |
| Child properties in custom metadata property of type "object" | 10 | 10 |
| Requests per minute (data plane) | 3,000 | 6,000 |
| API definitions analyzed | 10 | 2,0004 |
| Analysis profiles | 1 | 3 |
| Linked (integrated) API sources5 | 1 | 5 |
| APIs synchronized from a linked API source | 200 | 2,0004 |
| Dependencies | 200 | 200 |
| Semantic search in API Center portal | No | Yes |
1 Use of full service features including API analysis is limited.
2 To increase a limit in the Standard plan, contact support.
3 Custom metadata properties assigned to APIs, deployments, and environments.
4 Process can take a few minutes to up to 24 hours to complete.
5 Sources such as linked API Management instances.
Azure API Management limits
This section provides information about limits that apply to Azure API Management instances in different service tiers, including the following:
- Resource limits in API Management classic and v2 tiers
- Resource limits in API Management workspaces
- Resource limits in developer portal in API Management v2 tiers
- Gateway runtime limits
Limits - API Management classic and v2 tiers
The following limits are introduced starting March 2026. Services in the classic tiers that surpass the revised limits are allowed to keep their existing capacity. For more information, see Understanding API Management service limits.
Note
Limits are per service instance unless stated otherwise.
When counting the number of API-related resources (such as API operations and tags), API Management also includes API versions and revisions.
| Entity/Resource | Consumption | Developer | Basic/ Basic v2 |
Standard/ Standard v2 |
Premium/ Premium v2 |
|---|---|---|---|---|---|
| API operations | 3,000 | 3,000 | 10,000 | 50,000 | 75,000 |
| API tags | 1,500 | 1,500 | 1,500 | 2,500 | 15,000 |
| Named values | 5,000 | 5,000 | 5,000 | 10,000 | 18,000 |
| Loggers | 100 | 100 | 100 | 200 | 400 |
| Products | 100 | 100 | 200 | 500 | 2,000 |
| Subscriptions | N/A | 10,000 | 15,000 | 25,000 | 75,000 |
| Users | N/A | 20,000 | 20,000 | 50,000 | 75,000 |
| User-assigned managed identities | 10 | 10 | 10 | 10 | 10 |
| Workspaces per workspace gateway | N/A | N/A | 301 | 301 | 30 |
| Self-hosted gateways | N/A | 5 | N/A | N/A | 1002 |
1 Currently applies to v2 tiers only.
2 Applies to Premium tier only.
Limits - API Management workspaces
The following are resource limits per workspace in Azure API Management:
| Resource | Workspace - Premium tier |
|---|---|
| Workspaces per instance | 100 |
| Scale units per premium workspace gateway | 12 |
| APIs (including versions and revisions) | 200 |
| API operations | 5,000 |
| Operations per API | 100 |
| Releases per API | 100 |
| Schemas per API | 100 |
| Subscriptions per API | 200 |
| Tags per API | 100 |
| Backends | 200 |
| Certificates | 200 |
| Groups | 50 |
| Loggers | 50 |
| Named values | 200 |
| Policy fragments | 50 |
| Products | 100 |
| APIs per product | 200 |
| Groups per product | 200 |
| Subscriptions per product | 1,000 |
| Tags per product | 50 |
| Schemas | 500 |
| Subscriptions | 5,000 |
| Tags | 200 |
| Groups per user | 200 |
| Version sets | 50 |
Limits - Developer portal in API Management v2 tiers
| Item | Basic v2 | Standard v2 | Premium v2 |
|---|---|---|---|
| Number of media files to upload | 15 | 15 | 15 |
| Size of a media file | 500 KB | 500 KB | 500 KB |
| Number of pages | 30 | 50 |