touchups

v-thepet · v-thepet · commit 3b238ea6d88d · 2025-03-31T15:17:03.000-07:00
diff --git a/articles/devtest-labs/devtest-lab-create-template.md b/articles/devtest-labs/devtest-lab-create-template.md
@@ -23,7 +23,7 @@ In this article, you learn how to create an Azure DevTest Labs virtual machine (
 
 ## Create the custom image
 
-To create a custom image for DevTest Labs from a VHD or VHDX file, follow these steps:
+To create a custom image for DevTest Labs from a VHD file, follow these steps:
 
 1. In the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040), go to the lab that has the uploaded VHD file.
 1. On the lab **Overview** page, select **Configuration and policies** in the left navigation.
diff --git a/articles/devtest-labs/devtest-lab-set-lab-policy.md b/articles/devtest-labs/devtest-lab-set-lab-policy.md
@@ -52,7 +52,7 @@ This policy limits the VM sizes that users can create in the lab. The default po
 <a name="set-virtual-machines-per-user"></a>
 ### Virtual machines per user
 
-This policy specifies the maximum number of VMs and VMs using premium disks that an individual lab user can claim or create. The default policy setting is **Off**.
+These two policies specify the maximum number of VMs and VMs using premium disks that an individual lab user can claim or create. The default setting for both policies is **Off**.
 
 1. On the lab's **Configuration and policies** page, select **Virtual machines per user** from the left navigation.
 1. On the **Virtual machines per user** page, under **Limit the number of virtual machines**, select **On** or **Off** to enable or disable the policy.
@@ -69,7 +69,7 @@ If a user tries to create or claim a VM after the user limit is met, an error me
 
 ### Virtual machines per lab
 
-This policy specifies the maximum number of VMs that all users can create in the current lab. The default policy setting is **Off**.
+These two policies specify the maximum number of VMs and VMs using premium disks that all users can create in the current lab. The default setting for both policies is **Off**.
 
 1. On the lab's **Configuration and policies** page, select **Virtual machines per lab** from the left navigation.
 1. On the **Virtual machines per lab** page, under **Limit the number of virtual machines**, select **On** or **Off** to enable or disable the policy.
@@ -80,7 +80,7 @@ This policy specifies the maximum number of VMs that all users can create in the
 
 :::image type="content" source="./media/devtest-lab-set-lab-policy/max-vms-per-lab.png" alt-text="Screenshot showing VMs per lab.":::
 
-If a user tries to create or claim a VM after the lab limit is met, an error message indicates that the VM can't be created or claimed.
+If a user tries to create a VM after the lab limit is met, an error message indicates that the VM can't be created.
 
 <a name="set-auto-shutdown"></a>
 ### Autoshutdown
@@ -96,7 +96,7 @@ Autoshutdown helps minimize lab waste by shutting down lab VMs at a specific tim
 
 :::image type="content" source="./media/devtest-lab-set-lab-policy/auto-shutdown.png" alt-text="Screenshot showing Auto shutdown.":::
 
