After running through the following troubleshooting steps and changing firewall rules, I'm still unable to get my VMs w/Azure Monitor Agent to log data into my log analytics workspace: AMA Troubleshooting Steps: Uninstall and re-install Azure Monitor Agent with user assigned managed identity Even though the agent extension showed installed, Type Handler Status showed "Not Readay" which is an indicator that the agent is not functioning properly or authentication leveraging user assigned managed identity is not functioning. Result : MonAgentCore.exe is up and running on the VM Unassociated the VMs from the Data Collection Rules re-associated them From the Azure portal, when un-associating the VMs from the DCRs, the computers did not appear to remove themselves as they still showed up in the list of VMs Had to un-associate the VMs via CLI and PowerShell by removing the Association Names from the data collection rules Waited 10 min. and in the Azure Portal, re-associated the VMs to core-01-p0-sr-wsec-dcr-001 and core-01-p0-metrics-ext-dcr-001 After 15 min., on the VM, verified the existence of C:\WindowsAzure\Resources\AMADataStore.

Azure Monitor Agent Troubleshooting

Perry Thompson 0

After running through the following troubleshooting steps and changing firewall rules, I'm still unable to get my VMs w/Azure Monitor Agent to log data into my log analytics workspace:

AMA Troubleshooting Steps:

Uninstall and re-install Azure Monitor Agent with user assigned managed identity
1. Even though the agent extension showed installed, Type Handler Status showed "Not Readay" which is an indicator that the agent is not functioning properly or authentication leveraging user assigned managed identity is not functioning.
  1. Result: MonAgentCore.exe is up and running on the VM
Unassociated the VMs from the Data Collection Rules re-associated them
1. From the Azure portal, when un-associating the VMs from the DCRs, the computers did not appear to remove themselves as they still showed up in the list of VMs
  1. Had to un-associate the VMs via CLI and PowerShell by removing the Association Names from the data collection rules
  2. Waited 10 min. and in the Azure Portal, re-associated the VMs to core-01-p0-sr-wsec-dcr-001 and core-01-p0-metrics-ext-dcr-001
  3. After 15 min., on the VM, verified the existence of C:\WindowsAzure\Resources\AMADataStore.

Silvia Wibowo 5,126 Reputation points Microsoft Employee

2025-01-14T23:43:54.8633333+00:00

Hi @Perry Thompson , how did you know that your VM still fails to use AMA (Azure Monitor Agent) to put logs into Log Analytics Workspace? Was there an error message? What sort of logs did you configure in your DCR (Data Collection Rule)? Did you try to check the logs using KQL query?
Pavan Minukuri 1,040 Reputation points Microsoft Vendor

2025-01-20T20:16:43.7666667+00:00

Hi @Perry Thompson Just checking in to see if the below answer provided by @Silvia Wibowo helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Pavan Minukuri 1,040 Reputation points Microsoft Vendor

2025-01-21T18:05:12.16+00:00

Hi @Perry Thompson , We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.

Share via

Azure Monitor Agent Troubleshooting

Your answer