Microsoft 365 outage: Outlook and Exchange Online mail fails worldwide
For about a day, many Microsoft 365 users could not reach their mailboxes. Microsoft's preliminary explanation points to its network and secure-connection systems; it says the incident was not cyber-related.
- Root cause:
- Preliminary
- Security:
- No evidence reported
- Started
- Nov 12, 2026, 16:20 UTC
- End of impact (Microsoft)
- Nov 13, 2026, 16:10 UTC
- Duration
- 23 h 50 min
- Full recovery
- Complete
- Geographic scope
- Global
- Last verified
- 8 sources
What happened
- Systems and services affected
- Exchange OnlineOutlookMicrosoft TeamsCopilot
- Kind of failure
- Configuration change
- Sector
- Cloud software
- Provider report
- Not yet published
- Provider incident IDs
- EX1550543, MO1550821
- Status and recovery
- Resolved. Microsoft's final update says services across the previously affected environments have fully recovered.[2][3]
Start and end are the times in Microsoft's final update, as reproduced by two third-party copies of Microsoft 365 Service health. Other sources give different start times: 10:05 UTC (header of one service-health mirror), 16:17 UTC (Azure Blog) and 17:46 UTC (a university status page). Microsoft posted the final update on November 14.
What caused it?
Root cause: PreliminaryMicrosoft'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.[2][3]
Provider report: Not yet published. Microsoft said it will share a full post-incident report with the root cause after its review. Not published as of the last verification.[3]
How the failure happened
Microsoft's preliminary statements do not yet describe how the failure spread. A diagram will be added if the post-incident report does.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
Outlook and other Microsoft 365 apps could not reach many people's mailboxes for about a day. Schools, hospitals, government offices and businesses in several countries were affected.
Microsoft says the systems that set up secure connections to its mail servers failed, after a network change exposed a problem from an earlier upgrade. Servers that Microsoft restarted failed again once they took traffic.
Microsoft says it was not a cyberattack. Its full report is still to come.
Independent analysis
Our interpretation of the sourced facts. Not a statement by the provider or officials.
Removing failing servers moves their traffic onto the remaining ones. If the underlying fault persists, those servers can fail in turn. Microsoft's updates fit this pattern, but Microsoft has not described the incident this way.
Confirmed and unknown
Confirmed
- Confirmed
Stated or reported, not confirmed
- PreliminaryPreliminary root cause: a failure in the systems responsible for establishing secure connections to the service.[2]Said by: Microsoft (final update) · Evidence: Official (copy)
- Preliminary
- ReportedMicrosoft Teams and Copilot were also disrupted.[8]Evidence: Secondary
- Reported
- PreliminaryA separate, earlier Teams incident (TM1550488, 14:45 to 15:53 UTC on November 12) had a preliminary cause of "resource contention." No link to the mail outage has been stated.[3]Said by: Microsoft · Evidence: Official (copy)
Sources disagree
- Disputed
Denied
- Denied
Still unknown
- What the network capacity upgrade and the later network change were.
- Why the secure-connection process was overwhelmed when traffic had not increased.
- Whether the health-check automation limits how many servers it can remove from service at once.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedNot documented
- AcknowledgedNov 12, 2026, 16:20 UTC
- MitigationNov 13, 2026, 01:50 UTC
- RecoveryNov 13, 2026, 16:10 UTC
- ResolvedNov 14, 2026
- Incident reportNot yet published
- Microsoft acknowledges the issue publicly on its Microsoft 365 Status social account (10:08 a.m. PT).[4]
- Microsoft reports "elevated load across multiple regions."[3]
- Microsoft: the elevated load "isn't driven by an increase in traffic."[3]
- Microsoft says no recent change lines up with the start of impact and suspects the component that processes server health checks.[3]
- Microsoft: "our actions taken thus far have not provided the anticipated relief."[3]
- MitigationMicrosoft begins reverting a recent network configuration change that correlates with the start of impact; restarts show positive results.[3]
- Microsoft: "no indication this is the result of malicious activity."[3]
- After the incident endedMicrosoft says the incident was introduced during an earlier network capacity upgrade; "not related to cyber or AI / agents."[3]
- Start to: End of impact (Microsoft)23 h 50 min
Related incidents
Links stated by providers or officials carry their evidence label. “Similar failure” is a comparison of documented causes, not a causal link.
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Primary: provider and official sources
Published by the provider or agency itself: incident reports, status records, advisories, statements.
- 1.Summary of the Amazon DynamoDB Service Disruption in the Northern Virginia (US-EAST-1) Region (opens in a new tab)Amazon Web Services · Provider report · Publication date not recorded · Accessed
Copies of official records
Third-party copies of an official record that we cannot read directly, such as a provider's admin-only status page.
- 2.EX1550543: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods (opens in a new tab)Cloud Admin Hub (mirror of Microsoft 365 Service health) · Copy of official record · Publication date not recorded · AccessedThird-party mirror of Microsoft's service health record, sourced from Microsoft's Service Communications API. Its header times (10:05 to 16:10 GMT) differ from the times in Microsoft's final update text quoted here.
- 3.Microsoft 365 outage, 12 November 2026: what happened and what admins can do (opens in a new tab)Azure Blog (azureblog.co.uk) · Copy of official record · Published · AccessedThird-party copy of Microsoft's status updates with times. The primary record (EX1550543, MO1550821) is in the Microsoft 365 admin center, which requires a tenant login.
Independent reporting
News organizations reporting statements, impact and their own findings.
- 4.Outlook Mailbox Access Problems in the Americas: Microsoft Investigates Exchange Online Incident EX1550543 (opens in a new tab)Windows Forum · News · Published · Accessed
- 5.Microsoft outage hits hospitals, GPs, schools and police across UK (opens in a new tab)The Guardian · News · Published · Accessed
- 6.Flight chaos continues as air travel attempts to get back to normal after ground stop (live updates) (opens in a new tab)NBC News · News · Published · AccessedLive blog, updated November 15, 1:01 a.m. ET. Quotes FAA Administrator Bedford, FlightAware data and a Microsoft spokesperson.
Reference and third-party analysis
Encyclopedias, aggregators and outside analysis or measurement. Used for context, not as the only support for a confirmed claim.
- 7.What Caused the Microsoft 365 Outage of November 12, 2026 (opens in a new tab)Control Plane · Third-party analysis · Publication date not recorded · Accessed
- 8.2026 Microsoft outage (opens in a new tab)Wikipedia · Reference · Publication date not recorded · Accessed
Last verified against these sources on Nov 15, 2026.