Skip to content

Commit bb52e24

Browse files
committed
fixing paths
1 parent d675de7 commit bb52e24

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machines/quotas.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.author: cynthn
1818
The vCPU quotas for virtual machines and virtual machine 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. Any time 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 either of those quotas are exceeded, the VM deployment will not 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.
1919

2020
> [!NOTE]
21-
> 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-portal/supportability/regional-quota-requests.md) or delete VMs that are no longer needed.
21+
> 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-portal/supportability/regional-quota-requests.md) or delete VMs that are no longer needed.
2222
2323

2424
## Check usage
@@ -116,8 +116,8 @@ Premium Storage Managed Disks 1 10000 Count
116116
## Reserved VM Instances
117117
Reserved VM Instances, which are 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. This will cause Azure to 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.
118118

119-
If a quota increase is required to either purchase a Single Subscription RI, you can [request a quota increase](../../azure-portal/supportability/regional-quota-requests.md) on your subscription.
119+
If a quota increase is required to either purchase a Single Subscription RI, you can [request a quota increase](../azure-portal/supportability/regional-quota-requests.md) on your subscription.
120120

121121
## Next steps
122122

123-
For more information about billing and quotas, see [Azure subscription and service limits, quotas, and constraints](../../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/billing/TOC.json).
123+
For more information about billing and quotas, see [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/billing/TOC.json).

0 commit comments

Comments
 (0)