Microsoft Azure / incident
Updated 14 Sept 2026

Azure’s global front door closed

How incompatible configuration metadata caused multi-region timeouts and DNS failures across Azure Front Door.

Scope / Multiple regions; 8 hours 24 minutes

“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.