A Microsoft 365 outage that began on Thursday afternoon, US Eastern time, left tens of thousands of users unable to reach Outlook and other Microsoft services. Microsoft attributed the problem to servers becoming unexpectedly unavailable, and said that restored servers could fail again once traffic returned.

What happened

According to ABC7 Los Angeles, citing the Associated Press, reports on the outage tracker Downdetector spiked just after 1 p.m. Eastern on 12 November, which is about 18:00 UTC. Tom's Guide's live blog recorded about 119,000 Outlook reports at 18:49 UTC and a peak of about 130,000. ABC7 also cites nearly 130,000 users reporting trouble reaching Outlook. Downdetector counts are user reports, not a measure of affected accounts, and they tend to fall as people stop reporting, as the Tom's Guide author noted.

ABC News described the disruption as stretching on "for hours" on Thursday. New York City's Emergency Management Department warned of possible delays in email and online city services that rely on Microsoft systems, ABC News reported, and advised residents to call 311 for non-emergency services or 911 for emergencies.

Which services were affected

Microsoft's status posts, as relayed by Tom's Guide, listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. ABC7, citing Microsoft's status page, adds Planner, To Do, Intune and Defender for Office 365 as possibly affected. Users also reported problems with OneDrive access and Office online, according to Tom's Guide. That outlet noted that Gmail, Zoom and Yahoo Mail also showed problems on Downdetector but were not affected by the Microsoft outage itself.

Microsoft's incident references in the admin center were EX1550543 and MO1550821, per Tom's Guide. Administrators can use these to track updates, but they are visible only to tenant admins.

What Microsoft has said about the cause

Microsoft's explanation changed as the incident developed, which is normal in a live outage. As reported:

  • First: "elevated load across multiple regions," tied to connectivity errors on part of its infrastructure.
  • Then: the load was not extra traffic but a "number of servers being unexpectedly unavailable," per ABC News and ABC7.
  • Later: failed health checks, possibly involving a component that processes server health, according to Tom's Guide. Microsoft said it had not identified a correlated recent change.
  • Also reported: ABC7 says Microsoft described a process that establishes secure connections becoming overwhelmed, which caused servers to stop processing requests.

These descriptions overlap but are not the same, and none is a final root cause. Microsoft has typically published a post-incident review after major outages; we have not seen one for this incident.

What Microsoft did to fix it

Tom's Guide and ABC News report these steps, in rough order: redistributing connection traffic (about 19:00 UTC), pausing deployments and configuration changes (about 19:35 UTC), testing a configuration change and restarting affected servers (about 20:00 UTC), and validating an alternative health-check method on a subset of servers (about 21:30 UTC). Many servers became unresponsive around 20:49 UTC, which delayed validation.

Microsoft acknowledged that some actions did not provide the "anticipated relief," according to ABC News. By around 6 p.m. Eastern it was returning a portion of affected servers to service and said they remained stable so far. It then warned that servers "can become unresponsive again once they receive traffic" and limited traffic to affected infrastructure in some locations. Tom's Guide says Microsoft reported restoring an earlier Teams issue.

Where things stand

Tom's Guide's last update, at about 03:04 UTC on 13 November, showed more than 25,000 Outlook reports on Downdetector, down from the peak but not zero, and described services as partially recovering and not fully resolved. ABC7's last update, around 02:02 GMT, said repairs were underway and that Microsoft reported "positive results" restarting servers. Because the picture was still moving when these pages were captured, anyone reading this should check Microsoft's own service health page and its Microsoft 365 Status account on X for the current state.

Why this kind of outage matters to businesses

Email and collaboration tools are now a single point of failure for many organisations, and the impact is not only inconvenience. The New York City advisory shows that public services can depend on a commercial email platform. Several practical points follow, all general advice and not specific to this incident:

  • Have an out-of-band channel. Teams and Outlook failing together can leave staff without their normal way of coordinating. A pre-agreed alternative, such as a phone tree or a separate messaging tool, avoids improvising.
  • Expect repeat failures during recovery. Microsoft itself warned restored servers could fail again. Treat the first hour of "back to normal" with caution before resuming critical sends.
  • Check for delayed mail. After a mail outage, messages may arrive late or in bursts, so time-sensitive items sent during the window are worth re-confirming.
  • Security tools can be affected too. Defender XDR was among the services Microsoft listed, so security teams may have had reduced visibility for part of the incident. We have no report of a security consequence.

Not the first, but different

Our searches returned headlines about earlier Microsoft 365 outages, including one dated 22 January 2026 and one on 31 August 2026. We did not open those pages and do not compare causes or durations. The point is limited: large cloud platforms fail periodically, and the right preparation is the same each time.


Corrections and updates

Nexuswild welcomes factual corrections. Email contact@nexuswild.com with evidence and the article URL.