Resolve errors for resource quotas

This article describes quota errors you may encounter when deploying resources.


This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. For Az module installation instructions, see Install Azure PowerShell.


If you deploy a template that creates resources that exceed your Azure quotas, you get a deployment error that looks like:

Message=Operation results in exceeding quota limits of Core.
Maximum allowed: 4, Current in use: 4, Additional requested: 2.

Or, you may see:

Message=Creating the resource of type <resource-type> would exceed the quota of <number>
resources of type <resource-type> per resource group. The current resource count is <number>,
please delete some resources of this type before creating a new one.


Quotas are applied per resource group, subscriptions, accounts, and other scopes. For example, your subscription may be configured to limit the number of cores for a region. If you attempt to deploy a virtual machine with more cores than the permitted amount, you receive an error stating the quota has been exceeded. For complete quota information, see Azure subscription and service limits, quotas, and constraints.


Azure CLI

For Azure CLI, use the az vm list-usage command to find virtual machine quotas.

az vm list-usage --location "South Central US"

Which returns:

    "currentValue": 0,
    "limit": 2000,
    "name": {
      "localizedValue": "Availability Sets",
      "value": "availabilitySets"


For PowerShell, use the Get-AzVMUsage command to find virtual machine quotas.

Get-AzVMUsage -Location "South Central US"

Which returns:

Name                             Current Value Limit  Unit
----                             ------------- -----  ----
Availability Sets                            0  2000 Count
Total Regional Cores                         0   100 Count
Virtual Machines                             0 10000 Count


To request a quota increase, go to the portal and file a support issue. In the support issue, request an increase in your quota for the region into which you want to deploy.


Remember that for resource groups, the quota is for each individual region, not for the entire subscription. If you need to deploy 30 cores in West US, you have to ask for 30 Resource Manager cores in West US. If you need to deploy 30 cores in any of the regions to which you have access, you should ask for 30 Resource Manager cores in all regions.

  1. Select Subscriptions.


  2. Select the subscription that needs an increased quota.

    Select subscription

  3. Select Usage + quotas

    Select usage and quotas

  4. In the upper right corner, select Request increase.

    Request increase

  5. Fill in the forms for the type of quota you need to increase.

    Fill in form