Increasing CORE quota limits in Azure

Updated to reflect the new workflow - 11/23/2017
Please click on the individual pics below to load up a clearer view of the pic.

I had this ask on how to increase the default quota limits on Azure and I wanted to capture the basic flow using the new portal. The following talks about increasing CORE limits of VMs. The default for a subscription is 20. While we are here submitting a ticket for increasing CORE count of a subscription, increasing other limits is very similar and can be done by creating a similar ticket, though you will have to choose the correct resource type for which you want to increase the quota. Overall it is a very simple and straightforward process to submit a request and have the quota increase request granted. Note that increasing quota limits does not automatically mean you will be billed extra. It is only a soft limit that is being reset, and you will only be billed for actual usage. So you should have peace of mind increasing core counts.

Go to your portal and do either of the following to get to the blade where you can request Quota increases.

(a) Go to your subscription blade and click on Usage + Quotas as shown below OR use the method (b) shown below

(b) click on Help+Support->New Support Request -> Request Type (look at the bread crumbs at the top to see the navigational hierarchy)


Then click on Basic and on the "Issue Type" click on “Quotas” and then choose the subscription for which you want to change the quota. Note that customers usually have multiple subscriptions. So select the appropriate subscription where you want the quota increase.

Since we are talking about increasing "CORES" for Virtual Machines, pick that in the drop down for "Quota Type". As you can see below there are different types in this drop down. So be sure to pick the appropriate "Quota type".




Choose the resource type where you want to increase the QUOTA


NOTE:   If your VM instance sizes are going to go over and above the current subscription limit, you will see them as "Not Available" in the new portal (ie So you should check your current core quotas against the actual number of cores you are using. Another quirk is that if you are  using Azure Resource Manager (ARM), then the quota numbers are per region instead of subscription. So be aware if you are planning to use ARM based deployments and needed to increase the core counts, then you also have to factor the regions in which you are doing the deployment and request quota changes across the regions you are needing to deploy.

Follow the screen shots and fill up the rest. This should generate a support ticket (see the very last screen shot) and also generate an e-mail to you.


This will generate a support ticket and a support engineer will contact you based on priority and after making a few checks usually increase your quotas' soft limits. It is actually a simple and straightforward process.

Additional Reference: Troubleshooting and listing quotas using PowerShell or Azure CLI