Azure Virtual Desktop Alert: Windows App Endpoint Changes Are Now in Effect — What to Check
Organizations using Azure Virtual Desktop (AVD) should take note of an important change that is now in effect. Microsoft has transitioned the Windows App for Azure Virtual Desktop to new client-side endpoints. Administrators who have not yet updated their network configurations should review and update them now to ensure uninterrupted access for end users.
What’s Changing?
The Windows App now uses new client-side endpoints for Azure Virtual Desktop connectivity. As part of this transition, organizations must ensure that the required endpoints are permitted through all security and networking controls over TCP port 443 (HTTPS).
This includes reviewing configurations for:
- Firewalls
- Proxy servers
- VPN solutions
- Secure Web Gateways (SWG)
- Web filtering platforms
- Zero Trust access solutions
- Endpoint security products with network filtering capabilities
The required endpoints are listed in the next section — add them to your allow lists if you have not already.
The endpoints to allow
Allow these outbound over TCP 443 through every firewall, proxy, VPN, Secure Web Gateway and endpoint filter on the path. The full list lives in Microsoft Learn — Required FQDNs and endpoints for Azure Virtual Desktop:
| Endpoint | Port | What it carries |
|---|---|---|
*.wvd.microsoft.com |
TCP 443 | Service traffic, including TCP-based RDP connectivity |
login.microsoftonline.com |
TCP 443 | Authentication to Microsoft Online Services |
*.windows.cloud.microsoft |
TCP 443 | Service traffic (Windows App) |
*.service.windows.cloud.microsoft |
TCP 443 | Service traffic (Windows App) |
*.windows.static.microsoft |
TCP 443 | Service traffic (Windows App) |
Why This Matters
Failure to allow the new endpoints could result in several user-facing issues, including:
Authentication Failures
Users may be unable to authenticate successfully through the Windows App, preventing access to Azure Virtual Desktop resources.
Resource Discovery Problems
Published desktops and applications may not appear correctly, leaving users unable to locate the resources they need.
Connection Issues
Users could experience failed connections, launch errors, or session instability when attempting to access virtual desktops and remote applications.
Increased Support Requests
Organizations that do not prepare ahead of time may see an increase in help desk tickets related to AVD access and connectivity issues.
Recommended Actions for IT Administrators
To ensure a smooth transition:
✅ Review Microsoft’s published endpoint requirements.
✅ Update firewall and proxy allow lists.
✅ Verify VPN and Secure Web Gateway policies.
✅ Test connectivity from different locations and network segments.
✅ Notify support teams and service desks about the change.
✅ Validate functionality with a pilot group before broad deployment.
Best Practice
If your organization uses strict outbound filtering or URL-based restrictions, now is the ideal time to confirm that all required Azure Virtual Desktop endpoints are allowed. Testing the endpoints above now can help avoid downtime, user frustration, and reactive troubleshooting efforts.
Final Thoughts
Azure Virtual Desktop remains a critical platform for enabling secure remote work. Keeping networking requirements current is essential for maintaining a reliable user experience. Taking a few minutes today to review the new endpoint requirements can save hours of troubleshooting.
For organizations managing AVD environments, endpoint validation should be part of the standard checklist to ensure seamless authentication, resource discovery, and session connectivity.