Azure Virtual Desktop Alert: Windows App Endpoint Changes Require Action Before October

Organizations using Azure Virtual Desktop (AVD) should take note of an important upcoming change. Microsoft is transitioning the Windows App for Azure Virtual Desktop to new client-side endpoints beginning in early October. Administrators should review and update their network configurations now to ensure uninterrupted access for end users.

What’s Changing?

The Windows App will begin using 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 official list of required URLs should be added to allow lists before the rollout begins.

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 upcoming 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. Proactive testing before the October transition 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 after the rollout begins.

For organizations managing AVD environments, endpoint validation should be added to the pre-October checklist to ensure seamless authentication, resource discovery, and session connectivity.