In this article

The Windows Roaming Client supports Azure virtual machines (VMs). Supported VMs run Windows 10 version 22H2 or Windows 11. See support details for Windows 365 Cloud PC and other virtual environments.

Setup depends on the connection mode of the Roaming Client.

DNS PreCheck

Install the Windows Roaming Client the same way as on any other Windows device. No additional VM configuration is needed.

Classic DNS Filtering

Classic DNS Filtering sets DNS on the network interface (NIC) of the VM. A dedicated NIC for the Roaming Client keeps Azure and Remote Desktop Protocol (RDP) connectivity on a separate NIC.

To configure the VM for Classic DNS Filtering:

1. Add a dedicated NIC with internet access for the Roaming Client. 

   Keep the existing NIC for Azure and RDP access.

2. Set the NIC priority order to prevent DNS leaks, with the Roaming Client NIC as the default gateway (first priority).
3. Rename the RDP NIC to main.
4. Install the Windows Roaming Client.

5. Stop the Roaming Client service immediately. 

   If RDP access is lost before the service stops, restore RDP access through Azure Serial Console.

6. Add main to IgnoreVpnInterfacesNames using PowerShell or the registry.
7. Restart the Roaming Client service. 

Check the Azure VM policies for automation that removes a gateway. If setup fails or the VM goes offline later, review the policy defaults and adjust them as needed.

Non-persistent VMs

Non-persistent VM pools can show duplicate, offline Roaming Clients in the dashboard. Use the Clean Up Tool to keep licensing counts and user activity accurate.

Restore RDP access

If the Roaming Client is running and has blocked the RDP connection, use Azure Serial Console to stop the Roaming Client Windows service from the command prompt.