Skip to content

Commit 1f2f39f

Browse files
committed
Incorporated feedback from Nicole.
1 parent 2751bbd commit 1f2f39f

File tree

3 files changed

+7
-5
lines changed

3 files changed

+7
-5
lines changed

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -78,10 +78,9 @@ Calculate the total number of cores for each size group.
7878
Remember that the total number of cores is the existing cores and the new cores you're requesting.
7979

8080
## Best practices for requesting a core limit increase
81-
[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
82-
83-
For example, you may need to carry more capacity than you actually need for a single session to allow for a short overlap period between sessions. Often you need to keep the previous session's labs available to allow students to finish incomplete work. However, we don't recommend that you make the full capacity request immediately, instead break it into separate requests starting with the immediate session's needs. Later, you can request the capacity you need for the period between sessions.
81+
Verify the capacity available in your subscription by [determining the current usage and quota](./how-to-determine-your-quota-usage.md).
8482

83+
[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
8584

8685
## Start a new support request
8786
You can follow these steps to request a core limit increase:

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,7 @@ The time that it takes to assign capacity varies depending on the VM size, regio
1010

1111
- Request capacity as far in advance as possible.
1212
- If possible, be flexible on the region where you're requesting capacity.
13-
- Capacity remains assigned for the lifetime of a subscription. You only need to request extra capacity if you need more than is already assigned to your subscription.
13+
- Capacity remains assigned for the lifetime of a subscription. When lab plans or labs are deleted, the capacity remains assigned to the subscription.
14+
- You only need to request extra capacity if you need more than is already assigned to your subscription.
15+
- You should not have to go through the process of requesting extra capacity often.
1416
- Make incremental requests for VM cores rather than making large, bulk requests. Breaking requests for large numbers of cores into smaller requests gives extra flexibility in how those requests are fulfilled.

articles/lab-services/migrate-to-2022-update.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,8 @@ As a customer, you're now assigned your own [dedicated VM cores quota](/azure/la
6666
### Tips for requesting a capacity increase
6767

6868
[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
69-
- For example, when you move from lab accounts to lab plans, you should first request sufficient capacity to set up a few representative labs that serve as a proof-of-concept. Later, you can make additional capacity requests based on your upcoming lab needs.
69+
70+
For example, when you move from lab accounts to lab plans, you should first request sufficient capacity to set up a few representative labs that serve as a proof-of-concept. Later, you can make additional capacity requests based on your upcoming lab needs.
7071

7172

7273
## 3. Configure shared resources

0 commit comments

Comments
 (0)