Merge pull request #283266 from kainawroth/kainawroth-troubleshoot

Updating troubleshoot doc -- adding 'not' to sentence

Author: prmerger-automator[bot]

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-vm.md

@@ -12,43 +12,41 @@ ms.reviewer: jeffwo
 [!INCLUDE [azure-monitor-agent-architecture](../../../includes/azure-monitor-agent/azure-monitor-agent-architecture-include.md)]
 
 ## Basic troubleshooting steps (installation, agent not running, configuration issues)
-
 Follow the steps below to troubleshoot the latest version of the Azure Monitor agent running on your Windows virtual machine:
 
-1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**
+1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**  
 
-2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:
-    1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** from the pane on the left > 'AzureMonitorWindowsAgent'should show up with Status: 'Provisioning succeeded'
-    2. If not, check if machine can reach Azure and find the extension to install using the command below:
+2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:  
+    1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** from the pane on the left > 'AzureMonitorWindowsAgent'should show up with Status: 'Provisioning succeeded'  
+    2. If not, check if machine can reach Azure and find the extension to install using the command below:  
         ```azurecli
         az vm extension image list-versions --location <machine-region> --name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor
         ```  
-    3. Wait for 10-15 minutes as extension maybe in transitioning status. If it still doesn't show up, [uninstall and install the extension](./azure-monitor-agent-manage.md) again and repeat the verification to see the extension show up.
-    4. If not, check if you see any errors in extension logs located at `C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent` on your machine
-
-3. **Verify that the agent is running**:
+    3. Wait for 10-15 minutes as extension maybe in transitioning status. If it still doesn't show up, [uninstall and install the extension](./azure-monitor-agent-manage.md) again and repeat the verification to see the extension show up. 
+    4. If not, check if you see any errors in extension logs located at `C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent` on your machine   
+    
+3. **Verify that the agent is running**:  
     1. Check if the agent is emitting heartbeat logs to Log Analytics workspace using the query below. Skip if 'Custom Metrics' is the only destination in the DCR:
-        ```kusto
-        Heartbeat | where Category == "Azure Monitor Agent" and Computer == "<computer-name>" | take 10
+        ```Kusto
+        Heartbeat | where Category == "Azure Monitor Agent" and 'Computer' == "<computer-name>" | take 10
         ```
-    2. If not, open Task Manager and check if 'MonAgentCore.exe' process is running. If it is, wait for 5 minutes for heartbeat to show up.
-    3. If not, check if you see any errors in core agent logs located at `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration` on your machine
-
-4. **Verify that the DCR exists and is associated with the virtual machine:**
-    1. If using Log Analytics workspace as destination, verify that DCR exists in the same physical region as the Log Analytics workspace.
+    2. If not, open Task Manager and check if 'MonAgentCore.exe' process is running. If it is, wait for 5 minutes for heartbeat to show up.  
+    3. If not, check if you see any errors in core agent logs located at `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration` on your machine  
+    
+4. **Verify that the DCR exists and is associated with the virtual machine:**  
+    1. If using Log Analytics workspace as destination, verify that DCR exists in the same physical region as the Log Analytics workspace.  
     2. On your virtual machine, verify the existence of the file `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\mcsconfig.latest.xml`. If this file doesn't exist:
-        * The virtual machine may not be associated with a DCR. See step 3
-        * The virtual machine may not have Managed Identity enabled. [See here](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#enable-system-assigned-managed-identity-during-creation-of-a-vm) on how to enable.
-        * IMDS service isn't running/accessible from the virtual machine. [Check if you can access IMDS from the machine](../../virtual-machines/windows/instance-metadata-service.md?tabs=windows).
-        * AMA can't access IMDS. Check if you see IMDS errors in `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Tables\MAEventTable.tsf` file.
-    3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the virtual machine listed here
+        - The virtual machine may not be associated with a DCR. See step 3
+        - The virtual machine may not have Managed Identity enabled. [See here](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#enable-system-assigned-managed-identity-during-creation-of-a-vm) on how to enable. 
+        - IMDS service isn't running/accessible from the virtual machine. [Check if you can access IMDS from the machine](../../virtual-machines/windows/instance-metadata-service.md?tabs=windows). 
+        - AMA can't access IMDS. Check if you see IMDS errors in `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Tables\MAEventTable.tsf` file.
+    3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the virtual machine listed here  
     4. If not listed, click 'Add' and select your virtual machine from the resource picker. Repeat across all DCRs.
 
-5. **Verify that agent was able to download the associated DCR(s) from AMCS service:**
-    Check if you see the latest DCR downloaded at this location `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\configchunks`
-
+5. **Verify that agent was able to download the associated DCR(s) from AMCS service:**  
+    1. Check if you see the latest DCR downloaded at this location `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\configchunks`  
+    
 ## Issues collecting Performance counters
-
 1. Check that your DCR JSON contains a section for 'performanceCounters'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `CounterSet` nodes as shown in the example below:
@@ -63,8 +61,8 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     </CounterSet>
     ```
 
