Microsoft 365 services were disrupted around the world from November 12 into November 13, 2026. Outlook was among the most visibly affected services, alongside Teams and Copilot; recovery took place in stages, so broad improvement did not mean every customer was back online at once.
4
6
12
What happened and when
UptimeRobot’s incident tracking places the start of the outage at about 16:17 UTC on November 12, with Exchange Online mailbox access and other Microsoft 365 services affected. Reports tracked by Downdetector reached 74 countries and territories within about an hour, according to reporting by CNN and CERIAS.
1
3
7
The disruption continued overnight. On Friday, Microsoft reported progress and improving email delivery, while some customers were still experiencing problems. Nearly 24 hours after the connectivity issues began, Microsoft said it had addressed the underlying issue and was seeing broad recovery and stability as it continued restoring service.
4
12
19
Outlook, Teams and Copilot were affected—but not every feature failed
The incident hit Outlook and services dependent on Exchange Online, Microsoft’s cloud email system. Users also reported problems with Teams and Copilot. The effects varied: MacRumors reported that some Teams calling, meeting and messaging functions remained online, while users encountered errors with tasks such as scheduling meetings or adding calendar entries.
4
17
The outage also affected connected services. Claude’s status page recorded errors in Microsoft 365 connector tools and Claude for Outlook from November 12 into November 13. Reporting also described problems with Microsoft connectors used by OpenAI and Anthropic services.
24
44
What Microsoft said caused the outage
Microsoft attributed the disruption to a technical issue involving an earlier network capacity upgrade that surfaced after a later network change. The company said the incident was not related to a cyberattack or AI agents.
12
14
During the incident, Microsoft also reported that a process on affected servers responsible for establishing secure connections became overwhelmed, causing servers to stop processing requests.
37 This helps explain why problems with email and Exchange Online had consequences across multiple services that rely on those systems; it does not mean every Microsoft 365 product or feature was unavailable.
4
28
Recovery was gradual, with real-world disruption
Microsoft’s updates described recovery as an ongoing process, not a single moment when service returned for everyone. The company reported improving availability and email delivery, then broad stability, while still working to restore access for some customers and regions.
12
19
The disruption reached beyond individual inboxes. The Associated Press reported impacts on businesses and government operations from Asia to the United States. Reuters reported that some organizations turned to fax and that at least one European bond repurchase was halted.
17
40
The episode’s clearest takeaway is that failures in shared cloud infrastructure can affect many connected work tools at once. In this case, Microsoft identified a network-related technical issue, ruled out cyber and AI-agent causes, and restored service in phases over nearly a day.
12
14