Skip to content

Commit 80fd2d3

Browse files
authored
Merge pull request #90292 from v-thpra/1607434-fix-typo
US1607434-Fix typo for Loc
2 parents d6169e6 + 52bec8c commit 80fd2d3

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

articles/azure-supportability/classic-deployment-model-quota-increase-requests.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,15 @@ ms.assetid: ce37c848-ddd9-46ab-978e-6a1445728a3b
1212

1313
# Classic Deployment Model
1414

15-
Classic deployment model is the older generation Azure deployment mode land enforces a global vCPU quota limit for virtual machines and virtual machine scale sets. Classic deployment model is not recommended anymore and is now superseded by Resource Manager model. To learn more about these two deployment models and advantage of Resource Manager refer to Resource Manager Deployment Model page.
16-
When a new subscription is created, a default quota of vCPUs is assigned to it. Anytime a new VM is to be deployed using Classic deployment model, the sum of new and existing vCPUs usage across all regions must not exceed the vCPU quota approved for the Classic deployment model.
17-
Learn more about quotas on [Azure subscription and service limits page](https://aka.ms/quotalimits)
15+
The Classic deployment model is the older generation Azure deployment model. It enforces a global vCPU quota limit for virtual machines and virtual machine scale sets. The Classic deployment model is no longer recommended, and is now superseded by the Resource Manager model.
1816

19-
You can request an increase in vCPUs limit for Classic deployment model via Help + Support blade or the Usages + Quota blade in the portal.
17+
To learn more about these two deployment models and the advantages of using Resource Manager, refer to the [Resource Manager and classic deployment](../azure-resource-manager/resource-manager-deployment-model.md) page.
18+
19+
When a new subscription is created, a default quota of vCPUs is assigned to it. Anytime a new VM is to be deployed using the Classic deployment model, the sum of new and existing vCPU usage across all regions must not exceed the vCPU quota approved for the Classic deployment model.
20+
21+
Learn more about quotas on the [Azure subscription and service limits](https://aka.ms/quotalimits) page.
22+
23+
You can request an increase in the vCPU quota limit for the Classic deployment model via the 'Help + Support' blade or the 'Usages + Quota' blade in the portal.
2024

2125
## Request per VM Series vCPU quota increase at subscription level using the **Help + Support** blade
2226

0 commit comments

Comments
 (0)