-### Issues using 'Custom Metrics' as destination
 
+### Issues using 'Custom Metrics' as destination
 1. Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).  
 2. Ensure that the associated DCR is correctly authored to collect performance counters and send them to Azure Monitor metrics. You should see this section in your DCR:
     ```json
@@ -86,7 +84,6 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
     2. Open it and look for any Level 2 errors and try to fix them.
 
 ## Issues collecting Windows event logs
-
 1. Check that your DCR JSON contains a section for 'windowsEventLogs'. If not, fix your DCR. See [how to create DCR](./azure-monitor-agent-data-collection.md) or [sample DCR](./data-collection-rule-sample-agent.md).
 2. Check that the file `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\mcs\mcsconfig.lkg.xml` exists.
 3. Open the file and check if it contains `Subscription` nodes as shown in the example below:

articles/azure-monitor/vm/vminsights-troubleshoot.md

@@ -9,17 +9,17 @@ ms.custom: references_regions
 
 ---
 
-# Troubleshoot VM insights
+# Troubleshoot VM Insights
 
 This article provides troubleshooting information to help you with problems that you might experience when you try to enable or use the VM Insights feature in Azure Monitor.
 
 ## Can't enable VM Insights on a machine
 
 When you onboard an Azure virtual machine (VM) from the Azure portal, the following actions occur:
 
-- A default Log Analytics workspace is created if you selected that option.
-- The Azure Monitor Agent is installed on the virtual machine through an extension, if the agent is already installed.
-- The Dependency Agent is installed on the virtual machine through an extension, if it's required.
+* A default Log Analytics workspace is created if you selected that option.
+* The Azure Monitor Agent is installed on the virtual machine through an extension, if the agent isn't already installed.
+* The Dependency Agent is installed on the virtual machine through an extension, if it's required.
 
 During the onboarding process, each of these steps is verified and a notification status appears in the portal. Configuration of the workspace and the agent installation typically takes 5 to 10 minutes. It takes another 5 to 10 minutes for data to become available to view in the portal.
 
@@ -155,8 +155,8 @@ Heartbeat
 
 If no data appears or if the computer didn't send a heartbeat recently, you might have problems with your agent. For agent troubleshooting information, see these articles:
 
-- [Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
-- [Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
+* [Troubleshoot issues with the Log Analytics agent for Windows](../agents/agent-windows-troubleshoot.md)
+* [Troubleshoot issues with the Log Analytics agent for Linux](../agents/agent-linux-troubleshoot.md)
 
 ## Virtual machine doesn't appear in the Map view
 
@@ -178,13 +178,13 @@ Use the log query in the [Performance view has no data](#performance-view-has-no
 
 If the virtual machine is in the **Map** view and the Dependency Agent is installed and running, but the kernel driver didn't load, check the log file at the following locations:
 
-| Operating system | Log |
-|:---|:---|
-| Windows | C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log |
-| Linux | /var/opt/microsoft/dependency-agent/log/service.log |
+| Operating system | Log                                                          |
+|:-----------------|:-------------------------------------------------------------|
+| Windows          | C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log |
+| Linux            | /var/opt/microsoft/dependency-agent/log/service.log          |
 
 The last lines of the file should indicate why the kernel didn't load. For example, the kernel might not be supported on Linux if you updated your kernel.
 
 ## Related content
 
-- For more information on installing VM Insights agents, see [Enable VM Insights overview](vminsights-enable-overview.md)
+* For more information on installing VM Insights agents, see [Enable VM Insights overview](vminsights-enable-overview.md)