Merge pull request #269713 from RoseHJM/dtl-gh-troubleshooting

DTL - GH issues updates.

Author: v-ccolin

articles/devtest-labs/media/troubleshoot-vm-environment-creation-failures/configuration-policies-activity-log.png

@@ -4,37 +4,42 @@ description: Learn how to troubleshoot virtual machine (VM) and environment crea
 ms.topic: how-to
 ms.author: rosemalcolm
 author: RoseHJM
-ms.date: 06/26/2020
+ms.date: 03/20/2020
 ms.custom: UpdateFrequency2
+#customer intent: As a lab admin, I want to troubleshoot virtual machine (VM) and environment creation failures in Azure DevTest Labs so that I can resolve issues.
 ---
 
 # Troubleshoot virtual machine (VM) and environment creation failures in Azure DevTest Labs
-DevTest Labs gives you warnings if a machine name is invalid or if you're about to violate a lab policy. Sometimes, you see red `X` next to your lab VM or environment status that informs you that something went wrong.  This article provides a few tricks that you can use to find the underlying issue and, hopefully, avoid the issue in the future.
+DevTest Labs gives you warnings if a machine name is invalid or if you're about to violate a lab policy. Sometimes, you see red `X` next to your lab VM or environment status that informs you that something went wrong. This article provides a few tricks that you can use to find the underlying issue and, hopefully, avoid the issue in the future.
 
 ## Portal notifications
-If you're using the Azure portal, the first place to look at is the **notifications panel**.  The notifications panel, available on the main command bar by clicking the **bell icon**, will tell you whether the lab VM or environment creation was successful or not.  If there was a failure, you see the error message associated with the creation failure. The details often give further information to help you resolve the issue. In the following example, the virtual machine creation failed because of running out of cores. The detailed message tells you how to fix the issue and request a core quota increase.
+If you're using the Azure portal, the first place to look at is the **notifications panel**. The notifications panel, available on the main command bar by clicking the **bell icon**, tells you whether the lab VM or environment creation was successful or not. If there was a failure, you see the error message associated with the creation failure. The details often give further information to help you resolve the issue. In the following example, the virtual machine creation failed because you exceeded the limit of virtual machines allowed in the lab. 
 
-![Azure portal notification](./media/troubleshoot-vm-environment-creation-failures/portal-notification.png)
+:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/portal-notification.png" alt-text="Screenshot showing Azure portal notifications." lightbox="media/troubleshoot-vm-environment-creation-failures/portal-notification.png":::
 
-### VM in corruption state
-If you see the status of your VM in the lab as **Corrupted**, the underlying VM may have been deleted from the **Virtual Machine** page that user can navigate to from the **Virtual Machines** page (not from the DevTest Labs page). Clean up your lab in DevTest Labs by deleting the VM from the lab. Then, recreate your VM in the lab. 
+### VM in corrupted state
+If you see the status of your VM in the lab as **Corrupted**, the underlying VM might have been deleted from the **Virtual Machine** page that user can navigate to from the **Virtual Machines** page (not from the DevTest Labs page). Clean up your lab in DevTest Labs by deleting the VM from the lab. Then, recreate your VM in the lab. 
 
-![VM in corrupted state](./media/troubleshoot-vm-environment-creation-failures/vm-corrupted-state.png)
+:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/vm-corrupted-state.png" alt-text="Screenshot showing a VM in a corrupted state." lightbox="media/troubleshoot-vm-environment-creation-failures/vm-corrupted-state.png":::
 
+## Activity logs
+Look at activity logs if you're investigating a failure sometime after attempting the creation of your VM or environment. There are three types of activity logs available from the Lab page; logs for activities affecting lab configuration and policies, logs for VMs and logs for environments. The error you're troubleshooting might be in any one of these logs, depending on its source. This section shows you how to find these logs. 
 
+## Activity log for lab configuration and policies
 
