Forum Discussion

aniliri's avatar
aniliri
Copper Contributor
Feb 10, 2025

Unable to connect Azure Desktop

Yesterday I installed OPENVPN and configured it to run without user interruption, after restarting the machine unable to connect azure desktop. Under the host pool all health showing good except.

UrlsAccessibleCheck   Failed

This health check verifies that the required AVD service and Geneva URLs are reachable from the session host, including the RdTokenUri, RdBrokerUri, RdDiagnosticsUri, and storage blob URLs for Geneva agent monitoring. If this check fails, it may be fatal.

To resolve this, you'll need to reconfigure your networking, firewall, or proxy settings to unblock the following inaccessible URLs:

 607547e3-415a-4da6-bfcd-719dc9d86871.rdbroker-g-us-r1.wvd.microsoft.com

607547e3-415a-4da6-bfcd-719dc9d86871.rdbroker.wvd.microsoft.com

607547e3-415a-4da6-bfcd-719dc9d86871.rddiagnostics-g-us-r1.wvd.microsoft.com

3 Replies

  • aniliri 

    Try these steps connecting to Azure Desktop

    1. Check OpenVPN Config
      Ensure no forced gateway redirects or DNS changes blocking AVD.
    2. Bypass AVD URLs from VPN
      Run in Command Prompt (Admin)
      route add 20.190.128.0 mask 255.255.240.0 <your-gateway> -p
      route add 40.126.0.0 mask 255.255.248.0 <your-gateway> -p
    3. Allow AVD in Firewall
      Run in PowerShell (Admin)
      New-NetFirewallRule -DisplayName "Allow AVD" -Direction Outbound -Action Allow -RemoteAddress 20.190.128.0/20, 40.126.0.0/21 -Protocol Any
    4. Disable VPN & Test AVD
      Disconnect OpenVPN, restart, and check if AVD works.
    5. Enable Split Tunneling in OpenVPN
      Add these lines to .ovpn config
      route-nopull
      route 20.190.128.0 255.255.240.0 net_gateway
      route 40.126.0.0 255.255.248.0 net_gateway
      Restart OpenVPN.
    6. Restart AVD Services
      Run in PowerShell (Admin)
      Get-Service RDAgentBootLoader, RDAgent | Restart-Service
  • Take this:

     

    • Check Network Configuration: Ensure that your network configuration allows outbound traffic to the required URLs over TCP port 443. This includes checking your firewall and proxy settings.
    • Verify URL Accessibility:
      • Open Command Prompt (CMD) with administrator privileges.
      • Use the ping command to check if the URLs are reachable. For example, ping 607547e3-415a-4da6-bfcd-719dc9d86871.rdbroker.wvd.microsoft.com.
    • Update Firewall Rules: Make sure that your firewall rules are configured to allow traffic to the required URLs. You may need to add exceptions for these URLs in your firewall settings.
    • Reconfigure VPN Settings: Since you mentioned that you installed and configured OpenVPN, ensure that the VPN settings are not blocking access to the required URLs. You might need to adjust the VPN configuration to allow traffic to these URLs.
    • Restart AVD Services: Sometimes, restarting the AVD services can help resolve connectivity issues. You can do this by restarting the session host or the AVD services on the host.

Resources