-By default, autoshutdown applies to all lab VMs. If allowed by [autoshutdown policy](#autoshutdown-policy), lab users can override lab autoshutdown settings for their own individual lab VMs as follows:
+By default, the autoshutdown schedule applies to all lab VMs. If allowed by [autoshutdown policy](#autoshutdown-policy), lab users can override lab autoshutdown settings for their own individual VMs. To set a shutdown schedule for an individual VM:
 
 1. Select the VM from **My virtual machines** on the lab **Overview** page.
 1. On the home page for the VM, select **Auto-shutdown** from the **Operations** section of the left navigation.
@@ -109,7 +109,7 @@ For more information about autoshutdown and sending notifications, see [Configur
 Autostart policy helps you minimize waste by specifying a specific time of day and days of the week to start up lab VMs. The default policy setting is **No**.
 
 > [!IMPORTANT]
-> This policy isn't automatically applied to lab VMs. To apply this setting to VMs, open the VM's page and change its **Auto-start** setting.
+> This policy isn't automatically applied to lab VMs. To apply this setting to individual VMs, open the VM's page and change its **Auto-start** setting.
 
 1. On the lab's **Configuration and policies** page, select **Auto-start** from the left navigation.
 1. Select **Yes** or **No** to enable or disable the policy.
@@ -131,8 +131,8 @@ If you set an autoshutdown schedule for lab VMs, you can also set a policy to le
 1. On the lab's **Configuration and policies** page, select **Auto shutdown policy** from the left navigation.
 1. Select one of the following options:
 
-   - **User sets a schedule and can opt out**: Lab users can override or opt out of lab autoshutdown. Lab users can override the lab schedule times, and they don't have to set any autoshutdown for their VMs. This setting is the default.
-   - **User sets a schedule and cannot opt out**: Lab users can override the lab shutdown schedule for their VMs, but they can't opt out of autoshutdown. This option ensures that every VM in the lab is on some autoshutdown schedule.
+   - **User sets a schedule and can opt out**: Lab users can override or opt out of lab autoshutdown. Lab users can override the lab autoshutdown schedule time, or set no autoshutdown for their VMs. This setting is the default.
+   - **User sets a schedule and cannot opt out**: Lab users can set the shutdown time for their own VMs, but they can't opt out of autoshutdown entirely. This option ensures that every VM in the lab is on some autoshutdown schedule.
    - **User has no control over the schedule set by lab administrator**: Lab users can't override or opt out of the lab autoshutdown schedule. They can set up autoshutdown notifications for their own VMs.
 
 1. Select **Save**.
diff --git a/articles/devtest-labs/media/devtest-lab-set-lab-policy/configuration-policies-menu.png b/articles/devtest-labs/media/devtest-lab-set-lab-policy/configuration-policies-menu.png
diff --git a/articles/devtest-labs/samples-powershell.md b/articles/devtest-labs/samples-powershell.md
@@ -1,6 +1,6 @@
 ---
 title: Azure PowerShell Samples
-description: Use these Azure PowerShell scripts to do DevTest Labs activities like adding lab users, creating custom lab roles, and allowing specific lab VM sizes and Marketplace images.
+description: Use these Azure PowerShell scripts for DevTest Labs activities like adding users, creating custom roles, and setting lab policies.
 ms.topic: sample
 ms.custom: devx-track-azurepowershell, UpdateFrequency2
 ms.author: rosemalcolm
@@ -37,7 +37,7 @@ To use the script, replace the parameter values under the `# Values to change` c
 This script uses the following commands:
 
 - [Get-AzADUser](/powershell/module/az.resources/get-azaduser): Gets the user object from Microsoft Entra ID.
-- [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment): Assigns the specified role to the specified user at the specified scope.
+- [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment): Assigns the **DevTest Labs User** role to the specified user at the specified scope.
 
 ```powershell
 # Values to change
@@ -67,7 +67,7 @@ This script uses the following commands:
 
 - [Get-AzProviderOperation](/powershell/module/az.resources/get-azprovideroperation): Lists all the available operations for the `Microsoft.DevTestLab` resource provider.
 - [Get-AzRoleDefinition](/powershell/module/az.resources/get-azroledefinition): Lists all the allowed actions for the **DevTest Labs User** role.
-- [New-AzRoleDefinition](/powershell/module/az.resources/new-azroledefinition): Creates the new custom role.
+- [New-AzRoleDefinition](/powershell/module/az.resources/new-azroledefinition): Creates the new **Policy Contributor** custom role.
 - [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment): Assigns the custom role to the specified user at the specified scope.
 
 ```powershell
@@ -359,15 +359,15 @@ Set-PolicyChanges $lab $policyChanges
 
 ## Create a custom image from a VHD file
 
-This sample PowerShell script creates a custom image in DevTest Labs from a VHD file. This script requires a Windows VHD file uploaded to the lab's Azure Storage account, and uses a deployment template from the public [DevTest Labs template repository](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd).
+This sample PowerShell script creates a DevTest Labs custom image from a VHD file by using a deployment template from the public [DevTest Labs template repository](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates/201-dtl-create-customimage-from-vhd). This script requires a Windows VHD file uploaded to the lab's Azure Storage account.
 
 To use the script, replace the parameter values under the `# Values to change` comment with your own values. You can get the `subscriptionId`, `labRg`, and `labName` values from the lab's main page in the Azure portal. Get the `vhdUri` value from the Azure Storage container where you uploaded the VHD file.
 
 This script uses the following commands:
 
 - [Get-AzResource](/powershell/module/az.resources/get-azresource): Gets the lab and lab storage account resources.
 - [Get-AzStorageAccountKey](/powershell/module/az.storage/get-azstorageaccountkey): Gets the access keys for the lab storage account.
-- [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment): Deploys the custom image and resource group based on a template.
+- [New-AzResourceGroupDeployment](/powershell/module/az.resources/new-azresourcegroupdeployment): Deploys the custom image and resource group based on the template.
 
 ```powershell
 # Values to change
diff --git a/articles/devtest-labs/tutorial-use-custom-lab.md b/articles/devtest-labs/tutorial-use-custom-lab.md
@@ -10,9 +10,9 @@ ms.custom: UpdateFrequency2
 #customer intent: As a lab user, I want to be able to claim ownership and connect to lab VMs, so I can use preconfigured VMs to do my work.
 ---
 
-# Access, claim, and connect to a DevTest labs VM
+# Access, claim, and connect to a DevTest Labs VM
 
-When you create a virtual machine (VM) in Azure DevTest labs, you automatically own the VM. You can connect to the VM and see it listed in **My VMs** on the Azure portal lab page.
+When you create a virtual machine (VM) in Azure DevTest Labs, you automatically own the VM. You can connect to the VM and see it listed in **My VMs** on the Azure portal lab page.
 
 As a lab user, you can also claim ownership of existing claimable lab VMs. Once you claim a VM, you see it listed in **My VMs** and can connect to and manage it as your own VM.
 
