A major Microsoft 365 outage that began on November 12 is still running on Friday morning. Microsoft tracks the Exchange Online failure as EX1550543, starting 16:17 UTC, and a wider multi-service incident, MO1550821, covering Outlook on every client, Teams calendars and scheduling, SharePoint features, Microsoft 365 Copilot, Defender, Purview, Planner, To Do and Intune. As of Microsoft's 06:17 UTC update on November 13 the status was still 'service degradation,' with only partial, unsustained recovery.
Downdetector logged roughly 120,000 to 138,000 Outlook reports at peak from more than 70 countries. Copilot's failure mode is dependency, not a model fault: with Exchange down, Copilot Chat may not load and cannot reach users' mail, calendar or files — and reporting notes third-party assistants lost the same access. Teams calls, meetings and chat largely still work; it is the Exchange-dependent pieces that broke.
Microsoft says servers became unexpectedly unavailable after automated health-check failures, that remaining infrastructure buckled under extra load, and that it is not aware of any malicious activity. It is reverting a recent network change and adding capacity, and has promised a full root-cause report once the incident closes. No restoration time has been given.
Update, November 13 midday: recovery is under way but Microsoft had not declared the incident resolved as of 14:35 UTC. At about 14:06 UTC Microsoft said service availability was continuing to improve and email queues were significantly reduced and approaching normal levels, with progress reported in Asia-Pacific and Europe and North America improving. Microsoft has extended its email timeout window to 48 hours so delayed messages stay queued instead of bouncing. Downdetector's peak was about 130,000 Outlook reports. Microsoft still reports no indication of malicious activity and no confirmed root cause, and says it will publish a full post-incident report after recovery completes.
Update, November 13 evening: the outage is mostly over after more than 24 hours. Microsoft said on Friday afternoon that it had addressed the underlying issue and was continuing to restore service to remaining customers and regions, and its service health page showed all services, including Microsoft 365 and Outlook, operational as of about 3 p.m. ET. Downdetector Outlook reports had fallen to about 1,600 by 2:50 p.m. ET, from a peak of about 130,000, and Microsoft 365 reports to about 700. Microsoft apologized for the disruption.
On cause, Microsoft now says the incident was a technical issue not related to cyber activity or AI/agents, introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. Access is recovering before mail flow fully normalizes: Microsoft says it is still draining queued messages and rebalancing traffic, gave no ETA for full recovery, and downstream trackers note queued email may take up to 24 hours to deliver. A full post-incident report is promised once the review is complete.
Update, November 14: the incident is closed. Microsoft's final update, at 04:17 UTC on November 14 (11:17 p.m. ET on November 13), marks MO1550821 and EX1550543 as service restored, with an end time of 4:10 p.m. UTC on November 13, recovery confirmed across the previously affected environments and the backlog of email messages processed. Microsoft reiterated the cause — a technical issue from an earlier network capacity upgrade that surfaced following a recent network change — and that it was not related to cyber activity or AI agents. A preliminary post-incident report is due within two business days, with a final report to follow.