Azure Front Door outage of October 29, 2025
A global outage of Microsoft's network entry service, triggered by an inconsistent configuration that a defect in deployment safeguards let spread everywhere.
Azure Front Door is the global front door of Microsoft's network: it receives user requests at edge sites, filters them and routes them to applications, both customers' and Microsoft's own. On October 29, 2025, an inconsistent configuration was pushed to those sites; the checks meant to block an invalid deployment failed to stop it because of a software defect, and a large number of nodes could no longer load. The remaining healthy nodes then took on extra load, which spread errors to regions that had been partly spared. Recovery required freezing all configuration changes and then redeploying, in phases, a version known to be good. For insurers the case matters twice over: the same layer served customers' applications and the provider's own services, including its management portal, and it happened a few days after a major outage at another large provider, a reminder that spreading workloads across two clouds only helps if the two do not fail together.
On October 29, 2025, starting at about 15:41 UTC, Microsoft 365, the Azure portal, Entra ID, Xbox and Minecraft, along with many customer websites served through Azure Front Door, became unavailable or unstable. Service returned to normal at 00:05 UTC on October 30, more than eight hours later, and Microsoft published its incident review under tracking ID YKYN-BWZ.
Follow the research
One letter a week. First, the week's underwriting note, when one is published: a dated, argued decision, signed by Paul Bernardski. Then what the observatory published on cyber risk, political risk and insurance. No account, no tracking.
No spam, one-click unsubscribe, no data ever sold.