Merge pull request #66442 from jborsecnik/resource-group-control

ShawnJackson · web-flow · commit 8e5c3bd1c767 · 2019-02-21T14:14:07.000-06:00
edit pass: resource-group-control
diff --git a/articles/lab-services/resource-group-control.md b/articles/lab-services/resource-group-control.md
@@ -17,32 +17,33 @@ ms.author: spelluru
 ---
 
 # Specify a resource group for lab virtual machines in Azure DevTest Labs
-As a lab owner, you can configure your lab virtual machines to be created in a specific resource group. This feature helps you in the following scenarios: 
+
+As a lab owner, you can configure your lab virtual machines to be created in a specific resource group. This feature helps you in the following scenarios:
 
 - Have fewer resource groups created by labs in your subscription.
-- Have your labs operate within a fixed set of resource groups configured by you
+- Have your labs operate within a fixed set of resource groups that you configure.
 - Work around restrictions and approvals required for creating resource groups within your Azure subscription.
-- Consolidate all your lab resources within a single resource group to simplify tracking those resources and applying [policies](../governance/policy/overview.md) to manage them at the resource group level.
+- Consolidate all your lab resources within a single resource group to simplify tracking those resources and applying [policies](../governance/policy/overview.md) to manage resources at the resource group level.
 
-With this feature, you can use a script to specify a new or an existing resource group within your Azure subscription for all your lab VMs. Currently, DevTest Labs supports this feature through an API. 
+With this feature, you can use a script to specify a new or existing resource group within your Azure subscription for all your lab VMs. Currently, Azure DevTest Labs supports this feature through an API.
 
-## API to configure a resource group for lab virtual machines
-Now let’s walk through the options you have as a lab owner while using this API: 
+## API to configure a resource group for lab VMs
+You have the following options as a lab owner when using this API:
 
-- You can choose the **lab’s resource group** for all virtual machines.
-- You can choose an **existing resource group** other than the lab's resource group for all virtual machines.
-- You can enter a **new resource group** name for all virtual machines.
-- You can continue with the existing behavior, that is, a resource group is created for each VM in the lab.
+- Choose the **lab’s resource group** for all virtual machines.
+- Choose an **existing resource group** other than the lab's resource group for all virtual machines.
+- Enter a **new resource group** name for all virtual machines.
+- Continue using the existing behavior, in which a resource group is created for each VM in the lab.
  
-This setting applies to new virtual machines created in the lab. The older VMs in your lab that were created in their own resource groups continue to remain unaffected. Environments created in your lab continue to remain in their own resource groups.
+This setting applies to new virtual machines created in the lab. The older VMs in your lab that were created in their own resource groups remain unaffected. Environments that are created in your lab continue to remain in their own resource groups.
 
-### How to use this API:
-- Use the API version **2018_10_15_preview** while using this API. 
-- If you specify a new resource group, ensure that you have **write permissions on resource groups** within your subscription. Without write permissions, creating new virtual machines in the specified resource group result in a failure. 
-- While using the API, pass in the **full resource group ID**. For example: `/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>`. Ensure that the resource group is in the same subscription as that of the lab. 
+How to use this API:
+- Use API version **2018_10_15_preview**.
+- If you specify a new resource group, ensure that you have **write permissions on resource groups** in your subscription. If you lack write permissions, creating new virtual machines in the specified resource group will fail.
+- While using the API, pass in the **full resource group ID**. For example: `/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>`. Ensure that the resource group is in the same subscription as the lab. 
 
 ## Use PowerShell 
-Following example describes how to create all lab virtual machines in a new resource group using a PowerShell script.
+The following example shows how to use a PowerShell script to create all lab virtual machines in a new resource group.
 
 ```PowerShell
 [CmdletBinding()]
@@ -66,14 +67,14 @@ az resource update -g $labRg -n $labName --resource-type "Microsoft.DevTestLab/l
 "Done. New virtual machines will now be created in the resource group '$vmRg'."
 ```
 
-Invoke the script using the following command (ResourceGroup.ps1 is the file that contains the preceding script): 
+Invoke the script by using the following command. ResourceGroup.ps1 is the file that contains the preceding script:
 
 ```PowerShell
 .\ResourceGroup.ps1 -subId <subscriptionID> -labRg <labRGNAme> -labName <LanName> -vmRg <RGName> 
 ```
 
-## Use Azure Resource Manager template
-If you are using Azure Resource Manager template to create a lab, use the **vmCreationResourceGroupId** property in the lab properties section of your Resource Manager template as shown in the following example:
+## Use an Azure Resource Manager template
+If you're using an Azure Resource Manager template to create a lab, use the **vmCreationResourceGroupId** property in the lab properties section of your template, as shown in the following example:
 
 ```json
         {
