Microsoft 365
Email and workplace apps · Official status page (opens in a new tab)
- 1Failures in Microsoft 365's systems
- 3Its services disrupted by failures elsewhere
- Jan 25, 2023latest Nov 12, 2026Documented since
- 0 of 1Own failures with root cause confirmed
Counts cover incidents in this archive only. They are not a complete outage history or a reliability measure.
Failures in Microsoft 365's systems
Incidents where the documented failure was in Microsoft 365's own systems. Durations are measured to the end points the sources give.
- Nov 12, 2026Microsoft 365 outage: Outlook and Exchange Online mail fails worldwideDuration: 23 h 50 minto: End of impact (Microsoft)ResolvedExchange OnlineOutlookMicrosoft Teams+1Configuration change · Root cause preliminary
Stated cause
Microsoft's final update gives a preliminary root cause of "a failure in the systems responsible for establishing secure connections to the service." An earlier update said the incident "was introduced by an issue during an earlier network capacity upgrade" that "surfaced following a recent network change." The post-incident report is not out yet.
Microsoft 365 disrupted by failures elsewhere
Microsoft 365's services were affected, but the documented failure was at another provider.
- Oct 29, 2025Azure Front Door outage: a valid customer change exposes a latent bug at the edgeDuration: 8 h 24 minto: Impact mitigatedResolvedAzure Front DoorAzure CDNAzure Portal+6Failure at Microsoft Azure · Software defect · Root cause confirmed
Stated cause
A valid customer configuration change produced incompatible metadata that "exposed a latent bug in the data plane" during asynchronous processing. Edge servers crashed, which also affected Front Door's internal DNS service. Microsoft also cites a gap in pre-production validation.
- Jul 30, 2024Azure Front Door outage: a DDoS attack exposes a network misconfigurationDuration: 2 h 13 minto: Most impact mitigatedResolvedAzure Front DoorAzure CDNAzure Portal+2Failure at Microsoft Azure · Configuration change · Root cause confirmed
Stated cause
Microsoft says a DDoS attack "was merely a trigger event." The underlying cause was that "a network misconfiguration caused congestion and packet loss for AFD frontends," starting in Europe and spreading across regions.
- Jan 25, 2023Microsoft cloud outage: one router command disrupts Azure's global networkDuration: 5 h 35 minto: Full mitigationResolvedAzure regionsMicrosoft 365Power Platform+1Failure at Microsoft Azure · Human error · Root cause confirmed
Stated cause
While adding WAN capacity in Madrid, an engineer ran a standard operating procedure that had been modified without retesting. It included a command to purge the IGP database which, on one vendor's routers, runs across all routers joined to the IGP. All routers recomputed connectivity and BGP routers re-advertised Internet prefixes. The same operation ran on a second Madrid router 33 minutes later.