Windows Virtual Desktop uses Azure Monitor for monitoring and alerts. This lets admins identify issues through a single interface. The service creates activity logs for both user and administrative actions. Each activity log falls under the following categories:

  • Management Activities:
    • Track whether attempts to change Windows Virtual Desktop objects using APIs or PowerShell are successful. For example, can someone successfully create a host pool using PowerShell?
  • Feed:
    • Can users successfully subscribe to workspaces?
    • Do users see all resources published in the Remote Desktop client?
  • Connections:
    • When users initiate and complete connections to the service.
  • Host registration:
    • Was the session host successfully registered with the service upon connecting?
  • Errors:
    • Are users encountering any issues with specific activities? This feature can generate a table that tracks activity data for you as long as the information is joined with the activities.
  • Checkpoints:
    • Specific steps in the lifetime of an activity that were reached. For example, during a session, a user was load balanced to a particular host, then the user was signed on during a connection, and so on.

Connections that don’t reach Windows Virtual Desktop won’t show up in diagnostics results because the diagnostics role service itself is part of Windows Virtual Desktop. Windows Virtual Desktop connection issues can happen when the user is experiencing network connectivity issues.

Push diagnostics data to your workspace

Navigate to diagnostic settings from host pool and enable the diagnostic settings

Select the logs from left side and choose send to log analytics

Navigate to Application group(Desktop Application Group)

Enable the diagnostic settings and send to log analytics as shown below

Navigate to workspace diagnostics

Enable the diagnostic settings and send to log analytics as shown below

Verify the settings

To confirm if the settings are effective, Go to the log analytics workspace and check for the logs s shown below