Web, Payments, Bytes & Ventures

WPBV Radio

Tune into tech and money.

Microsoft Azure outage, 29 October 2025

The Microsoft Azure outage of 29 October 2025: cause, impact and fixes, from Microsoft’s own incident report.

Provider
Microsoft Azure
Date
Duration, hours
8.4
Cause
Configuration change
Regions
Global

Azure Front Door global configuration outage (29 October 2025). The disruption lasted about 8 hours 24 minutes, according to Microsoft Azure’s own timeline.

What happened. A sequence of valid customer configuration changes made across two control-plane build versions produced incompatible metadata that exposed a latent data-plane bug. Because the crash happened asynchronously, the config passed health-gated rollout stages and ‘last known good’ snapshot, then crashed edge servers globally.

What changes. Microsoft fixed the incompatibility and data-plane bug, now fully processes each config synchronously before production stages, and added rollout stages with longer bake time.

Questions

What caused the Microsoft Azure outage in October 2025?

A sequence of valid customer configuration changes made across two control-plane build versions produced incompatible metadata that exposed a latent data-plane bug.

Which services were affected?

Azure Front Door, Azure CDN, Azure Portal, App Service, SQL Database and more; Microsoft 365, Entra ID, Dynamics 365, Power Platform.

Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.

Started (UTC)
2025-10-29 15:41 UTC
Resolved (UTC)
2025-10-30 00:05 UTC
Services affected
Azure Front Door, Azure CDN, Azure Portal, App Service, SQL Database and more; Microsoft 365, Entra ID, Dynamics 365, Power Platform
Incident report
azure.status.microsoft
Sources
SourceLink
Microsoft Azure incident reporthttps://azure.status.microsoft/en-us/status/history/?trackingId=YKYN-BWZ
WPBV Radio

What are you looking for?

Search by headline, topic or keyword.