edits

Author: v-thepet

articles/devtest-labs/devtest-lab-add-vm.md

@@ -27,7 +27,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-add-vm.png" alt-text="Screenshot that shows the lab overview page with the Add button.":::
 
-1. On the **Choose a base** page, select an image for the VM. You can choose from Marketplace images, custom images, or formulas that the lab administrator made available. The following instructions use a Windows Server 2022 Datacenter image. Some bases might have different settings.
+1. On the **Choose a base** page, select an image for the VM. You can choose from Marketplace images, custom images, or formulas that the lab administrator made available. The following instructions use a Windows 11 Pro image. Some bases might have different settings.
 
 1. On the **Basic Settings** tab of the **Create lab resource** screen, provide the following information:
 
@@ -113,9 +113,9 @@ When you create a VM in DevTest Labs, you automatically have permission to acces
 
 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.
 
-## Copy existing VMs into a lab
+## Copy existing Azure VMs into a lab
 
-You can copy existing VMs to DevTest Labs as follows:
+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.

articles/devtest-labs/devtest-lab-attach-detach-data-disk.md

@@ -12,7 +12,7 @@ ms.custom: UpdateFrequency2
 
 # 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. You can create, attach, detach, and reattach multiple [data disks](/azure/virtual-machines/managed-disks-overview) for your lab VMs. 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 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
 
@@ -23,9 +23,7 @@ To attach or detach a data disk, you need to own the lab VM, and the VM must be
 Follow these steps to create and attach a new managed data disk for a DevTest Labs VM.
 
 1. In the Azure portal, select your VM from the **My virtual machines** list on your lab **Overview** page.
-
 1. On the VM **Overview** page, select **Disks** under **Settings** in the left navigation.
- 
 1. On the **Disks** page, select **Attach new**.
 
    :::image type="content" source="./media/devtest-lab-attach-detach-data-disk/devtest-lab-attach-new.png" alt-text="Screenshot of Attach new on the V M's Disk page.":::
@@ -49,9 +47,7 @@ Follow these steps to create and attach a new managed data disk for a DevTest La
 Follow these steps to attach an existing available data disk to a running VM.
 
 1. In the Azure portal, select your VM from the **My virtual machines** list on the lab **Overview** page.
-
 1. On the VM **Overview** page, select **Disks** under **Settings** in the left navigation.
- 
 1. On the **Disks** page, select **Attach existing**.
 
    :::image type="content" source="./media/devtest-lab-attach-detach-data-disk/devtest-lab-attach-existing-button.png" alt-text="Screenshot of Attach existing on the VM's Disk page.":::

articles/devtest-labs/devtest-lab-concepts.md

@@ -7,7 +7,7 @@ author: RoseHJM
 ms.date: 03/17/2025
 ms.custom: UpdateFrequency2
 
-#customer intent: As a lab user or administrator, I want to understand basic DevTest Labs concepts so I can create, manage, or use labs, VMs, and environments.
+#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.
 ---
 
 # DevTest Labs concepts
@@ -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. 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 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).
 
-  A lab Owner must have at least Contributor rights in the Azure subscription the 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. Azure subscription Owners have access to all resources and user assignments in their subscriptions, so they automatically inherit the lab Owner role.
 
   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 Owners can, such as create and configure labs and policies, but can't assign or manage users and roles.
+- 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 change any other users' VMs. 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 VM or lab owner grants them permission. DevTest Labs Users automatically have Owner permissions on their own VMs.
 
 ### Policies
 
@@ -55,9 +55,9 @@ You can use ARM templates to create and update DevTest Labs labs, environments,
 
 For more information about using ARM templates in DevTest Labs, see:
 
-- [Create labs from ARM templates](create-lab-windows-vm-template.md)
-- [Create environments from ARM templates](devtest-lab-create-environment-from-arm.md)
-- [Create ARM templates for VMs](devtest-lab-use-resource-manager-template.md)
+- [Create labs from ARM templates](create-lab-windows-vm-template.md).
+- [Create environments from ARM templates](devtest-lab-create-environment-from-arm.md).
+- [Create ARM templates for VMs](devtest-lab-use-resource-manager-template.md).
 
 ### Repositories
 
