Enable VM Insights on a Windows client machine

For Windows 10 and 11 client machines that are always powered on and connected to the internet, use Azure Arc for servers and follow the same process as enabling VM insights on Azure VMs.

This article describes how to enable VM Insights on a Windows client machine that's online intermittently and not managed using Azure Arc.


  • Log Analytics workspace.
  • A Windows device that's domain joined to your Microsoft Entra tenant. The device must be able to connect to the internet.
  • See Supported operating systems to ensure that the operating system of the virtual machine or virtual machine scale set you're enabling is supported.

Firewall requirements

  • For Azure Monitor Agent firewall requirements, see Define Azure Monitor Agent network settings.
  • The VM Insights Map Dependency agent doesn't transmit any data itself, and it doesn't require any changes to firewalls or ports.

Azure Monitor Agent transmits data to Azure Monitor directly or through the Log Analytics gateway if your IT security policies don't allow computers on the network to connect to the internet.


  • The data collection rules you create for Windows client machines can only target the entire Microsoft Entra tenant scope. That is, a data collection rule you associate to a monitored object applies to all Windows client machines on which you install Azure Monitor Agent using this client installer within the tenant. Granular targeting using data collection rules is not supported for Windows client devices yet.
  • Azure Monitor Agent doesn't support monitoring of Windows machines connected via Azure private links.
  • The agent installed using the Windows client installer is designed mainly for Windows desktops or workstations that are always connected. Although you can install Azure Monitor Agent on laptops using the installer, the agent isn't optimized for battery consumption and network limitations on a laptop.

Deploy VM Insights data collection rule and install agents

To enable VM Insights on a Windows client machine:

  1. If you don't have an existing VM Insights data collection rule, deploy a VM Insights data collection rule using ARM templates. The data collection rule must be in the same region as your Log Analytics workspace.

  2. Follow the steps described in Install Azure Monitor Agent on Windows client devices to:

    • Install Azure Monitor Agent on your machine using the client installer.
    • Create a monitored object.
    • Associate the monitored object to your VM Insights data collection rule.

    The monitored object automatically associates your VM Insights data collection rule to all Windows devices in your tenant on which you install the Azure Monitor Agent using the client installer.

  3. To use the Map feature of VM Insights, install Dependency Agent on your machine manually.


This section offers troubleshooting tips for common issues.

Machine doesn't appear on the map

If your Dependency agent installation succeeded but you don't see your computer on the map, diagnose the problem by following these steps:

  1. Is the Dependency agent installed successfully? Check to see if the service is installed and running. Look for the service named "Microsoft Dependency agent."

  2. Are you on the Free pricing tier of Log Analytics? The Free plan allows for up to five unique computers. Any subsequent computers won't show up on the map, even if the prior five are no longer sending data.

  3. Is the computer sending log and performance data to Azure Monitor Logs? Run this query for your computer:

    Usage | where Computer == "computer-name" | summarize sum(Quantity), any(QuantityUnit) by DataType

    Did it return one or more results? Is the data recent? If so, the agent is operating correctly and communicating with the service. If not, check the agent on your server. See Troubleshooting Azure Monitor Agent on Windows virtual machines and scale sets or Log Analytics agent for Linux troubleshooting.

Machine appears on the map but has no processes

You see your server on the map, but it has no process or connection data. In this case, the Dependency agent is installed and running, but the kernel driver didn't load.

Check the C:\Program Files\Microsoft Dependency Agent\logs\wrapper.log file . The last lines of the file should indicate why the kernel didn't load.

Next steps

Now that monitoring is enabled for your virtual machines, this information is available for analysis with VM Insights.