Microsoft 365 services began returning on Friday after a global outage knocked Outlook, Teams and a string of other workplace tools offline for roughly 20 hours, one of the longest disruptions to the platform in recent years.

The outage began on Thursday, November 12, at around 17:54 UTC, when users started reporting that Outlook would not load and Teams would not connect. Downdetector recorded more than 130,000 reports of Outlook problems at the peak of the incident, and Microsoft logged it under the incident codes EX1550543 and MO1550821, acknowledging the problem shortly before 1pm Eastern time.

Exchange Online, Copilot, SharePoint, Intune, Purview and Defender XDR were also affected, leaving millions of workers unable to reach email, calendars and files for much of Thursday and into Friday.

What caused the outage

Microsoft said the fault lay in a core process on affected servers that handles secure connections. The process became overwhelmed and failed its automatic health checks, and the servers left standing took on the extra load until they too became unresponsive. Engineers applied a configuration patch to an upstream authentication and routing component, then began bringing servers back online gradually, though some went unresponsive again as soon as traffic returned.

The company stressed that the incident was not a cybersecurity breach and said it had found no indication of malicious activity. A fuller root-cause account is promised once the disruption is fully resolved, and a preliminary post-incident review is typically published within 48 to 72 hours.

Recovery is under way, but not finished

Microsoft said recovery actions were completed across parts of its affected infrastructure in the Asia-Pacific region first, with broader improvements following in North America and across much of Europe. Email queues were significantly reduced and approaching normal levels by Friday evening, though the company warned some users may still face intermittent access and delayed delivery while it restores the remaining capacity.

To protect messages caught in the backlog, Microsoft extended its email timeout window to 48 hours. Independent tracker StatusGator marked the outage as ended at 13:39 UTC on Friday, 19 hours and 46 minutes after it first flagged the problem, though some users were still reporting sign-in trouble after that point.

A reminder of how much runs on one platform

The outage rippled well beyond office inboxes. Governments, airlines and hospitals were caught up in the disruption, with one London NHS trust telling staff on Friday afternoon that services were starting to come back but email would remain intermittent for several hours as queued messages cleared.

For businesses, the episode is a fresh reminder of how much daily work now depends on a single cloud platform, and how a failure in one shared component can take a whole suite of tools down with it. Microsoft said it would continue monitoring recovery and publish a detailed account of what went wrong once services are fully stable.