MO1550821 · Service restored, root cause to follow1, 2

The Microsoft 365 outage of November 2026.

From 5:26 am AEDT on Friday 13 November, people around the world could not connect reliably to Exchange Online, the service behind Outlook mail and calendars. Teams, SharePoint, Copilot and the security and compliance tools that read mail were affected wherever they depend on it.1, 3

At 5:09 pm AEDT on Saturday 14 November, Microsoft said it had addressed the underlying issue and restored service to the remaining customers and regions.1, 2

Microsoft says there is no indication of malicious or cyber activity. It has not yet published a root cause, which its Post-Incident Report will set out.1, 2, 3

Status
Service restored
Microsoft incident
MO1550821 (Microsoft 365), EX1550543 (Exchange Online)
Started
13 Nov 2026, 5:26 am AEDT (12 Nov, 6:26 pm UTC)
Microsoft reported restored
14 Nov 2026, 5:09 pm AEDT (14 Nov, 6:09 am UTC)
Cause
Not yet published by Microsoft
Malicious activity
None known to Microsoft
Report
Post-Incident Report to follow

This page follows Microsoft’s own record of the incident. We will update it with the root cause when Microsoft publishes its Post-Incident Report.1, 2, 3

How the outage unfolded.

Times are Sydney time (AEDT). Microsoft posted an update about every hour; these are the ones that changed what was happening.3

Figure 1 · Microsoft’s updates, in Sydney time

Microsoft 365 outage timeline, 13 to 14 November 2026, in Sydney time
The turns in Microsoft’s updates on MO1550821, from the first report to service restored.1, 2, 3
  1. 4:54 am, Fri 13 Nov

    Microsoft starts investigating Exchange Online mailbox access through several connection methods, first in the Americas, as EX1550543.2

  2. 5:26 am

    MO1550821 opens across Exchange Online, the Microsoft 365 suite, Defender XDR, Teams and SharePoint Online.1, 3

  3. 6:30 am

    Microsoft pauses all deployments and configuration changes. The extra load comes from a large number of servers becoming unavailable, not from more traffic.2, 3

  4. 7:57 am

    A different health check method returns a first group of servers to service.2, 3

  5. 11:00 am

    Servers returned to service stop responding again once traffic reaches them.2, 3

  6. 12:12 pm

    Microsoft finds that a process on the servers becomes overwhelmed. It begins reverting a recent network configuration change that correlates with the start of impact.3

  7. 6:24 pm

    A patch to an upstream authentication and routing configuration component brings stable results, and is rolled out first to regions in business hours.1, 3

  8. 8:24 pm

    To protect delayed mail, Microsoft extends the email timeout to 48 hours.2

  9. 9:00 am, Sat 14 Nov

    Microsoft reports sustained recovery, keeps monitoring for an extended period, and watches the backlog of email until it all processes before it calls the incident resolved.1

  10. 5:09 pm, Sat 14 Nov

    Microsoft says it has addressed the underlying issue and restored service to the remaining customers and regions. Microsoft’s public status page no longer shows the incident.1, 2

Why it reached services beyond email.

Microsoft’s incident notice draws the line itself: features of Microsoft 365 services that interact with Exchange Online were affected, and parts that do not depend on it kept working. So a Teams call still connected while scheduling a Teams meeting failed. A file stored in SharePoint still opened, while some sharing with people outside the organisation did not.1, 3

Figure 2 · What depended on Exchange Online

Exchange Online outage and the Microsoft 365 services that depend on it
Services Microsoft lists as affected through their dependence on Exchange Online, and the parts it says kept working.1, 3

For a compliance team the list matters more than the headline. This is Microsoft’s own impact list under MO1550821, in short.1, 3

