Azure Monitor Agent installs fail silently – extension reports success but agent not present on VM

Hello Jim Holcomb

In this scenario, the Azure Monitor Agent (AMA) VM extension shows ProvisioningState = Succeeded, but the agent is not installed inside the Windows VM, and no data is ingested into Log Analytics.

This behavior is not an Azure Monitor Agent configuration issue and is not caused by the Data Collection Rule (DCR).

Azure VM extensions (including AMA) depend entirely on the Azure Windows Guest Agent to execute installation payloads inside the guest OS.

If the Azure Windows Guest Agent is degraded or unresponsive, the following behavior is expected:

• VM extensions may report Provisioning succeeded
• Extension binaries are not installed
• In‑guest commands (RunCommand, MSI execution) do not execute
• No agent services or files are created

Azure platform does not validate successful execution inside the guest OS, only that the extension handler reported status back to Azure.

• ProvisioningState = Succeeded only means the extension handler completed
• It does not guarantee MSI installation completed
• MSI execution failures are not surfaced to the control plane

Please have a look into below remediation steps without shutting down the VM:

1. Restart Azure Guest Agent Services:

Restart-Service WindowsAzureGuestAgent -Force
Restart-Service RdAgent -Force

Restarting these services is safe and restores extension execution when the agent is in a degraded state.

2. Verify Agent Status in Portal

Navigate to:

VM → Properties → Agent status

Status must be Ready. if the agent is not Ready, extensions will not execute correctly.

3. Re‑deploy AMA After Agent Recovery:

After Guest Agent health is restored, re‑deploy the Azure Monitor Agent extension or use Azure Policy. AMA does not require VM reboot once the Guest Agent is healthy.

This issue occurs because the Azure Windows Guest Agent on the VM is degraded or unresponsive. As documented by Microsoft, when the Guest Agent cannot execute extension payloads, VM extensions including Azure Monitor Agent may report provisioning success even though the agent is not installed. Restoring Guest Agent health is required before AMA can be installed and telemetry can be ingested.

Thanks,
Suchitra.

Given the symptoms, focus on validating the AMA extension, the Azure VM Guest Agent, and the AMA processes inside the guest OS. The context supports the following checks and remediations without requiring a shutdown.

1. Verify the AMA extension is correctly present and provisioned
2. In Azure portal, open Virtual Machines → select WVDHOST-0 → Settings → Extensions + applications.
3. Confirm that an extension with type Microsoft.Azure.Monitor.AzureMonitorWindowsAgent exists.
4. Check its Status:
   • If it shows Provisioning Succeeded, proceed to Guest Agent and process checks below.
   • If it does not show Provisioning Succeeded, remove the extension and reinstall it, then re‑check the status.
   Guidance for this behavior is described in:
   • “Verify if the extension exists in the VM configuration” and “Verify the extension status”.
   • “Verify that the extension was successfully installed and provisioned”.
5. If the extension is missing or stuck, reinstall:
   • In Extensions + applications, select Add, search for AzureMonitorWindowsAgent, and install.
   • After 10–15 minutes, confirm that AzureMonitorWindowsAgent shows Provisioning succeeded.
   • If it still does not, review extension logs in C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent.
6. Verify the Azure VM Guest Agent health

Because the extension reports success but no binaries or processes are present, validate that the VM Guest Agent is actually running and able to execute extension payloads.

1. In the guest OS, open an elevated PowerShell session and run:

      Get-Service WindowsAzureGuestAgent
   

2. Confirm the Status is Running.
3. Alternatively, in Azure portal → VM → Extensions + applications, verify the Guest Health extension Microsoft.Azure.Monitor.VirtualMachines.GuestHealth.GuestHealthWindowsAgent shows Provisioning Succeeded.

If the Guest Agent service is stopped or missing, extension operations can appear successful in the portal while not actually running inside the OS. In that case, follow the guidance under “Troubleshoot the Azure Windows VM extension” to:

• Check for C:\WindowsAzure\logs\WaAppAgent.log.
  • If this log does not exist, the VM agent is not installed and must be reinstalled.
