Azure subscription and service limits, quotas, and constraints

If you want to raise the limit or quota above the Default Limitopen an online customer support request at no charge. The limits can’t be raised above the Maximum Limit value shown in the following tables. If there is no Maximum Limit column, then the resource doesn’t have adjustable limits.

It is now possible to combine multiple Azure resources in to a single Azure Resource Group. When using Resource Groups, limits that once were global become managed at a regional level with the Azure Resource Manager. For more information about Azure Resource Groups, see Azure Resource Manager overview.

It is important to emphasize that quotas for resources in Azure Resource Groups are per-region accessible by your subscription, and are not per-subscription, as the service management quotas are. Let’s use vCPU quotas as an example. If you need to request a quota increase with support for vCPUs, you need to decide how many vCPUs you want to use in which regions, and then make a specific request for Azure Resource Group vCPU quotas for the amounts and regions that you want. Therefore, if you need to use 30 vCPUs in West Europe to run your application there, you should specifically request 30 vCPUs in West Europe. But you will not have a vCPU quota increase in any other region — only West Europe will have the 30-vCPU quota.

As a result, you may find it useful to consider deciding what your Azure Resource Group quotas need to be for your workload in any one region, and request that amount in each region into which you are considering deployment. See troubleshooting deployment issues for more help discovering your current quotas for specific regions.

For a comprehensive list of service-specific limits, you must check the following Microsoft article: https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits

About The Author