edits

Author: v-thepet

articles/devtest-labs/deploy-nested-template-environments.md

@@ -10,26 +10,28 @@ ms.date: 04/02/2025
 #customer intent: As a DevTest labs user, I want to learn about using nested templates to deploy environments so I can take advantage of their testing, reuse, and readability benefits.
 ---
 
-# DevTest Labs environments with nested templates
+#  Nested templates in DevTest Labs environments
 
-Azure DevTest Labs environments contain multiple infrastructure-as-a-service (IaaS) virtual machines (VMs) with platform-as-a-service (PaaS) resources installed. You can provision the PaaS and IaaS resources by using Azure Resource Manager (ARM) templates. This article shows an example of nesting templates to deploy an Azure DevTest Labs environment.
+Azure DevTest Labs *environments* consist of multiple infrastructure-as-a-service (IaaS) virtual machines (VMs) with platform-as-a-service (PaaS) resources installed. You can provision these PaaS and IaaS resources by using Azure Resource Manager (ARM) templates.
 
-A *nested deployment* runs secondary ARM templates from within a main template. Decomposing a deployment into a set of targeted, purpose-specific templates provides testing, reuse, and readability benefits. For general information about nested templates, including code samples, see [Use linked and nested templates when deploying Azure resources](/azure/azure-resource-manager/templates/linked-templates).
+A *nested deployment* runs secondary ARM templates from within a main template. This article shows an example of using nested templates to deploy a DevTest Labs environment.
 
-In DevTest Labs, you can store ARM templates in a Git repository that you link to a lab. When you use a linked repository template to create a new DevTest Labs environment, the deployment copies the template files into the lab's Azure Storage container.
+Decomposing a deployment into a set of targeted, purpose-specific templates provides testing, reuse, and readability benefits. For general information about nested templates, including code samples, see [Use linked and nested templates when deploying Azure resources](/azure/azure-resource-manager/templates/linked-templates).
 
 [!INCLUDE [direct-azure-deployment-environments](includes/direct-azure-deployment-environments.md)]  
 
 ## Nested template deployment with Visual Studio
 
+In DevTest Labs, you can store ARM templates in a Git repository that you link to a lab. When you use a linked repository template to create a new DevTest Labs environment, the deployment copies the template files into the lab's Azure Storage container.
+
 The Azure Resource Group project template in Visual Studio makes it easy to develop and debug nested templates. When you add a nested template file to the lab repository and add nested template code to the main *azuredeploy.json* template file, Visual Studio automatically takes the following actions:
 
 - Adds a subfolder for the secondary template and parameters files, and copies the subfolder to the lab storage container.
 - Adds variables for the nested template folder and files to the `variables` section of the main template file.
 - Adds the `_artifactsLocation` and `_artifactsLocationSasToken` parameters to the main template file.
 - Inserts the location and Shared Access Signature (SaS) token into the parameters file.
 
-In the following nested template example, the Git repository folder has a subfolder, *nestedtemplates*, that contains the nested template files *NestOne.json* and *NestOne.parameters.json*. You can add more nested template subfolders, but at only one level of nesting.
+The following nested template example shows a Git repository folder with a subfolder, *nestedtemplates*, that contains the nested template files *NestOne.json* and *NestOne.parameters.json*. You can add more than one nested template subfolder, but at only one level of nesting.
 
 :::image type="content" source="media/deploy-nested-template-environments/visual-studio-project-structure.png" alt-text="Screenshot that shows the nested template project structure in Visual Studio.":::
 

articles/devtest-labs/devtest-lab-create-custom-image-from-vhd-using-powershell.md

@@ -10,7 +10,7 @@ ms.custom: devx-track-azurepowershell, UpdateFrequency2
 #customer intent: As a lab administrator, I want to create custom images from VHD files, so I can make the custom images available to lab users as bases for creating lab VMs.
 ---
 
-# Create a custom image from a VHD file with PowerShell
+# Create a custom image from a VHD file by using Azure PowerShell
 
 [!INCLUDE [devtest-lab-create-custom-image-from-vhd-selector](../../includes/devtest-lab-create-custom-image-from-vhd-selector.md)]
 

articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md

@@ -38,7 +38,7 @@ To create a custom image from a lab VM, take the following steps:
    - **I have already generalized this virtual machine**
    - **Generalize this virtual machine** (for Windows: **(Run sysprep)** or for Linux: **(Run deprovision)**)
 
