---
title: "Microsoft 365 and Exchange Online outage"
description: "A November 2026 Microsoft 365 gateway failure disrupted Outlook mailbox access, delayed email delivery, and affected features in Teams and other services."
incident_type: "Operational outage"
status: "active"
last_modified: "2026-11-17"
canonical_url: "https://www.ally.security/incidents/microsoft-365-exchange-online-outage-2026"
markdown_url: "https://www.ally.security/incidents/microsoft-365-exchange-online-outage-2026.md"
stix_url: "https://www.ally.security/incidents/microsoft-365-exchange-online-outage-2026/stix.json"
---

# Microsoft 365 and Exchange Online outage

A network gateway failure disrupted Outlook and Exchange Online worldwide and affected features in other Microsoft 365 services. Active customer impact lasted nearly 24 hours.

Last modified Nov 17, 2026 · 3 sources

## 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

## What happened

On November 12, 2026, a failure in a network gateway used by [Microsoft 365](https://www.microsoft.com/en-us/microsoft-365) disrupted access to [Exchange Online](https://www.microsoft.com/en-us/microsoft-365/exchange/exchange-online) worldwide. Microsoft's [preliminary post-incident report](https://www.365fanatic.com/wp-content/uploads/2026/11/PostIncidentReport.pdf) 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](https://mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-incidents.html?q=MO1550821). [2](#source-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](#source-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](#source-2)
- The [University of Bath](https://www.bath.ac.uk/) reported disruption to Outlook, Teams, its applicant CRM, and part of its service desk. [3](#source-3)
- In a [statement to Parliament](https://hansard.parliament.uk/commons/2026-11-16/debates/52FEDF8F-7F19-47A6-9FB7-1930054C9061/Microsoft365Outage), 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](#source-1)

## Timeline

### November 12, 2026 — Exchange Online disruption begins

Microsoft opened the Exchange Online service-health incident at 16:20 UTC. [2](#source-2)

### November 13, 2026 — 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](#source-2)

### November 13, 2026 — University of Bath resolves its local incident

The university marked its [local incident](https://status.bath.ac.uk/incident/1124080?mp=true) resolved at 17:00 UTC. [3](#source-3)

### November 14, 2026 — Microsoft posts its final customer status updates

After extended monitoring, Microsoft issued its final status updates at 04:15 UTC. [2](#source-2)

### November 15, 2026 — Microsoft dates its preliminary post-incident report

The preliminary report details the gateway failure, service impact, and actions taken during recovery. [2](#source-2)

### November 17, 2026 — Briefing updated

This briefing was last reviewed and updated on November 17, 2026.

## Threat Group & Attack Vector

Microsoft attributed the disruption to a cascading network gateway failure and reported finding no evidence of malicious activity associated with the incident. [2](#source-2) [3](#source-3)

## 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](#source-2)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/microsoft-365-exchange-online-outage-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### House of Commons statement on the Microsoft 365 outage

official · UK Parliament · Nov 16, 2026

<https://hansard-api.parliament.uk/debates/debate/52FEDF8F-7F19-47A6-9FB7-1930054C9061.json>

<a id="source-2"></a>

### Microsoft 365 November 12 outage preliminary post-incident report

official · Microsoft · Nov 15, 2026

<https://www.365fanatic.com/wp-content/uploads/2026/11/PostIncidentReport.pdf>

<a id="source-3"></a>

### Microsoft 365 global outage service updates

official · University of Bath · Nov 13, 2026

<https://status.bath.ac.uk/incident/1124080?mp=true>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Occurred At · 100% confidence · current**  
   Microsoft opens the Exchange Online service-health incident: 2026-11-12T16:20:00Z
2. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Impact varied by region, connection method and time.
3. **Affected Organization · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: University of Bath
4. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Mailbox access improved before delayed email finished processing.
5. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Many users could not access Exchange Online mailboxes through Outlook and other clients, and email delivery was delayed.
6. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: The University of Bath reported impact to Outlook, Teams, its applicant CRM and part of its service desk.
7. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: A latent defect exhausted gateway server resources under certain loads.
8. **Occurred At · 100% confidence · current**  
   Microsoft confirms active customer impact has ended: 2026-11-13T16:10:00Z
9. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: A separate issue had taken nearly 14% of gateway capacity out of service.
10. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Features relying on Exchange Online in Teams, Copilot, SharePoint and other Microsoft 365 services were affected.
11. **Occurred At · 100% confidence · current**  
   Microsoft dates its preliminary post-incident report: 2026-11-15
12. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Microsoft recovered capacity in stages and moved eligible traffic to alternative connection paths.
13. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Microsoft extended the mail delivery window to process queued messages.
14. **Began At · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: 2026-11-12T16:20:00Z
15. **Occurred At · 100% confidence · current**  
   Microsoft issues its final customer status updates: 2026-11-14T04:15:00Z
16. **Ended At · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: 2026-11-13T16:10:00Z
17. **Occurred At · 100% confidence · current**  
   University of Bath marks its local incident resolved: 2026-11-13T17:00:00Z
18. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: The UK government reported disruption in health and local government and said local resilience forums convened to coordinate support. The 999 emergency service continued to operate.
19. **Affected Organization · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Microsoft
20. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Earlier Teams failover shifted load to the gateway that also supported Exchange Online.
21. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Microsoft reported no evidence of malicious activity associated with the incident.
22. **Resulted In · 100% confidence · current**  
   Microsoft 365 and Exchange Online outage: Traffic shifted to remaining servers as others became unresponsive, causing a cascade. More than 80% of gateway servers were unresponsive at the lowest point.

</details>