ServiceWhat Microsoft says users saw
Exchange OnlineMailboxes might not open in Outlook on the web, Outlook desktop, ActiveSync or REST connections, and mail delivery could be delayed.
Microsoft PurviewDLP across Microsoft 365, auto-labelling, communication compliance, Information Protection labels, audit search, and eDiscovery search and export may have been affected. Portal pages might not load.
Defender for Office 365Microsoft’s earlier updates listed links rewritten by Safe Links failing to open, and quarantine, Threat Explorer, email remediation and quarantine release failing.
Defender XDRDefender portal pages might not load.
CopilotCopilot Chat might not load or answer, and might not reach mail, calendar and files.
TeamsCalls, meetings, group chats and channel messages were largely unaffected. Calendar scheduling, live and virtual events, and creating private or shared channels failed.
SharePoint OnlineFiles opened. Some sharing with people outside the organisation failed.
Microsoft GraphRequests for mail, calendar and contacts could time out.
IntuneEnrolment, check-in and compliance policies may have been affected at times.
Power BI and FabricExporting or updating items with sensitivity labels could fail.
Windows 365Cloud PCs that use Purview Customer Key might not connect.
Microsoft 365 admin centerSome pages might not load.

Sources for the table1, 3

What the capacity problem looked like.

The load did not come from a rise in traffic. A large number of servers became unavailable and failed automated health checks, which pushed their work onto the servers still running.2, 3

Servers Microsoft restarted stayed healthy until traffic returned, then stopped responding again. Microsoft traced that to a process on the servers that becomes overwhelmed. Its later updates report stable results after a patch to an upstream authentication and routing configuration component.1, 2, 3

Figure 3 · The capacity loop

Microsoft 365 outage capacity loop: servers fail health checks and load shifts
The cycle Microsoft described while it returned servers to service. Our illustration, not a Microsoft diagram.2, 3

What Microsoft has and has not said about the cause.

Microsoft has not named a root cause. It says it has no evidence of malicious activity.1, 3

It began reverting a recent network configuration change that correlates with the start of impact, but has not said that change caused the outage.3

Microsoft says a Post-Incident Report will set out the root cause and the defence-in-depth repairs it is making. Where an incident has broad impact across many organisations, Microsoft’s service description commits to a preliminary Post-Incident Review within 48 hours of resolution. A final review follows within five business days.1, 4

Admins will find it under MO1550821 in Health, then Service health, in the Microsoft 365 admin center.5

Microsoft’s public status page during the outage.

Microsoft posts here when admins may not be able to reach the admin center. While the incident was open it carried the same notice as MO1550821; it no longer shows the incident.1, 5

Microsoft Service Health Status page showing Microsoft 365 service degradation
Microsoft’s Service Health Status page while the incident was open, showing service degradation for Microsoft 365 business and consumer products.1

Screenshot of status.cloud.microsoft, shown whole. © Microsoft.

What we recommend checking now service is back.

In practice, an outage like this leaves gaps that no one notices until an audit. These are our recommendations, not Microsoft’s.

  1. Confirm that DLP and auto-labelling policies processed the mail that queued during the outage. Activity explorer and the DLP alerts queue show what was matched.

  2. Re-run any audit or eDiscovery search, or export, that ran while the incident was open.

  3. Review quarantine for messages that could not be released during the outage, and links rewritten by Safe Links that users reported failing to open.

  4. Record the incident and Microsoft’s Post-Incident Report in your own incident and business continuity records.

Where Microsoft’s record is, and where the report will appear.

General information about a Microsoft service incident, from Microsoft’s own record. Not Microsoft material, and not affiliated with Microsoft.

Sources.

  1. 1 Microsoft, Service Health Status (status.cloud.microsoft)
  2. 2 Microsoft, Microsoft 365 Status on X (@MSFT365Status)
  3. 3 Microsoft, Microsoft 365 admin center, Service health, incident MO1550821 (admin sign-in required)
  4. 4 Microsoft Learn, Service health and continuity (Microsoft 365 service description)
  5. 5 Microsoft Learn, How to check Microsoft 365 service health