Currently, the Compute quota alerts look at the total available quota for a particular family/region but disregard the Total Regional vCPUs. This creates the false impression that VMS can be deployed, and Azure inaccurately throws errors when trying to provision VMS.
Showing the total Regional vCpus an admin can easily track not only a particular VM size but the overall Azure Allowance available within a region.
The example below, shows that an admin can provision UP to 353 VCPUS of a particular size within East US. However, it errors out when trying to provision a VM with the message: “Error: Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 50, Current Usage: 50, Additional Required: 4, (Minimum) New Limit Required: 54.” The error message shows because the region in its totally can only fulfill 50 vCPUs .
Comments (1 comment)