azure west us outage: a repair job cut a datacenter off the wan
A defect expanded an automated network repair to every optical device leaving one datacenter, cutting it off from Microsoft's WAN and disrupting Azure services in West US and Microsoft 365.
- tracking id
- ZJV6-SGG (Azure PIR); MO1437424 (Microsoft 365)
- impact window
- 14:44–19:41 UTC, 23 Jul 2026 (Microsoft PIR)
- root cause
- blast-radius analysis defect expanded an automated optical-device repair to all optical devices egressing one datacenter, withdrawing routes and cutting it off from the WAN
- services hit
- Azure services in West US (App Service, AKS, Cosmos DB, ExpressRoute, Firewall, VPN Gateway, Virtual Desktop and more) plus Microsoft 365
what happened
- Microsoft's post-incident review (tracking ID ZJV6-SGG) gives an impact window of 14:44–19:41 UTC on 23 July 2026 for connectivity failures and higher latency reaching resources in West US.[1]
- Only traffic entering or leaving the region was affected; traffic staying inside West US was not.[1]
- A break-fix repair on one optical device was processed automatically, and a defect in the blast-radius analysis widened it to all optical devices leaving one datacenter, cutting that datacenter off from Microsoft's WAN.[1]
- The safety check validated devices one at a time rather than their combined effect, and the automated rollback failed because it relied on the same disrupted connectivity.[1]
- Manual rollback started at 17:45 UTC and succeeded on all affected devices at 18:26 UTC.[1]
- Affected Azure services included App Service, AKS, Cosmos DB, ExpressRoute, Azure Firewall, VPN Gateway and Azure Virtual Desktop; Microsoft 365 impact was tracked as MO1437424.[1,2]
- BleepingComputer reported Microsoft 365 services including OneDrive, SharePoint Online and Teams were disrupted.[2]
sources2
- 01Post Incident Review (PIR) – Network connectivity – Issues accessing resources in West US ↗ primaryMicrosoft Azure Statusaccessed 2026-10-21
- 02Microsoft blames massive Microsoft 365 outage on maintenance bug ↗ secondaryBleepingComputeraccessed 2026-10-21