LIVE: I pieced together Microsoft's updates because they're spread across the admin centre, the public status page, X and news sites. Times are UK (UTC).
Video on what happened: https://youtu.be/GEVYLvEGEjU?is=G_sT9mB1WpBHO9Ws
Latest (22:00, 13 Nov, from Microsoft’s status page): Still not marked as fixed. Microsoft says “We continue to observe sustained service recovery across the previously affected environments.” It adds: “Due to the severity of impact this incident caused, we’re monitoring for an extended period to ensure no additional mitigative actions are required”, and it’s “monitoring the backlog of email messages accrued during this event to ensure all process successfully before considering the issue resolved.” It’s still listed as “Service degradation”. Next update due by 02:30 UK time on 14 Nov.
Cause: "a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests."
Fix so far: restarts, patches and extra capacity. An "upstream authentication/routing configuration component patch" showed "positive results" at 07:29, and recovery is now being rolled out region by region, starting with Asia Pacific.
Possible trigger: Microsoft has "begun reverting a recent network configuration change that correlates with the start of impact." It's not a confirmed root cause.
Timeline (UK time, from Microsoft's updates)
16:20, 12 Nov: Microsoft starts investigating a potential issue with mailbox access. By 18:19, Outlook is down across multiple regions.
19:18: The load "isn't driven by an increase in traffic". Servers are failing health checks and being taken out of service, which overloads the rest.
20:56: An alternative health check method brings some servers back, but at 22:00 Microsoft says "our actions taken thus far have not provided the anticipated relief."
00:00, 13 Nov: Restored servers "can become unresponsive again once they begin receiving traffic." Microsoft limits some traffic and rebuilds some servers on an older configuration.
Overnight: A process "responsible for establishing secure connections becomes overwhelmed". Microsoft reverts a network change "that correlates with the start of impact."
04:11: "there is no indication this is the result of malicious activity."
04:22: "partial recovery", but "these actions aren't resulting in sustained recovery."
06:57: Patches show "marginal success". Microsoft is adding capacity with virtual machines.
07:29: "positive results for server stability" after a patch to part of the infrastructure.
09:10: "early signs of stabilization", but capacity "has not yet returned to normal levels". The email timeout is extended to 48 hours.
10:01: "incremental improvement in several workloads", but capacity "has not yet fully returned to baseline".
11:04: Recovery done in parts of Asia Pacific. Mailbox access and delayed email are improving, but there are still intermittent issues. Fixes are being extended to other regions.
12:00: Microsoft reports encouraging recovery in Europe, North America improving, Japan more stable; intermittent issues continue, 48-hour email timeout still in place. Next update 13:00.
14:00: Service availability still improving; email queues “approaching normal levels”; intermittent access issues and delayed email still possible. Next update by 15:00.
22:00: Microsoft reports “sustained service recovery” but will keep monitoring “for an extended period” and wait for the email backlog to clear “before considering the issue resolved.”
What's affected (from MO1550821), beyond Outlook
Mail delivery may be delayed, not lost. Microsoft has extended the email timeout to 48 hours.
Teams calendar and meeting scheduling. Core chat and meetings "remain largely functional".
Safe Links "may be unable to verify URLs", so link clicks in Outlook and Teams may fail.
Purview DLP, auto-labelling and classification. Defender XDR and Purview portals may not load.
Graph calls for mail, calendar and contacts may time out, so integrations and scripts that read mailboxes will break.
Windows 365 Cloud PCs using Purview Customer Key may not connect.
Microsoft Fabric: exporting reports with sensitivity labels to PDF or PowerPoint, updating labelled items, or opening a labelled .pbix in Power BI Desktop may fail. Workaround from Microsoft: remove the label, if your data protection policies allow it.
Also Copilot, Planner, To Do, Intune, Universal Print, Power Apps, Power BI labelled PDF export, and some admin centre pages.
My reading
Early on it looked like the health check component was wrongly failing servers. It now looks like the servers really were falling over, because the secure-connections process was overwhelmed. Two things stand out. At 19:57 Microsoft said it hadn't found any recent change that correlated with the start, and overnight it started reverting one that does. And the fix that finally worked was a patch to an "upstream authentication/routing configuration component", which points at routing, not mailbox servers. That's my interpretation, not Microsoft's root cause. Wait for the PIR.
Worth doing now
Service health email alerts to at least one address outside M365: Health > Service health > Customize > Email.
The Microsoft 365 Admin app for push notifications.
Bookmark status.cloud.microsoft for when you can't get into the admin centre.
A way to tell staff about an outage when Outlook and Teams are both down.
Download the PIR when it lands. Service health only keeps 30 days of history. Graph: GET /admin/serviceAnnouncement/issues/MO1550821/incidentReport (ServiceHealth.Read.All).
What's it looking like in your tenant now?