Merge pull request #176765 from dagiro/Freshness9

Freshness9 - Add a VM to a lab in Azure DevTest Labs

Author: Court72

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

@@ -26,7 +26,9 @@ You add a claimable VM to a lab in a similar manner to how you [add a standard V
         You can also save secrets in the key vault first and then use it while creating a VM in the lab. For more information, see [Store secrets in a key vault](devtest-lab-store-secrets-in-key-vault.md). To use the password stored in the key vault, select **Use a saved secret**, and specify a key value that corresponds to your secret (password).
     4. In the **More options** section, select **Change size**. Select one of the predefined items that specify the processor cores, RAM size, and the hard drive size of the VM to create.
     5. Select **Add or Remove Artifacts**. Select and configure the artifacts that you want to add to the base image.
-    **Note:** If you're new to DevTest Labs or configuring artifacts, refer to the [Add an existing artifact to a VM](./devtest-lab-add-vm.md#add-an-existing-artifact-to-a-vm) section, and then return here when finished.
+    
+    >[!NOTE] 
+    >If you're new to DevTest Labs or configuring artifacts, refer to the [Add artifacts after installation](./devtest-lab-add-vm.md#add-artifacts-after-installation) section, and then return here when finished.
 2. Switch to the **Advanced Settings** tab at the top, and do the following actions:
     1. To change the virtual network that the VM is in, select **Change VNet**.
     2. To change the subnet, select **Change subnet**.

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

@@ -226,7 +226,7 @@ sections:
           You have two options for simultaneously creating multiple VMs from the same template:
           
           - You can use the [Azure DevOps Tasks extension](https://marketplace.visualstudio.com/items?itemName=ms-azuredevtestlabs.tasks).
-          - You can [generate a Resource Manager template](devtest-lab-add-vm.md#save-azure-resource-manager-template) while you're creating a VM, and [deploy the Resource Manager template from Windows PowerShell](../azure-resource-manager/templates/deploy-powershell.md).
+          - You can [generate a Resource Manager template](devtest-lab-add-vm.md#create-and-add-virtual-machines) while you're creating a VM, and [deploy the Resource Manager template from Windows PowerShell](../azure-resource-manager/templates/deploy-powershell.md).
           - You can also specify more than one instance of a machine to be created during virtual machine creation. To learn more about creating multiple instances of virtual machines, see the doc on [creating a lab virtual machine](devtest-lab-add-vm.md).
           
       - question: |

articles/devtest-labs/devtest-lab-faq.yml

@@ -22,7 +22,7 @@ Developers often have different requirements for development machines for differ
 - Developers can quickly provision their development machines on demand or [claim an existing pre-configured machine](devtest-lab-add-claimable-vm.md).
 - Developers can provision resources in a self-service way without needing subscription-level permissions.
 - IT or admins can [pre-define the networking topology](devtest-lab-configure-vnet.md) and developers can directly use it in a simple and intuitive way without requiring any special access.
-- Developers can easily [customize](devtest-lab-add-vm.md#add-an-existing-artifact-to-a-vm) their development machines as needed.
+- Developers can easily [customize](devtest-lab-add-vm.md#add-artifacts-after-installation) their development machines as needed.
 - Administrators can control costs by ensuring that:
     - Developers [can't get more VMs](devtest-lab-set-lab-policy.md#set-virtual-machines-per-user) than they need for development
     - [VMs are shut down](devtest-lab-set-lab-policy.md#set-auto-shutdown) when not in use
@@ -55,7 +55,7 @@ A lab in Azure DevTest Labs acts as a great container for transient activities l
 - [Policies](devtest-lab-set-lab-policy.md) ensure trainees only get the number of resources, such as virtual machines, that they need.
 - Pre-configured and created machines are [claimed](devtest-lab-add-claimable-vm.md) with single action from trainee.
 - Labs are shared with trainees by accessing [URL for the lab](/azure/devtest-labs/devtest-lab-faq#how-do-i-share-a-direct-link-to-my-lab).
-- [Expiration dates](devtest-lab-add-vm.md#steps-to-add-a-vm-to-a-lab-in-azure-devtest-labs) on virtual machines ensure that machines are deleted after they are no longer needed.
+- [Expiration dates](devtest-lab-add-vm.md#create-and-add-virtual-machines) on virtual machines ensure that machines are deleted after they are no longer needed.
 - It’s easy to [delete a lab](devtest-lab-delete-lab-vm.md#delete-a-lab) and all [related resources](/azure/devtest-labs/devtest-lab-faq#how-do-i-automate-the-process-of-deleting-all-the-vms-in-my-lab) when the training is over.
 
 For more information, see [Use Azure DevTest Labs for training](devtest-lab-training-lab.md).