Deploy the DNSFilter Windows Roaming Client as part of your Azure VM setup with just a few configuration updates. 

We recommend consulting Microsoft's documentation for Azure VM process details. 

✍️ Check your Azure VM policies for any automation that could remove a Gateway for any reason. If these configuration steps fail during setup or randomly go offline, our customers have found resolution by examining policy defaults and adjusting as needed.  

In order to add the Windows agent to your Azure VM environment you'll need to:

1. Add a dedicated network interface (NIC) with internet access for the agent, leaving the pre-existing NIC for Azure/Remote Desktop Protocol (RDP) access
2. Configure the two NIC's priority order to prevent DNS leaks  
   1. Windows Roaming Client NIC as the default gateway (1st priority)
   2. Rename the RDP NIC to main. While installing the Windows agent you'll add a command to ignore this NIC by using this new name
3. Install the Windows Roaming Client and Stop the agent immediately. If you miss stopping the agent before RDP connectivity stops, see the recovery methods below to fix the issue
4. Configure the agent to ignore the RDP NIC (main) as a VPN
   1. From Powershell or the VM's Registry, add main to IgnoreVPNInterfacesNames

You can now restart the Roaming Client service and the VM setup is complete.

🚨 Recovery Methods

If Windows Roaming Client is running and has removed the RDP/Azure VM connection, use Azure Serial Console to stop the agent's Windows service from command prompt.

• Azure Serial Console for Windows - Virtual Machines
• Start or stop Windows service from command line (CMD)