touchups

v-thepet · v-thepet · commit 02c9653478a9 · 2025-03-19T19:05:44.000-07:00
diff --git a/articles/devtest-labs/devtest-lab-add-vm.md b/articles/devtest-labs/devtest-lab-add-vm.md
@@ -4,7 +4,7 @@ description: Learn how to use the Azure portal to add a virtual machine (VM) to
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.custom: UpdateFrequency2
 
 #customer intent: As a lab user, I want to learn how to create VMs in DevTest Labs so I can use my lab VMs for developing, testing, or training.
@@ -36,7 +36,7 @@ This article describes how to create Azure virtual machines (VMs) in Azure DevTe
    - **Use a saved secret**: Select this checkbox to use a secret from Azure Key Vault instead of a password to access the VM. If you select this option, under **Secret**, select the secret to use from the dropdown list. For more information, see [Store secrets in a key vault](devtest-lab-store-secrets-in-key-vault.md). 
    - **Password**: If you don't use a secret, enter a VM password between 8 and 123 characters long.
    - **Save as default password**: Select this checkbox to save the password in the Key Vault associated with the lab.
-   - **Virtual machine size**: Keep the default value for the base, or select **Change Size** to select a different size. For more information about default VM sizes, see [VM sizes](#vm-sizes).
+   - **Virtual machine size**: Keep the default value for the base, or select **Change Size** to select a different size. For more information about default VM sizes, see [Default VM sizes](#vm-sizes).
    - **Allow hibernation**: Select this option to enable hibernation for the virtual machine.
      >[!NOTE]
      >If you enable hibernation, you must also select **Public IP** in **Advanced Settings**. **Private** and **Shared** IPs aren't supported if hibernation is enabled.
@@ -45,7 +45,7 @@ This article describes how to create Azure virtual machines (VMs) in Azure DevTe
 
    :::image type="content" source="./media/devtest-lab-add-vm/portal-lab-vm-basic-settings.png" alt-text="Screenshot that shows the VM Basic Settings page.":::
 
-### VM sizes
+### Default VM sizes
 
 The default **Virtual machine size** that appears in **Basic Settings** depends on the chosen **Image Base** architecture and the lab's **Allowed virtual machine** sizes policy setting. For more information, see [Set allowed virtual machine sizes](devtest-lab-set-lab-policy.md#set-allowed-virtual-machine-sizes).
 
@@ -61,12 +61,14 @@ If the lab's **Configuration and policies** > **Allowed virtual machine sizes**
   - If no 4-core nonpremium CPU size is available, the first available 4-core CPU size is selected.
   - If no 4-core CPU size is available, the first available CPU size is selected.
 
-<a name="add-artifacts-during-installation"></a>
 <a name="add-optional-artifacts"></a>
+<a name="add-artifacts-during-installation"></a>
 <a name="add-artifacts-after-installation"></a>
 ## Add artifacts
 
-Artifacts are tools, actions, or software you can add to lab VMs during or after VM creation. You can add artifacts to VMs from the [DevTest Labs public artifact repository](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts), or from private artifact repositories connected to the lab.
+Artifacts are tools, actions, or software you can optionally add to lab VMs. You can add artifacts to VMs from the [DevTest Labs public artifact repository](https://github.com/Azure/azure-devtestlab/tree/master/Artifacts), or from private artifact repositories connected to the lab. For more information about adding artifacts, see [Add artifacts to DevTest Labs VMs](add-artifact-vm.md).
+
+You can add artifacts to VMs before or after VM creation. To add artifacts after VM creation, see [Add artifacts to VMs after creation](add-artifact-vm.md#add-artifacts-to-vms-from-the-azure-portal).
 
 To add or configure artifacts during VM creation:
 
@@ -80,10 +82,8 @@ To add or configure artifacts during VM creation:
 
 1. When you're done adding artifacts, select **OK** on the **Add artifacts** page.
 
-To add artifacts to VMs after VM creation, see [Add artifacts to VMs after creation](add-artifact-vm.md#add-artifacts-to-vms-from-the-azure-portal). For more information about adding artifacts, see [Add artifacts to DevTest Labs VMs](add-artifact-vm.md).
-
 <a name="configure-optional-advanced-settings"></a>
-## Configure advanced settings
+## Configure other settings
 
 1. Optionally, select the **Advanced Settings** tab on the **Create lab resource** screen, and change any of the following values:
 
@@ -97,9 +97,9 @@ To add artifacts to VMs after VM creation, see [Add artifacts to VMs after creat
 
    :::image type="content" source="./media/devtest-lab-add-vm/portal-lab-vm-advanced-settings.png" alt-text="Screenshot that shows the VM Advanced Settings page.":::
 
-1. You can also optionally select the **Tags** tab to apply tags to the VM.
+1. Optionally, select the **Tags** tab to apply tags to the VM.
 
-## Complete the VM deployment
+## Complete VM deployment
 
 After you configure all settings, select **Create** at the bottom of the screen. During VM deployment, you can select the **Notifications** icon at the top of the screen to see progress. Creating a VM takes a while.
 
@@ -111,15 +111,15 @@ Or, if you chose **Make this machine claimable** during VM creation, select **Cl
 
 When you create a VM in DevTest Labs, you automatically have permission to access that VM, and you can see the VM listed both on the lab **Overview** page and the **All resources** page.
 
-DevTest Labs users in the **Owner** and **Contributor** roles can see all lab VMs on the lab's **All Resources** page. Users in the **DevTest Labs User** role can't automatically access VM resources that other users created, so they don't see those VMs on the **All resources** page.
+DevTest Labs users in the **Owner** and **Contributor** roles can see all lab VMs on the lab's **All Resources** page. Users in the **DevTest Labs User** role can't access other users' VM resources by default, so they don't automatically see those VMs on the **All resources** page.
 
 ## Copy existing Azure VMs into a lab
 
 You can copy existing Azure VMs to DevTest Labs as follows:
 
 1. Use a [PowerShell script](https://github.com/Azure/azure-devtestlab/blob/master/samples/DevTestLabs/Scripts/CopyVirtualMachines/CopyAzVHDFromVMToLab.ps1) to copy your existing VM's virtual hard disk (VHD) file to the lab.
 1. Use the VHD file to [create a custom image](devtest-lab-create-template.md) in your lab.
-1. [Create a lab VM]((add-vm-use-shared-image.md) from your custom image.
+1. [Create a lab VM](add-vm-use-shared-image.md) from your custom image.
 
 ## Related content
 
diff --git a/articles/devtest-labs/devtest-lab-attach-detach-data-disk.md b/articles/devtest-labs/devtest-lab-attach-detach-data-disk.md
@@ -4,15 +4,15 @@ description: Learn how to use the Azure portal to attach or detach a data disk f
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.custom: UpdateFrequency2
 
 #customer intent: As a lab user, I want to attach and detach data disks for my DevTest Labs VMs so I can manage storage or software separately from individual VMs.
 ---
 
 # Attach or detach a data disk for a lab VM in Azure DevTest Labs
 
-This article explains how to attach and detach a lab virtual machine (VM) data disk in Azure DevTest Labs by using the Azure portal. Depending on VM size, you can create, attach, detach, and reattach multiple [data disks](/azure/virtual-machines/managed-disks-overview). Data disks let you manage storage or software separately from individual VMs.
+This article explains how to attach and detach a lab virtual machine (VM) data disk in Azure DevTest Labs by using the Azure portal. Depending on the VM size, you can create, attach, detach, and reattach multiple [data disks](/azure/virtual-machines/managed-disks-overview). Data disks let you manage storage or software separately from individual VMs.
 
 ## Prerequisites
 
@@ -92,7 +92,7 @@ You can also detach or delete a data disk by using the lab's **Overview** page.
 
    :::image type="content" source="./media/devtest-lab-attach-detach-data-disk/devtest-lab-detach-data-disk.png" alt-text="Screenshot of detaching a data disk from the listing's context menu.":::
 
-To delete a detached data disk, select **Delete** from the context menu on the **My data disks** page, or select **Delete** on the disk's page. Deleting a data disk removes it from storage. You can reattach the disk only by readding it as a new disk.
+To delete a detached data disk, select **Delete** from the context menu on the **My data disks** page, or select **Delete** on the disk's page. Deleting a data disk removes it from storage. If you want to attach the disk again, you must add it as a new disk.
 
 ## Related content
 
diff --git a/articles/devtest-labs/devtest-lab-concepts.md b/articles/devtest-labs/devtest-lab-concepts.md
@@ -4,7 +4,7 @@ description: Learn about some basic Azure DevTest Labs concepts related to labs,
 ms.topic: conceptual
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.custom: UpdateFrequency2
 
 #customer intent: As a lab user or administrator, I want to understand basic DevTest Labs concepts so I can manage or use labs, VMs, and environments.
@@ -31,17 +31,17 @@ A DevTest Labs lab is the infrastructure that encompasses a group of resources s
 
 [Azure role-based access control (RBAC)](/azure/role-based-access-control/overview) defines DevTest Labs access and roles. DevTest Labs has three roles that define lab member permissions: **Owner**, **Contributor**, and **DevTest Labs User**.
 
-- Lab **Owners** can do all lab tasks, including creating labs and managing policies and users. Only lab Owners can add and manage lab users and roles. For more information about managing user access and roles, see [Add lab owners, contributors, and users](devtest-lab-add-devtest-user.md).
+- Lab **Owners** can do all lab tasks, including reading or writing to lab resources, setting policies and configurations, adding repositories and base images, and managing users. Only lab Owners can add and manage lab users and roles. For more information about managing user access and roles, see [Add lab owners, contributors, and users](devtest-lab-add-devtest-user.md).
 
-  Lab Owners must have at least Contributor rights in the Azure subscription their lab is in. Azure subscription Owners have access to all resources and user assignments in their subscriptions, so they automatically inherit the lab Owner role.
+  Lab Owners must have at least Contributor rights in the Azure subscription their lab is in. Subscription Owners can access all subscription resources and user assignments, so they automatically inherit the Owner role for labs in their subscriptions.
 
   Lab Owners can also create and assign custom DevTest Labs roles. For more information, see [Grant user permissions to specific lab policies](devtest-lab-grant-user-permissions-to-specific-lab-policies.md).
 
 - Lab **Contributors** can do everything that lab Owners can, such as create and configure labs and policies, but they can't assign or manage users and roles.
 
 - **DevTest Labs Users** can view all lab resources and policies and can create and modify their own VMs and environments, within policy restrictions such as number of VMs per user.
 
-  DevTest Labs Users can't modify lab policies, or view or change any other users' VMs unless the VM or lab owner grants them permission. DevTest Labs Users automatically have Owner permissions on their own VMs.
+  DevTest Labs Users can't modify lab policies, or view or change any other users' VMs unless the lab or VM owner grants them permission. DevTest Labs Users automatically have Owner permissions on their own VMs.
 
 ### Policies
 
diff --git a/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md b/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md
@@ -4,7 +4,7 @@ description: Walk through the steps to upload a virtual hard disk (VHD) file to
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.custom: UpdateFrequency2
 
 #customer intent: As a lab user, I want to learn how to upload a VHD to a lab storage account so I can use the VHD to create a custom image and VMs.
@@ -55,7 +55,7 @@ When you open Storage Explorer, the Explorer pane shows all the Azure subscripti
 1. Follow the prompts to sign in with the Microsoft account associated with the Azure subscription that has your lab.
 1. After you sign in, select the dropdown arrow next to the Azure subscription you want to use.
 1. The left pane shows the storage accounts associated with the selected Azure subscription. If you don't see your storage account listed, select **Refresh all**.
-1. Select the dropdown arrow next to the lab storage account name you saved earlier, expand **Blob Containers**, and then select **uploads**.
+1. Select the dropdown arrow next to the lab storage account name you noted earlier, expand **Blob Containers**, and then select **uploads**.
 
    :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-dir.png" alt-text="Screenshot that shows the expanded Blob Containers node with the uploads directory.":::
 
diff --git a/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md b/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md
@@ -4,7 +4,7 @@ description: Use Azure PowerShell or Azure CLI command lines and scripts to star
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, UpdateFrequency2 
 ms.devlang: azurecli
 
@@ -26,13 +26,13 @@ This article shows how you can use PowerShell or Azure CLI commands to script or
 
 # [Azure PowerShell](#tab/PowerShell)
 
-- Ownership of a [lab VM](devtest-lab-add-vm.md) in DevTest Labs.
-- Access to Azure PowerShell. You can [use the PowerShell environment of Azure Cloud Shell](/azure/cloud-shell/quickstart) in the Azure portal, or [install Azure PowerShell](/powershell/azure/install-azure-powershell) to use locally. If necessary, run `Update-Module -Name Az` to update your local installation.
+- Owner access to a [lab VM](devtest-lab-add-vm.md) in DevTest Labs.
+- Access to Azure PowerShell. You can [use the Azure Cloud Shell PowerShell environment](/azure/cloud-shell/quickstart), or [install Azure PowerShell](/powershell/azure/install-azure-powershell) to use locally. If necessary, run `Update-Module -Name Az` to update your local installation.
 
 # [Azure CLI](#tab/CLI)
 
-- Ownership of a [lab VM](devtest-lab-add-vm.md) in DevTest Labs.
-- Access to Azure CLI. You can [use the Bash environment of Azure Cloud Shell](/azure/cloud-shell/quickstart) in the Azure portal, or [install Azure CLI ](/cli/azure/install-azure-cli) to use locally in a Bash or Windows environment.
+- Owner access to a [lab VM](devtest-lab-add-vm.md) in DevTest Labs.
+- Access to Azure CLI. You can [use the Azure Cloud Shell Bash environment](/azure/cloud-shell/quickstart), or [install Azure CLI](/cli/azure/install-azure-cli) to use locally in a Bash or Windows environment.
 
 ---
 
@@ -42,7 +42,7 @@ This article shows how you can use PowerShell or Azure CLI commands to script or
 
 The following PowerShell script starts or stops a VM in a lab by using the [Invoke-AzResourceAction](/powershell/module/az.resources/invoke-azresourceaction) PowerShell cmdlet. The `ResourceId` parameter is the fully qualified ID for the lab VM you want to start or stop. The `Action` parameter determines whether to start or stop the VM, depending on which action you need.
 
-1. In Cloud Shell, make sure the **PowerShell** environment is selected.
+1. If you use Cloud Shell, make sure the **PowerShell** environment is selected.
 
 1. Use the PowerShell [Connect-AzAccount](/powershell/module/Az.Accounts/Connect-AzAccount) cmdlet to sign in to your Azure account. If you have multiple Azure subscriptions, uncomment `Set-AzContext` and provide the `<SubscriptionId>` you want to use.
 
@@ -86,9 +86,9 @@ The following PowerShell script starts or stops a VM in a lab by using the [Invo
 
 # [Azure CLI](#tab/CLI)
 
-The following script uses the Azure CLI [az lab vm start](/cli/azure/lab/vm#az-lab-vm-start) or [az lab vm stop](/cli/azure/lab/vm#az-lab-vm-stop) commands to start or stop a lab VM.
+The following script uses the Azure CLI [az lab vm start](/cli/azure/lab/vm#az-lab-vm-start) or [az lab vm stop](/cli/azure/lab/vm#az-lab-vm-stop) command to start or stop a lab VM.
 
-To run locally, use the appropriate syntax for setting and calling variables depending on whether you have a Bash or Windows environment. In Cloud Shell, use the **Bash** environment and syntax.
+To run the script locally, use the appropriate syntax depending on whether you have a Bash or Windows environment. In Cloud Shell, use the **Bash** environment and syntax.
 
 1. Sign in to your Azure account. If you have multiple Azure subscriptions, uncomment the `az account set` line and provide a subscription ID to use.
 
