Today is not the first time I have come across this issue, but I’m going to make sure it’s the last time I google how to find out the limits applied to an Azure subscription!
By default, different VM soft limits apply to different types of subscriptions. If you come across this issue, your error will look something like this:
New-AzureRmVM : Operation results in exceeding quota limits of Core. Maximum allowed: 10, Current in use: 10
From memory (this may not be correct), the limits are as follows for different subscription types:
- Pay as you go – 10 cores per VM type / region
- CSP – 30 cores per VM type / region
- VL – 20 cores per VM type / region
- EA – I’m not sure!
If you want to see how many cores you are allowed by default, you need to login to Azure Powershell and run the following command, substituting your region.
Get-AzureRMVMUsage -Location "West Europe"
This will give you an output similar to below:
PS C:\WINDOWS\system32> Get-AzureRmVMUsage -Location "West Europe" Name Current Value Limit Unit ---- ------------- ----- ---- Availability Sets 3 2000 Count Total Regional Cores 10 10 Count Virtual Machines 8 10000 Count Virtual Machine Scale Sets 0 2000 Count Standard Av2 Family Cores 10 10 Count Basic A Family Cores 0 10 Count Standard A0-A7 Family Cores 0 10 Count Standard A8-A11 Family Cores 0 10 Count Standard D Family Cores 0 10 Count Standard Dv2 Family Cores 0 10 Count Standard G Family Cores 0 10 Count Standard DS Family Cores 0 10 Count Standard DSv2 Family Cores 0 10 Count Standard GS Family Cores 0 10 Count Standard F Family Cores 0 10 Count Standard FS Family Cores 0 10 Count Standard NV Family Cores 0 12 Count Standard NC Family Cores 0 12 Count Standard H Family Cores 0 8 Count Standard LS Family Cores 0 10 Count
As you can see, for each region there is a subset of machine types. If you need to raise a core limit, you need to raise an Azure support ticket and request an increase for the required region and VM type. This does not cost anything and from my experience is usually done within 24 hours.
Hopefully this helps some folk out there who come across this issue. If you haven’t seen this yet and are planning an Azure rollout, it would be worth requesting this increase prior to starting your project!
Advertisements