-## Activity logs
-Look at activity logs if you're investigating a failure sometime after attempting the creation of your VM or environment. This section shows you how to find logs for VMs and environments.
+Activity logs for configuration and policies show events generated by the lab configuration settings or any lab policies you set. In this example, you see the error that details the VM creation failure referenced in the [portal notification](#portal-notifications) shown earlier. To see the activity logs for lab configuration and policies, follow these steps:
 
-## Activity logs for virtual machines
+1. On the home page for your lab, select **Configuration and policies** on the left menu.
+1. On the **Configuration and policies** page, select **Activity log** on the menu.
+1. In the activity log items, expand the failed operation `Create a virtual machine`, then select the failed operation `Add or modify virtual machine` to see the details.
 
-1. On the home page for your lab, select the VM to launch the **Virtual Machine** page.
-2. On the **Virtual Machine** page, in the **MONITORING** section of the left menu, select **Activity log** to see all logs associated with the VM.
-3. In the activity log items, select the operation that failed. Typically, the failed operation is called `Write Virtualmachines`.
-4. In the right pane, switch to the JSON tab. You see the details in the JSON view of the log.
+   :::image type="content" source="media/troubleshoot-vm-environment-creation-failures/configuration-policies-activity-log.png" alt-text="Screenshot of Azure portal showing a Lab Configuration and policies activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/configuration-policies-activity-log.png":::
+
+1. In the right pane, switch to the JSON tab. You see the details in the JSON view of the log.
 
-    ![Activity log for a VM](./media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png)
-5. Look through the JSON log until you find the `statusMessage` property. It gives you the main error message and further detail information, if applicable. The following JSON is an example for the core quoted exceeded error seen earlier in this article.
+   :::image type="content" source="media/troubleshoot-vm-environment-creation-failures/configuration-policies-error-json.png" alt-text="Screenshot of Azure portal showing details of a Lab Configuration and policies activity log event in JSON." lightbox="media/troubleshoot-vm-environment-creation-failures/configuration-policies-error-json.png":::
+
+1. Look through the JSON log until you find the `statusMessage` property. It gives you the main error message and further detail information, if applicable. The following JSON is an example for the core quoted exceeded error seen earlier in this article.
 
     ```json
     "properties": {
@@ -43,27 +48,44 @@ Look at activity logs if you're investigating a failure sometime after attemptin
     },
     ```
 
+## Activity log for a virtual machine
+
+Activity logs for virtual machines show events generated by the virtual machine, like starting and stopping. To see the activity logs for a virtual machine, follow these steps:
+
+1. On the home page for your lab, select the VM to launch the **Virtual Machine** page.
+1. On the **Virtual Machine** page, in the **General** section of the left menu, select **Activity log** to see all logs associated with the VM.
+
+   :::image type="content" source="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png" alt-text="Screenshot of Azure portal showing a virtual machine activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png":::
+
+1. Select the event you're interested in to see the details.
+1. To see the details of the event, switch to the JSON tab.
+
 ## Activity log for an environment
 
-To see the activity log for an environment creation, follow these steps:
+Activity logs for environments show events generated by the environment, like deployments. In this example, you see an error generated by a failed environment creation attempt. To see the activity log for an environment, follow these steps:
 
-1. On the home page for your lab, select **Configuration and policies** on the left menu.
-2. on the **Configuration and policies** page, select **Activity logs** on the menu.
-3. Look for the failure in the activity list in the log and select it.
-4. In the right pane, switch to the JSON tab, and look for the **statusMessage**.
+1. On the home page for your lab, select the environment.
+1. On the environment page, select **Activity log** on the left menu.
+1. Look for the failure in the activity list in the log and select it.
+ 
+   :::image type="content" source="media/troubleshoot-vm-environment-creation-failures/environment-activity-log.png" alt-text="Screenshot of Azure portal showing an environment activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/environment-activity-log.png"::: 
+ 
+1. In the right pane, switch to the JSON tab, and look for the **statusMessage**.
 
-    ![Environment activity log](./media/troubleshoot-vm-environment-creation-failures/envirionment-activity-log.png)
+   :::image type="content" source="media/troubleshoot-vm-environment-creation-failures/environment-error-json.png" alt-text="Screenshot of Azure portal showing details of an environment activity log event in JSON." lightbox="media/troubleshoot-vm-environment-creation-failures/environment-error-json.png"::: 
 
 ## Resource Manager template deployment logs
-If your environment or virtual machine was created through automation, there's one last place to look error information. That's the Azure Resource Manager template deployment log. When a lab resource is created through automation, it's often done through an Azure Resource Manager template deployment. See[https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates) for sample Azure Resource Manager templates that create DevTest Labs resources.
+
+If your environment or virtual machine was created through automation, there's one last place to look error information; the Azure Resource Manager template deployment log. When a lab resource is often created through an Azure Resource Manager template deployment. See [https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates) for sample Azure Resource Manager templates that create DevTest Labs resources.
 
 To see the lab template deployment logs, follow these steps:
 
 1. Launch the page for the resource group in which the lab exists.
-2. Select **Deployments** on the left menu under **Settings**.
-3. Look for deployments with a failed status and select it.
-4. On the **Deployment** page, select **Operation details** link for the operation that failed.
-5. You see details about the operation that failed in the **Operation details** window.
+1. Select **Deployments** on the left menu under **Settings**.
+1. Look for deployments with a failed status and select it.
+1. On the **Deployment** page, select **Operation details** link for the operation that failed.
+1. You see details about the operation that failed in the **Operation details** window.
 
 ## Next steps
-See [Troubleshooting artifact failures](devtest-lab-troubleshoot-artifact-failure.md)
+
+See [Troubleshooting artifact failures](devtest-lab-troubleshoot-artifact-failure.md).