Microsoft says a regional gateway-management change contributed to a multi-region Azure connectivity disruption affecting a subset of gateway-service customers. Its incident record places the impact window from 8:30 p.m. UTC on Sept. 30 to 2:15 a.m. UTC on Oct. 1, 2026, a total of 5 hours 45 minutes. Microsoft says actual impact varied by customer and resource.
How Microsoft connects the gateway change to the disruption
Microsoft’s review says a change to a regional gateway-management service triggered higher-than-expected load while infrastructure operating-system servicing progressed gradually across multiple regions. The servicing was unrelated to the gateway-management change.
The added workload increased demand on dependent services and prevented regional services from scaling as expected. In practical terms, pressure on the gateway-management service affected the capacity of connected services to handle their work.
Affected Azure services and Microsoft’s response
Microsoft lists Azure ExpressRoute Gateway, Azure Firewall, Azure Application Gateway, Web Application Firewall, Azure VPN Gateway, and Azure VMware Solution among the affected services. Some customers experienced degraded or interrupted network connectivity, along with failures or delays in network-management operations.
Microsoft says it reverted the contributing gateway-manager change. That reduced the load and allowed affected services to recover.
