Proposed Pull Request Change

title description author ms.service ms.subservice ms.topic ms.date ms.author
vCPU quotas Check your vCPU quotas for Azure virtual-machines. cynthn azure-virtual-machines sizes how-to 01/16/2026 cynthn
📄 Document Links
GitHub View on GitHub Microsoft Learn View on Microsoft Learn
Content Truncation Detected
The generated rewrite appears to be incomplete.
Original lines: -
Output lines: -
Ratio: -
Raw New Markdown
Generating updated version of doc...
Rendered New Markdown
Generating updated version of doc...
+0 -0
+0 -0
--- title: vCPU quotas description: Check your vCPU quotas for Azure virtual-machines. author: cynthn ms.service: azure-virtual-machines ms.subservice: sizes ms.topic: how-to ms.date: 01/16/2026 ms.author: cynthn # Customer intent: "As a cloud infrastructure administrator, I want to monitor my vCPU quotas for virtual machines, so that I can ensure successful deployments without exceeding resource limits." --- # Check vCPU quotas **Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets The vCPU quotas for virtual machines and scale sets are arranged in two tiers for each subscription, in each region. The first tier is the Total Regional vCPUs, and the second tier is the various VM size family cores such as the D-series vCPUs. Anytime a new VM is deployed the vCPUs for the VM must not exceed the vCPU quota for the VM size family or the total regional vCPU quota. If you exceed either of those quotas, the VM deployment won't be allowed. There is also a quota for the overall number of virtual machines in the region. The details on each of these quotas can be seen in the **Usage + quotas** section of the **Subscription** page in the [Azure portal](https://portal.azure.com), or you can query for the values using the Azure CLI. > [!NOTE] > Quota is calculated based on the total number of cores in use both allocated and deallocated. If you need additional cores, [request a quota increase](/azure/azure-portal/supportability/regional-quota-requests) or delete VMs that are no longer needed. ## Check usage ### [CLI](#tab/cli) You can check your quota usage using [az vm list-usage](/cli/azure/vm). ```azurecli-interactive az vm list-usage --location "Central US" -o table ``` The output should look something like this: ``` Name CurrentValue Limit -------------------------------- -------------- ------- Availability Sets 0 2000 Total Regional vCPUs 29 100 Virtual Machines 7 10000 Virtual Machine Scale Sets 0 2000 Standard DSv3 Family vCPUs 8 100 Standard DSv2 Family vCPUs 3 100 Standard Dv3 Family vCPUs 2 100 Standard D Family vCPUs 8 100 Standard Dv2 Family vCPUs 8 100 Basic A Family vCPUs 0 100 Standard A0-A7 Family vCPUs 0 100 Standard A8-A11 Family vCPUs 0 100 Standard DS Family vCPUs 0 100 Standard G Family vCPUs 0 100 Standard GS Family vCPUs 0 100 Standard F Family vCPUs 0 100 Standard FS Family vCPUs 0 100 Standard Storage Managed Disks 5 10000 Premium Storage Managed Disks 5 10000 ... ``` ### [PowerShell](#tab/powershell) You can use the [Get-AzVMUsage](/powershell/module/az.compute/get-azvmusage) cmdlet to check on your quota usage. ```azurepowershell-interactive Get-AzVMUsage -Location "Central US" ``` The output looks similar to this: ``` Name Current Value Limit Unit ---- ------------- ----- ---- Availability Sets 0 2000 Count Total Regional vCPUs 4 260 Count Virtual Machines 4 10000 Count Virtual Machine Scale Sets 1 2000 Count Standard B Family vCPUs 1 10 Count Standard DSv2 Family vCPUs 1 100 Count Standard Dv2 Family vCPUs 2 100 Count Basic A Family vCPUs 0 100 Count Standard A0-A7 Family vCPUs 0 250 Count Standard A8-A11 Family vCPUs 0 100 Count Standard D Family vCPUs 0 100 Count Standard G Family vCPUs 0 100 Count Standard DS Family vCPUs 0 100 Count Standard GS Family vCPUs 0 100 Count Standard F Family vCPUs 0 100 Count Standard FS Family vCPUs 0 100 Count Standard NV Family vCPUs 0 24 Count Standard NC Family vCPUs 0 48 Count Standard H Family vCPUs 0 8 Count Standard Av2 Family vCPUs 0 100 Count Standard LS Family vCPUs 0 100 Count Standard Dv2 Promo Family vCPUs 0 100 Count Standard DSv2 Promo Family vCPUs 0 100 Count Standard MS Family vCPUs 0 0 Count Standard Dv3 Family vCPUs 0 100 Count Standard DSv3 Family vCPUs 0 100 Count Standard Ev3 Family vCPUs 0 100 Count Standard ESv3 Family vCPUs 0 100 Count Standard FSv2 Family vCPUs 0 100 Count Standard ND Family vCPUs 0 0 Count Standard NCv2 Family vCPUs 0 0 Count Standard NCv3 Family vCPUs 0 0 Count Standard LSv2 Family vCPUs 0 0 Count Standard Storage Managed Disks 2 10000 Count Premium Storage Managed Disks 1 10000 Count ... ``` --- ## Reserved VM Instances Reserved VM Instances, scoped to a single subscription without VM size flexibility, will add a new aspect to the vCPU quotas. These values describe the number of instances of the stated size that must be deployable in the subscription. They work as a placeholder in the quota system to ensure that quota is reserved to ensure Azure reservations are deployable in the subscription. For example, if a specific subscription has 10 Standard_D1 reservations the usages limit for Standard_D1 reservations will be 10. Azure will ensure that there are always at least 10 vCPUs available in the Total Regional vCPUs quota to be used for Standard_D1 instances and there are at least 10 vCPUs available in the Standard D Family vCPU quota to be used for Standard_D1 instances. If a quota increase is required to either purchase a Single Subscription RI, you can [request a quota increase](/azure/azure-portal/supportability/regional-quota-requests) on your subscription. ## Related content For more information about billing and quotas, see [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/billing/TOC.json).
Success! Branch created successfully. Create Pull Request on GitHub
Error: