“Multi-region” can still mean one shared point of control.
What happened
Incompatible customer configuration metadata progressed through Azure Front Door’s protection system and triggered edge-site crashes. From 15:41 UTC on 29 October to 00:05 UTC on 30 October 2025, customers saw connection timeouts and DNS resolution problems.
The affected surface included Azure services and Microsoft 365, Dynamics 365, Entra ID, Defender, Purview, Sentinel and parts of the Azure Portal.
The boundary
Several downstream services used working failover strategies and limited their impact. Microsoft’s review also notes that some services inside the Portal had no established fallback and continued to fail after the Portal moved away from Azure Front Door.
The point
Geographic distribution does not remove a shared global configuration path. A fallback matters only if the service has built and exercised it.
Read Microsoft’s post-incident review.
More incident dossiers
- Your spare zone needs room for your failure — Google Cloud
- A cloud told 495 customers: restore from your own backups — IDC Frontier (IDCF Cloud)
- Two gateways. One shared way to fail. — Microsoft Azure
- One failed AI request became 48 more — Microsoft Azure
- One suspended account cut off three clouds — Google Cloud / Railway
- Multi-AZ did not survive the region — AWS
- Cloudflare went down, too — Cloudflare
- One empty DNS record reached across AWS — AWS
All cloud outage evidence → · Test your cloud exit readiness →