-   [Sysprep](/windows-hardware/manufacture/desktop/sysprep--system-preparation--overview) for Windows or [deprovision] for Linux create generalized images that have user profiles and other VM-specific settings removed. If you don't run sysprep or deprovision, the custom image creates exact copies of the machine that can run in isolated networks. For more information, see [Generalize a VM](/azure/virtual-machines/generalize).
+   [Sysprep](/windows-hardware/manufacture/desktop/sysprep--system-preparation--overview) for Windows or [deprovision](/azure/virtual-machines/generalize#linux) for Linux create generalized images that have user profiles and other VM-specific settings removed. If you don't run sysprep or deprovision, the custom image creates exact copies of the machine that can run in isolated networks. For more information, see [Generalize a VM](/azure/virtual-machines/generalize).
 
    If you want sysprep or deprovision to be run on the VM when creating the custom image, choose **Generalize this virtual machine**. Running sysprep or deprovision when you create the custom image makes the existing VM unusable.
 

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

@@ -17,7 +17,7 @@ Azure DevTest Labs supports changing the size of a lab virtual machine (VM), bas
 
 To resize a VM, you must be a lab administrator or an owner of the VM. If the lab sets an [allowed VM sizes](devtest-lab-set-lab-policy.md#set-allowed-virtual-machine-sizes) policy, you can resize the VM only to sizes that the policy permits.
 
-The VM must be stopped before you resize it. To stop a VM, disconnect from it, and select **Stop** on the top toolbar of the VM's **Overview** page in the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
+To avoid losing work, stop the VM before you resize it. To stop a VM, disconnect from it, and select **Stop** on the top toolbar of the VM's **Overview** page in the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
 
 :::image type="content" source="./media/devtest-lab-resize-vm/stop-vm.png" alt-text="Screenshot that shows selecting Stop on the Overview page for a VM.":::
 
@@ -31,7 +31,10 @@ To resize a VM:
 
 You can check the status of the resize operation in the **Notifications** window.
 
-   :::image type="content" source="./media/devtest-lab-resize-vm/resize-status.png" alt-text="Screenshot of the Notifications window that shows resizing status.":::
+:::image type="content" source="./media/devtest-lab-resize-vm/resize-status.png" alt-text="Screenshot of the Notifications window that shows resizing status.":::
+
+>[!NOTE]
+>If the resize operation fails with an error that **Resizing virtual machines with shared IP configuration is not supported**, you need to add and associate a Public IP address to the VM. For more information, see [Associate a public IP address to a virtual machine](/azure/virtual-network/ip-services/associate-public-ip-address-vm).
 
 When the resize finishes, you can start the VM by selecting **Start** from the VM **Overview** page top toolbar, and then connect to the VM by selecting **Connect** in the toolbar.
 

articles/devtest-labs/media/devtest-lab-resize-vm/resize-status.png

@@ -51,15 +51,31 @@ Create the following files in your Terraform directory. Make sure the directory
 
 ## Initialize Terraform
 
-[!INCLUDE [terraform-init.md](../includes/terraform-init.md)]
+Run [terraform init](https://www.terraform.io/docs/commands/init.html) to initialize the Terraform deployment. This command downloads the Azure provider required to manage your Azure resources. The `-upgrade` parameter upgrades the provider plugins to the newest supported version.
+
+```console
+terraform init -upgrade
+```
 
 ## Create the Terraform execution plan
 
-[!INCLUDE [terraform-plan.md](../includes/terraform-plan.md)]
+Run [terraform plan](https://www.terraform.io/docs/commands/plan.html) to create an execution plan. The `terraform plan` command creates an execution plan, but doesn't execute it. Instead, it determines what actions are necessary to create the configuration specified in your configuration files.
+
+This pattern allows you to verify whether the execution plan matches your expectations before making any changes to actual resources. Use the optional `-out` parameter to specify an output file for the plan named `main.tfplan`. You can review the file to ensure that the plan is exactly what to apply.
+
+```console
+terraform plan -out main.tfplan
+```
 
 ## Apply the Terraform execution plan
 
-[!INCLUDE [terraform-apply-plan.md](../includes/terraform-apply-plan.md)]
+Run [terraform apply](https://www.terraform.io/docs/commands/apply.html) to apply the execution plan to your cloud infrastructure. The example `terraform apply` command assumes you previously ran `terraform plan -out main.tfplan`.
+
+If you specify a different filename for the `-out` parameter in `terraform_plan`, use that filename in the call to `terraform apply`. If you don't use the `-out` parameter in `terraform_plan`, call `terraform apply` without any parameters.
+
+```console
+terraform apply main.tfplan
+```
 
 ## Verify the results
 
@@ -73,7 +89,19 @@ az lab vm list --resource-group $resource_group_name --lab-name $lab_name
 
 ## Clean up resources
 
-[!INCLUDE [terraform-plan-destroy.md](../includes/terraform-plan-destroy.md)]
+When you no longer need the resources Terraform created, take the following steps to remove them:
+
+1. Run [terraform plan](https://www.terraform.io/docs/commands/plan.html) with the `destroy` flag. The `terraform plan` command creates the execution plan but doesn't execute it. The `-out` parameter specifies an output file for the plan named `main.destroy.tfplan`. 
+
+   ```console
+   terraform plan -destroy -out main.destroy.tfplan
+   ```
+
+1. Run [terraform apply](https://www.terraform.io/docs/commands/apply.html) to apply the execution plan specified in the `main.destroy.tfplan` file.
+
+    ```console
+    terraform apply main.destroy.tfplan
+    ```
 
 ## Next step