# Azure product updates - 2026-09-15 **2 new update(s)** — first seen in this run. The last 7 day(s) are rescanned every time so late or backdated announcements are not missed. Grouped by Azure product category. Source: [Azure Updates](https://azure.microsoft.com/en-us/updates) ## Summary by category | Category | Updates | GA | Preview | Top products | | --- | ---: | ---: | ---: | --- | | [Compute](#compute) | 1 | - | - | Azure Virtual Desktop | | [Networking](#networking) | 1 | - | 1 | Application Gateway | ## Compute ### [Announcing: New Windows App client-side endpoints for Azure Virtual Desktop](https://azure.microsoft.com/en-us/updates?id=571360) **Status:** Effective | **Published:** 2026-09-14 | **Products:** Azure Virtual Desktop | **Tags:** Announcement Starting October 2026, Windows App for Azure Virtual Desktop will use three new wildcard client-side FQDNs to unify domain requirements, requiring organizations to update network controls to prevent connection issues. - Windows App will use *.windows.cloud.microsoft, *.service.windows.cloud.microsoft, and *.windows.static.microsoft for client-side traffic over port 443/TCP. - These domains are already included in cloud-side requirements; this update affects client-side network policies like firewall, proxy, VPN, DNS filtering, and Secure Web Gateway. - Organizations must allow outbound HTTPS traffic to these endpoints before October 2026 to avoid sign-in, connection, or session failures. - The change supports Microsoft's broader effort to unify domain requirements across Microsoft 365 and Azure Virtual Desktop services. Documentation: [Unified cloud.microsoft domain for Microsoft 365 apps - Microsoft 365 Enterprise](https://learn.microsoft.com/en-us/microsoft-365/enterprise/cloud-microsoft-domain?view=o365-worldwide) ## Networking ### [Public Preview: HTTP/3 over QUIC support in Azure Application Gateway](https://azure.microsoft.com/en-us/updates?id=571123) **Status:** In preview | **Published:** 2026-09-14 | **Products:** Application Gateway | **Tags:** Features Azure Application Gateway now publicly previews HTTP/3 over QUIC support to improve connection setup time, reduce latency, and enhance resiliency for frontend client connections, benefiting latency-sensitive workloads. - HTTP/3 over QUIC is supported on Basic listeners at the listener level, configurable via Azure portal or REST API during public preview. - Backend communication remains HTTP/1.1; IPv6 listeners, mutual authentication, WAF gateways, and Public-Private IP Same Port feature are not supported with HTTP/3 listeners. - Requires TLS 1.3 with predefined 2022 TLS policies; enabling HTTP/3 applies only to the specific listener. - Azure PowerShell, Azure CLI, and Terraform support for HTTP/3 is planned for general availability but not available during preview. Documentation: [HTTP/3 support in Azure Application Gateway - Preview](https://learn.microsoft.com/en-us/azure/application-gateway/http3-quic-support) --- _Generated automatically on 2026-09-15 01:17 UTC._