Merge pull request #111009 from spelluru/dtlactivitylog0410

activity log

Author: American-Dipper

articles/lab-services/devtest-lab-auto-shutdown.md

@@ -13,7 +13,7 @@ ms.workload: na
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: article
-ms.date: 01/17/2020
+ms.date: 04/10/2020
 ms.author: spelluru
 
 ---
@@ -25,7 +25,7 @@ This article explains how to configure autoshutdown settings for lab VMs in DevT
 ## Configure autoshutdown for lab VMs (DevTest Labs)
 Azure DevTest Labs enables you to control cost and minimize waste in your labs by managing policies (settings) for each lab. This article shows you how to configure autoshutdown policy for a lab account and configure autoshutdown settings for a lab in the lab account. To view how to set every lab policy, see [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md).  
 
-### Set auto shut down policy for a lab
+### Set auto shutdown policy for a lab
 As a lab owner, you can configure a shutdown schedule for all the VMs in your lab. By doing so, you can save costs from running machines that aren't being used (idle). You can enforce a shutdown policy on all your lab VMs centrally but also save your lab users the effort from setting up a schedule for their individual machines. This feature enables you to set the policy on your lab schedule starting from offering no control to full control, to your lab users. As a lab owner, you can configure this policy by taking the following steps:
 
 1. On the home page for your lab, select **Configuration and policies**.
@@ -188,14 +188,33 @@ To get started, create a logic app in your Azure subscription by using the follo
 
 ## Configure autoshutdown for compute VMs
 
-1. On the **Virtual machine** page, select **Auto-shutdown** on the left menu. 
+1. On the **Virtual machine** page, select **Auto-shutdown** on the left menu in the **Operations** section. 
 2. On the **Auto-shutdown** page, select **On** to enable this policy, and **Off** to disable it.
 3. If you enable this policy, specify the **time** (and **time zone**) at which the VM should be shut down.
 4. Specify **Yes** or **No** for the option to send a notification 30 minutes prior to the specified autoshutdown time. If you choose **Yes**, enter a webhook URL endpoint or email address specifying where you want the notification to be posted or sent. The user receives notification and is given the option to delay the shutdown. For more information, see the [Notifications](#notifications) section. 
 9. Select **Save**.
 
     ![Configure autoshutdown for a compute VM](./media/devtest-lab-auto-shutdown/comnpute-auto-shutdown.png)
 
+### Activity log
+When you update the autoshutdown setting, you will see the **Add or modify schedules** operation in the activity log. If you don't see it, remove **Resource: mycomputevm** from the filters. If you still don't see it, wait for sometime and refresh the activity log.
+
+![Activity log entry](./media/devtest-lab-auto-shutdown/activity-log-entry.png)
+
+When you select the **Add or modify schedules** operation, you see the following information on the **Summary** page:
+
+- Operation name (Add or modify schedules)
+- The date and time at which the autoshutdown setting was updated.
+- The email address of the user who updated the setting. 
+
+![Activity log entry summary](./media/devtest-lab-auto-shutdown/activity-log-entry-summary.png)
+
+Switch to the **Change history** tab in the **Add or modify schedules** page, you see the change history for the setting. In the following example, the shutdown time was changed from 7 PM to 6 PM on April 10, 2020 at 15:18:47 EST. And, the setting was disabled at 15:25:09 EST. 
+
+![Activity log - change history](./media/devtest-lab-auto-shutdown/activity-log-entry-change-history.png)
+
+To see more details about the operation, switch to the **JSON** tab in the **Add or modify schedules** page.
+
 ## Next steps
 To learn how to set all policies, see [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md).