Skip to content

Commit 12fd372

Browse files
committed
Fixing flow and typos
1 parent f7a73d8 commit 12fd372

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

articles/lab-services/how-to-request-capacity-increase.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,9 @@ To create a support request, you must be assigned to one of the following roles
2222
- [Contributor](../role-based-access-control/built-in-roles.md)
2323
- [Support Request Contributor](../role-based-access-control/built-in-roles.md)
2424

25+
26+
### Verify available capacity
27+
Before you begin calculating the number of extra cores you require, verify the capacity available in your subscription by [determining the current usage and quota](./how-to-determine-your-quota-usage.md). You'll be able to see exactly where your current capacity is used, and may discover extra capacity in an unused lab plan or lab.
2528
### Determine the regions for your labs
2629
Azure Lab Services resources can exist in many regions. You can choose to deploy resources in multiple regions close to your students. For more information about Azure regions, how they relate to global geographies, and which services are available in each region, see [Azure global infrastructure](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
2730

@@ -78,10 +81,10 @@ Calculate the total number of cores for each size group.
7881
Remember that the total number of cores is the existing cores and the new cores you're requesting.
7982

8083
## Best practices for requesting a core limit increase
81-
Verify the capacity available in your subscription by [determining the current usage and quota](./how-to-determine-your-quota-usage.md).
8284

8385
[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
8486

87+
8588
## Start a new support request
8689
You can follow these steps to request a core limit increase:
8790

articles/lab-services/includes/lab-services-request-capacity-best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ ms.author: RoseHJM
66
ms.date: 12/01/2022
77
---
88

9-
The time it takes to assign capacity varies depending on the VM size, region, and number of cores requested. You shouldn't have to go through the process of requesting extra capacity often, but to ensure you have the resources you require when you need them, you should:
9+
The time it takes to assign capacity varies depending on the VM size, region, and number of cores requested. You won't have to go through the process of requesting extra capacity often, but to ensure you have the resources you require when you need them, you should:
1010

1111
- Request capacity as far in advance as possible.
1212
- If possible, be flexible on the region where you're requesting capacity.
1313
- Recognize that capacity remains assigned for the lifetime of a subscription. When lab plans or labs are deleted, the capacity remains assigned to the subscription.
14-
- Request extra capacity only if you need more than is already assigned to your subscription.
14+
- Request extra capacity only if you need more than is already assigned to your subscription.
1515
- Make incremental requests for VM cores rather than making large, bulk requests. Break requests for large numbers of cores into smaller requests for extra flexibility in how those requests are fulfilled.

0 commit comments

Comments
 (0)