@@ -97,7 +97,7 @@ After a lab user claims a VM, the VM moves to that user's **My virtual machines*
 
 DevTest Labs custom images and formulas are mechanisms for fast VM creation and provisioning.
 
-- A custom image is a VM image created from an existing VM or virtual hard drive (VHD), which can have software and other artifacts installed. Lab users can create identical VMs from the custom image. For more information, see [Create a custom image from a VM](devtest-lab-create-custom-image-from-vm-using-portal.md).
+- A custom image is a VM image created from an existing VM or virtual hard disk (VHD), which can have software and other artifacts installed. Lab users can create identical VMs from the custom image. For more information, see [Create a custom image from a VM](devtest-lab-create-custom-image-from-vm-using-portal.md).
 
 - A formula is a list of default property values for creating a lab VM, such as base image, VM size, virtual network, and artifacts. When you create a VM from a formula, you can use the default values as-is or modify them. For more information, see [Manage Azure DevTest Labs formulas](devtest-lab-manage-formulas.md).
 

articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md

@@ -40,11 +40,11 @@ To get the name of the lab storage account:
 
    :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-image-powershell.png" alt-text="Screenshot that shows the link to upload a VHD by using PowerShell.":::
 
-1. On the **Upload an image using PowerShell** page, scroll right to see the call to the `Add-AzureRmVhd` cmdlet. The `-Destination` parameter contains the URI for the blob container in the format `https://<storageAccountName>.blob.core.windows.net...`.
+1. On the **Upload an image using PowerShell** page, scroll right to see the call to the `Add-AzureRmVhd` cmdlet. The `Destination` parameter contains the URI for the blob container in the format `https://<storageAccountName>.blob.core.windows.net`.
 
    :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/destination-parameter.png" alt-text="Screenshot that shows an example of a storage account name in the Add VHD box.":::
 
-1. Note the storage account name to use in the next section.
+1. Note the `<storageAccountName>` to use in the next section.
 
 ### Upload the VHD file
 
@@ -67,17 +67,17 @@ When you open Storage Explorer, the Explorer pane shows all the Azure subscripti
 1. For **Blob type**, select **Page Blob**.
 1. Select **Upload**.
 
-:::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-file.png" alt-text="Screenshot that shows the Upload Files dialog box.":::
+   :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-file.png" alt-text="Screenshot that shows the Upload Files dialog box.":::
 
 1. Track the upload status in the **Activities** pane at the bottom of Storage Explorer. Uploading the VHD file might take a long time, depending on the size of the VHD file and your connection speed.
 
    :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/upload-status.png" alt-text="Screenshot that shows the Activities pane with upload status.":::
 
 After the VHD file uploads, you can see it in your lab storage account in the Azure portal.
 
-1. Open your lab storage account by searching for and selecting it in the Azure Search bar, or by selecting it from **Storage accounts**.
+1. Open your lab storage account by searching for and selecting its name in the Azure Search bar, or by selecting it from **Storage accounts**.
 1. On the storage account's **Overview** page, select **Data storage** > **Containers** from the left navigation.
-1. On the **Containers** page, open the **Uploads** folder to see the uploaded VHD file along with any other uploads to the storage account.
+1. On the **Containers** page, open the **Uploads** folder to see the uploaded VHD file and any other uploads to the storage account.
 
    :::image type="content" source="media/devtest-lab-upload-vhd-using-storage-explorer/uploads.png" alt-text="Screenshot that shows the uploaded VHD file in the Azure storage account.":::
 

articles/devtest-labs/media/devtest-lab-upload-vhd-using-storage-explorer/upload-file.png

@@ -20,19 +20,19 @@ This article shows how you can use PowerShell or Azure CLI commands to script or
 - Start and stop a VM when a continuous integration and continuous delivery (CI/CD) workflow begins and finishes. For an example of this workflow, see [Run an image factory from Azure DevOps](image-factory-set-up-devops-lab.md).
 
 >[!NOTE]
