Microsoft said on Friday, November 13, that the worldwide Microsoft 365 outage that began the previous afternoon was finally in broad recovery, after nearly 24 hours in which businesses, schools, and governments struggled to reach email and the services that depend on it. The company said it had addressed the underlying issue and was seeing broad recovery and stability, while warning that it was still restoring service to remaining customers and regions and that its service health page still listed some services as unavailable.
The disruption started at about 1:00 p.m. Eastern Time on Thursday, November 12, centered on Exchange Online. Downdetector recorded more than 130,000 reports of Outlook problems at about 1:27 p.m. Eastern, according to Reuters, and Microsoft tracked the mailbox failure as incident EX1550543 and the wider impact as MO1550821. Users could not open mailboxes through Outlook on the web, desktop, or mobile, messages were delayed, and Exchange accounts reached through other clients, including Apple Mail, were also affected because the failure sat in Microsoft's underlying infrastructure.
Because so much of Microsoft 365 depends on Exchange, the effects spread well beyond email. Microsoft said features that interact with Exchange Online were affected in Teams, SharePoint Online, Microsoft 365 Copilot, and Defender XDR, along with Planner, To Do, administrative tools, and other services. Teams calling, meetings, and messaging mostly remained available, but users hit errors scheduling meetings, handling invitations, and editing calendar entries. Copilot chats could fail, and the assistant could not reliably retrieve work email, calendars, or files. Files stored directly in SharePoint remained accessible.
The scale was global. Japan confirmed a significant impact on government IT systems, and in Australia the Australian Security Intelligence Organisation and the Australian Federal Police were among the organizations affected on Friday, according to Reuters. Australia's home affairs minister said Microsoft had told him it did not believe the outage was caused by a cyber attack, and that the government had activated an agreement to ensure priority restoration of Australian services.
Microsoft apologized for the disruption and gave its clearest explanation yet on Friday. It said the incident was a technical issue not related to cyber activity or to AI agents. In its words, the incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. Earlier updates described servers failing automated health checks and becoming unavailable, leaving remaining capacity strained as traffic returned. Microsoft said it restored services gradually, validating stability at each stage, even though that approach took longer.
To protect mail that was stuck in queues, Microsoft increased the email timeout window to 48 hours while backlogs cleared, and its updates through Friday described repairs in parts of the Asia Pacific region improving mailbox access and helping delayed messages move through the system before the work extended to other regions. The company said it had found no evidence of malicious activity and promised a full post-incident report once its review is complete.
For enterprise IT teams, the incident is a reminder of how concentrated modern office infrastructure has become. A single failure in Exchange Online did not just delay email; it disrupted meeting scheduling, AI assistance, compliance and security tooling, and everyday planning tools that now assume Exchange is always there. Until Microsoft publishes its post-incident report, customers are left with a one-line cause, a gradual recovery, and a clear case for testing what their organizations can still do when their primary cloud suite goes dark for a day.