azure monitor VMinsights say:Cannot enable - Unable to determine if OS is supported (Why?)

Question

In two different customer environments, we have activate Azure Arc, installed the Agent on a Windows Server (2016 - 2025), installed the AMA-agent and the responsible DCR. Now we think about to monitor more detail the sevrer and want to enable VMsights. But all System under the register "not monitored" we found this information near the device: Cannot enable - Unable to determine if OS is supported(Why?)

I have already GA rights and for the subscription I'm the owner. Have anyone an Idea what happened?

Answer 1

Hello Lux, Carsten

Thank you for posting your query on Microsoft Q&A platform.

"Cannot enable – Unable to determine if OS is supported” message in VM Insights is not related to permissions or the Windows Server version. This behavior occurs when Azure Monitor cannot validate the guest OS because the required agent telemetry is not being reported, even though the agents appear installed.

For Azure Arc–enabled servers, VM Insights relies on Azure Monitor Agent (AMA) runtime data to confirm OS support. If AMA (or the Dependency Agent, if Maps were previously enabled) is installed but not fully operational, VM Insights cannot complete this validation and leaves the machine in a Not monitored state.

VM Insights onboarding requires:

• Azure Monitor Agent to be successfully installed and running
• Extensions to fully initialize and report telemetry, not just show “provisioned”
• Outbound connectivity to Azure Monitor endpoints

If OS inventory or health data is not received from the agent, the portal displays this exact message, even when the OS itself is supported.

As a resolution, please try below workarounds:

1. Remove the existing extensions from the Arc‑enabled server:
   • AzureMonitorWindowsAgent
   • DependencyAgentWindows (if present)
   Reinstall the Azure Monitor Agent and confirm the extension status is Succeeded Re‑enable VM Insights from the Azure Arc server’s Insights blade, which recreates and associates the required Data Collection Rule automatically

This process forces fresh agent registration and restores OS detection.

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

Answer 2

The error message "Cannot enable - Unable to determine if OS is supported" typically indicates that the operating system of the virtual machine is not recognized as supported by Azure Monitor for VM Insights. Here are a few potential reasons why this might occur:

1. Unsupported Operating System: Ensure that the operating system version you are using is listed in the supported operating systems for Azure Monitor Agent. While you mentioned Windows Server 2016-2025, it's important to verify that the specific build and edition are supported.
2. Agent Installation Issues: If the Azure Monitor Agent (AMA) or the Dependency Agent is not installed correctly, it may lead to this error. You can check the Extensions pane in the Azure portal to verify if the required agents are installed and their status.
3. Configuration Issues: There may be issues with the Data Collection Rule (DCR) configuration that could prevent the system from being monitored. Ensure that the DCR is correctly set up and associated with the virtual machine.
4. Permissions: Although you mentioned having GA rights and being the owner of the subscription, double-check that there are no additional permissions required for enabling VM Insights on the specific virtual machines.
5. Time for Onboarding: After enabling VM Insights, it may take some time for the system to recognize the OS and complete the onboarding process. If you have just enabled it, consider waiting a bit longer and checking again.

If these steps do not resolve the issue, further investigation may be required, including checking logs or contacting Azure support for assistance.

---

References:

• Troubleshoot VM insights
• Enable VM Insights