Merge pull request #220161 from RoseHJM/azlab-tips-for-requesting-capacity

Capacity request best practices - includes file

Author: JamesJBarnett

articles/lab-services/capacity-limits.md

@@ -40,6 +40,9 @@ Azure Lab Services hosts lab resources, including VMs, within special Microsoft-
 
 Before you set up a large number of VMs across your labs, we recommend that you open a support ticket to pre-request VM capacity. Requests should include VM size, number, and location. Requesting capacity before lab creation helps us to ensure that you create your labs in a region that has a sufficient number of VM cores for the VM size that you need for your labs.
 
+## Best practices for requesting a limit increase
+[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
+
 ## Next steps
 
 See the following articles:

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

@@ -22,6 +22,9 @@ To create a support request, you must be assigned to one of the following roles
  - [Contributor](../role-based-access-control/built-in-roles.md)
  - [Support Request Contributor](../role-based-access-control/built-in-roles.md)
 
+
+### Verify available capacity
+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.
 ### Determine the regions for your labs
 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/).
 
@@ -75,7 +78,12 @@ Calculate the total number of cores for each size group.
 
      :::image type="content" source="./media/how-to-request-capacity-increase/total-cores-grouped.png" alt-text="Screenshot showing the total number of cores in each group.":::
 
-Remember that the total number of cores is the existing cores and the new cores you are requesting.
+Remember that the total number of cores is the existing cores and the new cores you're requesting.
+
+## Best practices for requesting a core limit increase
+
+[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
+
 
 ## Start a new support request
 You can follow these steps to request a core limit increase:  

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

@@ -0,0 +1,15 @@
+---
+ms.service: lab-services
+ms.topic: include
+author: rosemalcolm
+ms.author: RoseHJM
+ms.date: 12/01/2022
+---
+
+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:
+
+- Request capacity as far in advance as possible.
+- If possible, be flexible on the region where you're requesting capacity.
+- 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. 
+- Request extra capacity only if you need more than is already assigned to your subscription. 
+- 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.

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

@@ -10,7 +10,7 @@ ms.date: 11/30/2022
 
 # Transition from lab accounts to the improved Azure Lab Services August 2022 Update 
 
-This article applies to users of Azure Lab Services with labs created with a lab account. If you are a brand new user to Azure Lab Services, start with [create a lab plan](tutorial-setup-lab-plan.md).
+This article applies to users of Azure Lab Services with labs created with a lab account. If you're a brand new user to Azure Lab Services, start with [create a lab plan](tutorial-setup-lab-plan.md).
 
 In this article, you'll learn the sequence to getting started using the features and resources made available beginning in the August 2022 update. The important update to Azure Lab Services August 2022 includes enhancements that boost performance, reliability, and scalability. It also gives you more flexibility in the way you manage labs, use capacity, and track costs. 
 
@@ -19,7 +19,7 @@ In this article, you'll learn the sequence to getting started using the features
 
 ## What's different in the update?
 
-A big part of the August 2022 update is centered around the fact that the concept *lab plans* replaces *lab accounts* in the August 2022 Update.  Although similar in functionality, there are some fundamental differences between the two concepts. The lab plan serves as a collection of configurations and settings that apply to the labs created from it. Also since the August 2022 update, a lab is an Azure resource in its own right and a sibling resource to lab plans.  You can read more about the differences between [lab plans and lab accounts](./lab-services-whats-new.md#lab-plans-replace-lab-accounts).
+A significant part of the August 2022 update is centered around the fact that the concept *lab plans* replaces *lab accounts* in the August 2022 Update.  Although similar in functionality, there are some fundamental differences between the two concepts. The lab plan serves as a collection of configurations and settings that apply to the labs created from it. Also since the August 2022 update, a lab is an Azure resource in its own right and a sibling resource to lab plans.  You can read more about the differences between [lab plans and lab accounts](./lab-services-whats-new.md#lab-plans-replace-lab-accounts).
 
 If you're moving from the current version of Azure Lab Services to the August 2022 Update, there's likely to be a time when you're using both your existing lab accounts and using the newer lab plans. And that's ok as both are still supported, can coexist in your Azure subscription, and can even share the same external resources.
 
@@ -63,15 +63,12 @@ As a customer, you're now assigned your own [dedicated VM cores quota](/azure/la
 1. [Request a core limit increase](/azure/lab-services/how-to-request-capacity-increase?tabs=Labplans).
 1. If you created a temporary lab plan, you can delete it at this point.  Deleting lab plans has no impact on your subscription or the capacity you have available. Capacity is assigned to your subscription.
 
-#### Tips for requesting capacity
+### Tips for requesting a capacity increase
 
-The time that it takes to assign capacity varies depending on the VM size, region, and number of cores requested. To ensure you have the resources you require when you need them, you should:
+[!INCLUDE [lab-services-request-capacity-best-practices](includes/lab-services-request-capacity-best-practices.md)]
 
-- Request capacity as far in advance as possible.
-- 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.
-  - 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.
-- If possible, be flexible on the region where you're requesting capacity.
-- 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.
+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.
+ 
 
 ## 3. Configure shared resources  
 
@@ -109,8 +106,8 @@ Each of the VM sizes has been remapped to use a newer [Azure VM Compute SKU](/az
 
 ## 6. Create and publish labs
 
-Once you have capacity assigned to your subscription, you can [create and publish](/azure/lab-services/tutorial-setup-lab) representative labs to validate the educator and student experience. Creating representative labs is an optional but highly recommended step, which enables you to validate performance based on common student workloads. 
-
+Once you have capacity assigned to your subscription, you can [create and publish](/azure/lab-services/tutorial-setup-lab) representative labs to validate the educator and student experience. 
+Creating a selection of representative labs as a proof of concept is an optional but highly recommended step, which enables you to validate performance based on common student workloads. After a successful proof of concept is completed, you can submit capacity requests based on your immediate upcoming need, building incrementally to your full capacity requirement over time. 
 ### Lab strategies
 
 You cannot migrate existing labs to the August 2022 Update. Instead, you must create new labs. Along with all the new enhancements, the requirement to create new labs provides a good opportunity to revisit your overall lab structure and plan changes where necessary.