Connector for Microsoft Azure Virtual Desktop

This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to Nexthink Support.

The connector for Microsoft Azure Virtual Desktop (AVD) allows you to import device organizational information about virtual desktops, such as host pool or the type of desktop virtualization. The feature is scheduled to run automatically and communicate with an Azure app according to the configuration of the Azure portal.

Prerequisites

1. Register a new application in Azure portal.

   • During the registration process, make sure to select the Single tenant option.

   • For the Redirect URI part, using the drop-down list, select Web.

2. Assign the Desktop Virtualization Host Pool Reader role to the Service Principal of the Azure app.

3. To retrieve the disk image information, assign a role with Microsoft.Compute/virtualMachines/read permissions to the Service Principal. Assign the Virtual Machine User built-in role or create a custom role for this purpose.

4. Install the latest version of the Nexthink data collector on your virtual desktops.

Refer to Installing Collector on Windows for more information.

Device fields

The following device virtualization fields are imported.

Nexthink Field	Description
Virtualization desktop pool name	Hardware characteristics of the associated virtual machines
Virtualization desktop pool type	Type of the desktop pool. Possible values are: shared personal pooled
Virtualization hypervisor name	Hardware virtualization system which is being used. In this case, the hypervisor name will always be Azure.
Virtualization instance size	A predefined configuration that determines the CPU, memory and storage which is allocated to a virtual machine.
Virtualization region	Geographical areas where one or more Microsoft Azure data centers are located.
Environment name	Name of the connector instance which enriches the virtual device.
Desktop broker	Name of the desktop virtualization broker product being used. In this case, azure_virtual_desktop

For more information, please refer to Desktop Virtualization Optimization documentation.

Configuring the Nexthink web interface

1. Select Administration > Inbound connectors from the main menu.

2. Select Azure Virtual Desktop from the list of connectors on the Integrations page.

F.A.Q.

What is the connector for Azure Virtual Desktop used for?

To enrich Nexthink device data from Azure Virtual Desktop by importing information like the host pool or the type of desktop virtualization. This is done in order to enhance device visualization.

How do we troubleshoot the connector for Azure Virtual Desktop?

Currently, the only way to troubleshoot issues with the connector for Azure Virtual Desktop is to reach out to Nexthink support.