->You can also use the Azure portal to start, stop, or [restart](devtest-lab-restart-vm.md) DevTest Labs VMs. Lab admins can use the portal to configure [automatic startup](devtest-lab-auto-startup-vm.yml) and [automatic shutdown](devtest-lab-auto-shutdown.md) schedules and policies for lab VMs.
+>You can also start, stop, or [restart](devtest-lab-restart-vm.md) DevTest Labs VMs by using the Azure portal. Lab admins can use the portal to configure [automatic startup](devtest-lab-auto-startup-vm.yml) and [automatic shutdown](devtest-lab-auto-shutdown.md) schedules and policies for lab VMs.
 
 ## Prerequisites
 
 # [Azure PowerShell](#tab/PowerShell)
 
-- Ownership of a [lab VM in DevTest Labs](devtest-lab-add-vm.md).
-- Access to Azure PowerShell. You can [use Azure Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) in the Azure portal, or [install Azure PowerShell](/powershell/azure/install-azure-powershell) locally. If necessary, run `Update-Module -Name Az` to update your local installation.
+- 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.
 
 # [Azure CLI](#tab/CLI)
 
-- Ownership of a [lab VM in DevTest Labs](devtest-lab-add-vm.md).
-- Access to Azure CLI. You can [use Azure Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) in the Azure portal, or [install Azure CLI ](/cli/azure/install-azure-cli) locally.
+- 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.
 
 ---
 
@@ -88,10 +88,7 @@ The following PowerShell script starts or stops a VM in a lab by using the [Invo
 
 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.
 
->[!NOTE]
->This script assumes a Bash environment. The variables and command for a Windows environment, like a command prompt, have slight variations.
-
-1. In Cloud Shell, make sure the **Bash** environment is selected.
+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.
 
 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.
 
@@ -103,6 +100,8 @@ The following script uses the Azure CLI [az lab vm start](/cli/azure/lab/vm#az-l
 
 1. Set variables by providing values for `<SubscriptionId>`, `<resourceGroup>`, `<lab name>`, `<VM name>`, and whether to `Start` or `Stop` the VM.
 
+   **Bash**
+
    ```azurecli
    SUBSCRIPTIONID=<SubscriptionId>
    RESOURCEGROUP=<resourceGroup>
@@ -111,19 +110,37 @@ The following script uses the Azure CLI [az lab vm start](/cli/azure/lab/vm#az-l
    ACTION=<Start or Stop>
    ```
 
-   >[!TIP]
-   >If you don't know the name of the Azure resource group that contains your lab, you can find it by providing your `<lab name>` in the following query.
+   **Windows**
 
    ```azurecli
-   az resource list --resource-type "Microsoft.DevTestLab/labs" --name "<lab name>" --query "[0].resourceGroup"
+   set SUBSCRIPTIONID=<SubscriptionId>
+   set RESOURCEGROUP=<resourceGroup>
+   set DEVTESTLABNAME=<lab name>
+   set VMNAME=<VM name>
+   set ACTION=<Start or Stop>
    ```
 
+   >[!TIP]
+   >If you don't know the name of the Azure resource group that contains your lab, you can find it by providing your `<lab name>` in the following query.
+   >
+   >```azurecli
+   >az resource list --resource-type "Microsoft.DevTestLab/labs" --name "<lab name>" --query "[0].resourceGroup"
+   >```
+
 1. Run the following Azure CLI command to start or stop the VM, based on the value passed to `ACTION`.
 
+   **Bash**
+
    ```azurecli
    az lab vm $ACTION --lab-name $DEVTESTLABNAME --name $VMNAME --resource-group $RESOURCEGROUP
    ```
 
+   **Windows**
+
+   ```azurecli
+   az lab vm %ACTION% --lab-name %DEVTESTLABNAME% --name %VMNAME% --resource-group %RESOURCEGROUP%
+```
+
 ---
 
 ## Related content