Summary
- Environment: Microsoft 365 network gateway and Exchange Online
- Operational impact: Worldwide mailbox access and mail delivery disruption, with downstream effects in Microsoft 365 applications
- Financial impact: No financial impact quantified in the public reports
- Record status: Developing record. Reviewed November 17, 2026; updated as evidence emerges.
What happened
On November 12, 2026, a failure in a network gateway used by Microsoft 365 disrupted access to Exchange Online worldwide. Microsoft’s preliminary post-incident report dates the active disruption from 16:20 UTC on November 12 to 16:10 UTC on November 13. The company tracked the event under EX1550543 and MO1550821. [2]
Microsoft identified three contributing factors in its preliminary review. A software defect could exhaust gateway server resources under certain loads. An earlier Teams failover shifted traffic to the gateway that also served Exchange Online, and a separate issue had taken nearly 14% of that gateway’s capacity out of service. As servers stopped responding, traffic shifted to the remaining servers and put them under more strain. At the lowest point, more than 80% of the gateway servers were unresponsive. [2]
Impact
- Users had trouble accessing their Exchange Online mailboxes through Outlook and other mail clients, and email delivery slowed. Features in Teams, Copilot, SharePoint, and other services that relied on Exchange Online also experienced disruption. Impact varied by region, connection method, and time. [2]
- The University of Bath reported disruption to Outlook, Teams, its applicant CRM, and part of its service desk. [3]
- In a statement to Parliament, the UK government reported disruption in health and local government. Several local resilience forums convened to coordinate support. The UK’s 999 emergency service stayed operational. [1]
Timeline
Exchange Online disruption begins
Microsoft opened the Exchange Online service-health incident at 16:20 UTC.
[2]Microsoft confirms active impact has ended
Microsoft confirmed customer impact had ended at 16:10 UTC and moved into extended monitoring and backlog recovery.
[2]University of Bath resolves its local incident
The university marked its local incident resolved at 17:00 UTC.
[3]Microsoft posts its final customer status updates
After extended monitoring, Microsoft issued its final status updates at 04:15 UTC.
[2]Microsoft dates its preliminary post-incident report
The preliminary report details the gateway failure, service impact, and actions taken during recovery.
[2]Briefing updated
This briefing was last reviewed and updated on November 17, 2026.
Threat Group & Attack Vector
Response
Microsoft restored server capacity in stages and moved eligible traffic to other connection paths. Mailbox access improved before the email backlog cleared. Microsoft extended the mail delivery window so queued messages could still be delivered and continued monitoring after active impact ended. [2]
