Use Azure Monitor for Windows Virtual Desktop to monitor your deployment

Azure Monitor for Windows Virtual Desktop is a dashboard built on Azure Monitor Workbooks that helps IT professionals understand their Windows Virtual Desktop environments. This topic will walk you through how to set up Azure Monitor for Windows Virtual Desktop to monitor your Windows Virtual Desktop environments.

Requirements

Before you start using Azure Monitor for Windows Virtual Desktop, you'll need to set up the following things:

  • All Windows Virtual Desktop environments you monitor must be based on the latest release of Windows Virtual Desktop that’s compatible with Azure Resource Manager.
  • At least one configured Log Analytics Workspace. Use a designated Log Analytics workspace for your Windows Virtual Desktop session hosts to ensure that performance counters and events are only collected from session hosts in your Windows Virtual Desktop deployment.
  • Enable data collection for the following things in your Log Analytics workspace:
    • Diagnostics from your Windows Virtual Desktop environment
    • Recommended performance counters from your Windows Virtual Desktop session hosts
    • Recommended Windows Event Logs from your Windows Virtual Desktop session hosts

The data setup process described in this article is the only one you'll need to monitor Windows Virtual Desktop. You can disable all other items sending data to your Log Analytics workspace to save costs.

Anyone monitoring Azure Monitor for Windows Virtual Desktop for your environment will also need the following read-access permissions:

  • Read-access to the Azure subscriptions that hold your Windows Virtual Desktop resources
  • Read-access to the subscription's resource groups that hold your Windows Virtual Desktop session hosts
  • Read access to the Log Analytics workspace or workspaces

Note

Read access only lets admins view data. They'll need different permissions to manage resources in the Windows Virtual Desktop portal.

Open Azure Monitor for Windows Virtual Desktop

You can open Azure Monitor for Windows Virtual Desktop with one of the following methods:

  • Go to aka.ms/azmonwvdi.
  • Search for and select Windows Virtual Desktop from the Azure portal, then select Insights.
  • Search for and select Azure Monitor from the Azure portal. Select Insights Hub under Insights, then select Windows Virtual Desktop. Once you have the page open, enter the Subscription, Resource group, Host pool, and Time range of the environment you want to monitor.

Note

Windows Virtual Desktop currently only supports monitoring one subscription, resource group, and host pool at a time. If you can't find the environment you want to monitor, see our troubleshooting documentation for known feature requests and issues.

Log Analytics settings

To start using Azure Monitor for Windows Virtual Desktop, you'll need at least one Log Analytics workspace. Use a designated Log Analytics workspace for your Windows Virtual Desktop session hosts to ensure that performance counters and events are only collected form session hosts in your Windows Virtual Desktop deployment. If you already have a workspace set up, skip ahead to Set up using the configuration workbook. To set one up, see Create a Log Analytics workspace in the Azure portal.

Note

Standard data storage charges for Log Analytics will apply. To start, we recommend you choose the pay-as-you-go model and adjust as you scale your deployment and take in more data. To learn more, see Azure Monitor pricing.

Set up using the configuration workbook

If it's your first time opening Azure Monitor for Windows Virtual Desktop, you'll need set up Azure Monitor for your Windows Virtual Desktop environment. To configure your resources:

  1. Open Azure Monitor for Windows Virtual Desktop in the Azure portal at aka.ms/azmonwvdi, then select configuration workbook.
  2. Select an environment to configure under Subscription, Resource Group, and Host Pool.

The configuration workbook sets up your monitoring environment and lets you check the configuration after you've finished the setup process. It's important to check your configuration if items in the dashboard aren't displaying correctly, or when the product group publishes updates that require new settings.

Resource diagnostic settings

To collect information on your Windows Virtual Desktop infrastructure, you'll need to enable several diagnostic settings on your Windows Virtual Desktop host pools and workspaces (this is your Windows Virtual Desktop workspace, not your Log Analytics workspace). To learn more about host pools, workspaces, and other Windows Virtual Desktop resource objects, see our environment guide.

You can learn more about Windows Virtual Desktop diagnostics and the supported diagnostic tables at Send Windows Virtual Desktop diagnostics to Log Analytics.

To set your resource diagnostic settings in the configuration workbook:

  1. Select the Resource diagnostic settings tab in the configuration workbook.
  2. Select Log Analytics workspace to send Windows Virtual Desktop diagnostics.

Host pool diagnostic settings

To set up host pool diagnostics using the resource diagnostic settings section in the configuration workbook:

  1. Under Host pool, check to see whether Windows Virtual Desktop diagnostics are enabled. If they aren't, an error message will appear that says "No existing diagnostic configuration was found for the selected host pool." You'll need to enable the following supported diagnostic tables:

    • Checkpoint
    • Error
    • Management
    • Connection
    • HostRegistration
    • AgentHealthStatus

    Note

    If you don't see the error message, you don't need to do steps 2 through 4.

  2. Select Configure host pool.

  3. Select Deploy.

  4. Refresh the configuration workbook.

Workspace diagnostic settings

