Merge pull request #215428 from SnehaSudhirG/21Oct-Freshness3

Edits for readability

Author: Maggiemouse1

articles/automation/troubleshoot/collect-data-microsoft-azure-automation-case.md

@@ -4,40 +4,41 @@ description: This article describes the information to gather before opening a c
 services: automation
 ms.subservice:
 ms.topic: troubleshooting
-ms.date: 09/23/2019
+ms.custom: engagement-fy23
+ms.date: 10/21/2022
 ---
 
 # Data to collect when opening a case for Microsoft Azure Automation
 
-This article describes some of the information that you should gather before you open a case for Azure Automation with Microsoft Azure Support. This information is not required to open the case. However, it can help Microsoft resolve your problem more quickly. Also, you may be asked for this data by the support engineer after you open the case.
-
-## Basic data
+This article describes the information that you should gather before you open a case for Azure Automation with Microsoft Azure Support. Even though this information isn't required to open a case. However, it helps the support team to quickly resolve a problem.  
+ 
+> [!NOTE]
+> For more information, refer the Knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-Collect the basic data described in the Knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
 ## Data for Update Management issues on Linux
 
-1. In addition to the items that are listed in KB [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics), run the following log collection tool:
+1. Run the following log collection tool, in addition to the details in KB [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-   [OMS Linux Agent Log Collector](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/tools/LogCollector/OMS_Linux_Agent_Log_Collector.md)
+      - [OMS Linux Agent Log Collector](https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/tools/LogCollector/OMS_Linux_Agent_Log_Collector.md)
 
-2. Compress the contents of the **/var/opt/microsoft/omsagent/run/automationworker/** folder, then send the compressed file to Azure Support.
+1. Compress the contents of the **/var/opt/microsoft/omsagent/run/automationworker/** folder, and send the compressed file to Azure Support.
 
-3. Verify that the ID for the workspace that the Log Analytics agent for Linux reports to is the same as the ID for the workspace being monitored for updates.
+1. Verify that the ID for the workspace that the Log Analytics agent for Linux reports to is the same as the ID for the workspace being monitored for updates.
 
 ## Data for Update Management issues on Windows
 
 1. Collect data for the items listed in [4034605](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics).
 
-2. Export the following event logs into the EVTX format:
+1. Export the following event logs into the EVTX format:
 
    * System
    * Application
    * Security
    * Operations Manager
    * Microsoft-SMA/Operational
 
-3. Verify that the ID of the workspace that the agent reports to is the same as the ID for the workspace being monitored by Windows Updates.
+1. Verify that the ID of the workspace that the agent reports to is the same as the ID for the workspace being monitored by Windows Updates.
 
 ## Data for job issues
 
@@ -48,10 +49,13 @@ Collect the basic data described in the Knowledge Base article [4034605 - How to
    1. In the Azure portal, go to **Automation Accounts**.
    2. Select the Automation account that you are troubleshooting, and note the name.
    3. Select **Jobs**.
+
+      :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/select-jobs.png" alt-text="Screenshot showing to select jobs menu from automation account.":::
+
    4. Choose the job that you are troubleshooting.
-   5. In the Job Summary pane, look for the GUID value in **Job ID**.
+   5. In the Job Summary pane, check for the GUID value in **Job ID**.
 
-   ![Job ID within Job Summary Pane](media/collect-data-microsoft-azure-automation-case/job-summary-job-id.png)
+      :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/job-summary-job-id.png" alt-text="Screenshot Job ID within Job Summary Pane.":::
 
 3. Collect a sample of the script that you are running.
 
@@ -62,22 +66,20 @@ Collect the basic data described in the Knowledge Base article [4034605 - How to
    3. Select **Jobs**.
    4. Choose the job that you are troubleshooting.
    5. Select **All Logs**.
-   6. In the resulting pane, collect the data.
-
-   ![Data listed under All Logs](media/collect-data-microsoft-azure-automation-case/all-logs-data.png)
+      In the pane below, you can collect the data.
 
+       :::image type="content" source="./media/collect-data-microsoft-azure-automation-case/all-logs-data.png" alt-text="Screenshot of Data listed under All Logs.":::
+      
 ## Data for module issues
 
-In addition to the [basic data items](#basic-data), gather the following information:
+In addition to the knowledge Base article [4034605 - How to capture Azure Automation-scripted diagnostics](https://support.microsoft.com/help/4034605/how-to-capture-azure-automation-scripted-diagnostics), obtain the following information:
 
-* The steps you have followed, so that the problem can be reproduced.
+* The steps you followed, so that the problem can be reproduced.
 * Screenshots of any error messages.
 * Screenshots of the current modules and their version numbers.
 
 ## Next steps
 
-If you need more help:
-
 * Get answers from Azure experts through [Azure Forums](https://azure.microsoft.com/support/forums/).
 * Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience by connecting the Azure community to the right resources: answers, support, and experts.
 * File an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.