Announcing Required Client-Side Endpoints for AVD Windows App
Microsoft announced that the Windows App for Azure Virtual Desktop will begin utilizing three new wildcard fully qualified domain names (FQDNs) for client-side service traffic starting in early October 2026. Organizations that implement network controls on user devices must allow outbound HTTPS traffic on port 443/TCP to `*.windows.cloud.microsoft`, `*.service.windows.cloud.microsoft`, and `*.windows.static.microsoft`. Failure to configure these network endpoints could lead to sign-in, resource discovery, or connection failures for users. This change is part of a broader effort to unify Microsoft domain requirements and requires action before the specified deadline.
Notes (1) ›
- Future Required Client-Side Endpoints for Windows App
Starting early October 2026, Windows App for Azure Virtual Desktop will use three new wildcard FQDNs: `*.windows.cloud.microsoft`, `*.service.windows.cloud.microsoft`, and `*.windows.static.microsoft` for client-side traffic. Organizations must ensure outbound HTTPS traffic on port 443/TCP is allowed to these domains in firewall, proxy, VPN, DNS filtering, and Secure Web Gateway policies on user devices to prevent service disruption. This change is distinct from previous cloud-side updates.
https://azure.microsoft.com/updates?id=571360
Related releases
- Azure Application Gateway gains HTTP/3 over QUIC support in public preview Azure Updates ·
- Azure Functions runtime 1 has reached end of life endoflife.date ·
- Azure Database for MySQL 8.0 end-of-life date moved to 2027-01-31 endoflife.date ·
- Azure AI Foundry model Cohere-command-a-plus-05-2026 1 reaches end of life in 30 days endoflife.date ·
- Azure AI Foundry model o4-mini 2025-04-16 end-of-life date moved to 2026-11-19 endoflife.date ·
- Azure AI Foundry model o3-pro 2025-06-10 end-of-life date moved to 2026-11-19 endoflife.date ·