To set up workspace diagnostics using the resource diagnostic settings section in the configuration workbook:

  1. Under Workspace, check to see whether Windows Virtual Desktop diagnostics are enabled for the Windows Virtual Desktop workspace. If they aren't, an error message will appear that says "No existing diagnostic configuration was found for the selected workspace." You'll need to enable the following supported diagnostics tables:

    • Checkpoint
    • Error
    • Management
    • Feed

    Note

    If you don't see the error message, you don't need to do steps 2-4.

  2. Select Configure workspace.

  3. Select Deploy.

  4. Refresh the configuration workbook.

Session host data settings

To collect information on your Windows Virtual Desktop session hosts, you'll need to install the Log Analytics agent on all session hosts in the host pool, make sure the session hosts are sending to a Log Analytics workspace, and configure your Log Analytics agent settings to collect performance data and Windows Event Logs.

The Log Analytics workspace you send session host data to doesn't have to be the same one you send diagnostic data to. If you have Azure session hosts outside of your Windows Virtual Desktop environment, we recommend having a designated Log Analytics workspace for the Windows Virtual Desktop session hosts.

To set the Log Analytics workspace where you want to collect session host data:

  1. Select the Session host data settings tab in the configuration workbook.
  2. Select the Log Analytics workspace you want to send session host data to.

Session hosts

You'll need to install the Log Analytics agent on all session hosts in the host pool and send data from those hosts to your selected Log Analytics workspace. If Log Analytics isn't configured for all the session hosts in the host pool, you'll see a Session hosts section at the top of Session host data settings with the message "Some hosts in the host pool are not sending data to the selected Log Analytics workspace."

Note

If you don't see the Session hosts section or error message, all session hosts are set up correctly. Skip ahead to set up instructions for Workspace performance counters.

To set up your remaining session hosts using the configuration workbook:

  1. Select Add hosts to workspace.
  2. Refresh the configuration workbook.

Note

The host machine needs to be running to install the Log Analytics extension. If automatic deployment doesn't work, you can install the extension on a host manually instead. To learn how to install the extension manually, see Log Analytics virtual machine extension for Windows.

Workspace performance counters

You'll need to enable specific performance counters to collect performance information from your session hosts and send it to the Log Analytics workspace.

If you already have performance counters enabled and want to remove them, follow the instructions in Configuring performance counters. You can add and remove performance counters in the same location.

To set up performance counters using the configuration workbook:

  1. Under Workspace performance counters in the configuration workbook, check Configured counters to see the counters you've already enabled to send to the Log Analytics workspace. Check Missing counters to make sure you've enabled all required counters.
  2. If you have missing counters, select Configure performance counters.
  3. Select Apply Config.
  4. Refresh the configuration workbook.
  5. Make sure all the required counters are enabled by checking the Missing counters list.

Configure Windows Event Logs

You'll also need to enable specific Windows Event Logs to collect errors, warnings, and information from the session hosts and send them to the Log Analytics workspace.

If you've already enabled Windows Event Logs and want to remove them, follow the instructions in Configuring Windows Event Logs. You can add and remove Windows Event Logs in the same location.

To set up Windows Event Logs using the configuration workbook:

  1. Under Windows Event Logs configuration, check Configured Event Logs to see the Event Logs you've already enabled to send to the Log Analytics workspace. Check Missing Event Logs to make sure you've enabled all Windows Event Logs.
  2. If you have missing Windows Event Logs, select Configure Events.
  3. Select Deploy.
  4. Refresh the configuration workbook.
  5. Make sure all the required Windows Event Logs are enabled by checking the Missing Event Logs list.

Note

If automatic event deployment fails, select Open agent configuration in the configuration workbook to manually add any missing Windows Event Logs.

Optional: configure alerts

Azure Monitor for Windows Virtual Desktop allows you to monitor Azure Monitor alerts happening within your selected subscription in the context of your Windows Virtual Desktop data. Azure Monitor alerts are an optional feature on your Azure subscriptions, and you need to set them up separately from Azure Monitor for Windows Virtual Desktop. You can use the Azure Monitor alerts framework to set custom alerts on Windows Virtual Desktop events, diagnostics, and resources. To learn more about Azure Monitor alerts, see Azure Monitor Log Alerts.

Diagnostic and usage data

Microsoft automatically collects usage and performance data through your use of the Azure Monitor service. Microsoft uses this data to improve the quality, security, and integrity of the service.

To provide accurate and efficient troubleshooting capabilities, the collected data includes the portal session ID, Azure Active Directory user ID, and the name of the portal tab where the event occurred. Microsoft doesn't collect names, addresses, or other contact information.

For more information about data collection and usage, see the Microsoft Online Services Privacy Statement.

Note

To learn about viewing or deleting your personal data collected by the service, see Azure Data Subject Requests for the GDPR. For more information about GDPR, see the GDPR section of the Service Trust portal.

Next steps

Now that you’ve configured Azure Monitor for your Windows Virtual Desktop environment, here are some resources that might help you start monitoring your environment:

  • Check out our glossary to learn more about terms and concepts related to Azure Monitor for Windows Virtual Desktop.
  • To estimate, measure, and manage your data storage costs, see Estimate Azure Monitor costs.
  • If you encounter a problem, check out our troubleshooting guide for help and known issues.