• If present, review it for Guest Agent errors.

3. Confirm AMA processes are actually running

Even if C:\Program Files\Azure Monitor Agent is missing, confirm whether any AMA processes are present (to distinguish between a pure install failure vs. a path expectation issue):

1. Connect via RDP to WVDHOST-0.
2. Open Task Manager (Ctrl+Shift+Esc) → Processes tab.
3. Look for the following processes:
   • AMAExtHealthMonitor
   • MonAgentHost
   • MonAgentLauncher
   • MonAgentManager

If all four are present and running, the agent processes have started successfully. If one or more are missing, the issue is with AMA installation or startup.

4. Use basic AMA troubleshooting steps for Windows VMs

Follow the documented basic flow for AMA on Windows:

1. Verify extension installation and provisioning:
   • As above, AzureMonitorWindowsAgent must show Provisioning succeeded under Extensions + applications.
   • If not, reinstall and then check extension logs at:
     • C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent
2. Verify the agent is running:
   • In Log Analytics, run:

          Heartbeat
          | where Category == "Azure Monitor Agent" and Computer == "<computer-name>"
          | take 10
     

   • If no results and MonAgentCore.exe is not visible in Task Manager, check core agent logs at:
     • C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration
3. Verify that the DCR exists and is associated with the VM and, if using a Log Analytics workspace, that the DCR and workspace are in the same physical region.
4. Validate that the OS and VM state support AMA
5. Confirm the OS is supported by AMA:
   • In Azure portal → VM → Overview, check Operating system and compare with the supported Windows list referenced in the AMA documentation.
6. Ensure the VM is Running; if the VM is stopped or was stopped during onboarding, extension installation can fail and need to be retried.
7. When extension shows success but binaries are missing

From the provided guidance, the most likely causes when the portal reports Provisioning Succeeded but the agent is not present are:

• The VM Guest Agent is degraded or not actually executing the extension handler, even though the extension resource state is updated.
• The extension handler ran but the internal MSI installation failed or was blocked; the failure is only visible in the extension logs and AMA logs on disk.

To differentiate and remediate without shutting down the VM:

1. Confirm Guest Agent health as in section 2 (service running, WaAppAgent.log present and without critical errors).
2. Confirm AMA extension logs exist under C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent and review them for MSI or script failures.
3. Confirm AMA data store and configuration logs under C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration and review for configuration or startup errors.
4. If logs or directories for the extension are entirely missing, this indicates the Guest Agent is not properly attempting the installation; in that case, follow the VM agent troubleshooting steps and, if necessary, open a support request with the VM support team as suggested in the Windows agent troubleshooting article.
5. Summary of recommended next steps for this VM

All steps below avoid shutting down the VM:

1. In the guest OS, verify WindowsAzureGuestAgent service is present and running; if not, repair/reinstall the Azure VM Agent per the Windows VM extension troubleshooting guidance.
2. In Azure portal, confirm Microsoft.Azure.Monitor.AzureMonitorWindowsAgent exists and shows Provisioning succeeded; if not, remove and reinstall it, then re‑check after 10–15 minutes.
3. On the VM, check:
   • C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent for extension/installer errors.
   • C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Configuration for AMA core errors.
4. In Task Manager, verify AMAExtHealthMonitor, MonAgentHost, MonAgentLauncher, and MonAgentManager are running.
5. In Log Analytics, run the Heartbeat query to confirm ingestion once processes are running.
6. If the Guest Agent is healthy but the extension log shows MSI failures that cannot be resolved, collect those logs and open a support case as recommended in the AMA troubleshooting documentation.

References:

• Troubleshooting guidance for the Azure Monitor agent on Windows virtual machines and scale sets
• Preparation for troubleshooting Azure Monitor Agent installation issues on Windows VMs
• Troubleshoot Azure Monitor Agent installation issues on Windows VMs
• Troubleshoot VM monitoring in Azure Monitor
• Troubleshoot the Log Analytics VM extension in Azure Monitor
• Resolve Windows Log Analytics Agent installation issues