Microsoft said on November 14, 2026, that services were back after a global Microsoft 365 outage disrupted Outlook, Teams and other workplace tools. The outage began on November 12, 2026, and left businesses and public agencies unable to send email, manage calendars or use parts of their collaboration software, Reuters reported.
Microsoft blamed a technical problem in its network infrastructure. In an update reproduced by the THERS Account Help Center, the company said an earlier network-capacity upgrade had introduced a problem that surfaced after another network change. Microsoft said the outage was unrelated to a cyberattack or AI agents.
Email and collaboration tools affected
Microsoft’s incident notice MO1550821 listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot and Microsoft Defender XDR among the affected products. The THERS Account Help Center said people in the THERS organization could not send or receive organizational email, open Outlook or use some Teams and SharePoint features. It updated its notice on November 14, 2026, to say services were back.
Exchange Online is Microsoft’s cloud email and scheduling service. Reuters reported that features connected to it were particularly affected, while applications that did not depend on it kept working. Organizations running Microsoft services on their own servers were somewhat spared, and the level of disruption varied between customers.
Government agencies in Australia, Japan and the United States were affected. Reuters reported delays at trading firms and problems for companies trying to publish earnings. Airlines warned that communications could be slower. Employees across regions encountered the outage during working hours as they tried to use the same cloud tools.
Servers failed and a core process became overloaded
Microsoft found early in the outage that servers were failing unexpectedly, according to BleepingComputer’s reporting on November 12, 2026. That put more strain on the infrastructure still running. Microsoft said increased traffic had not caused the higher load.
Microsoft paused deployments, redirected connection traffic and restarted affected servers. Those steps did not immediately reduce the strain as expected. Engineers then found that a core process was becoming overwhelmed and contributing to the loss of capacity.
Microsoft also checked whether reversing recent configuration changes could restore services faster. As some servers returned, engineers routed traffic along other paths. They checked that services were stable before putting more infrastructure back into use.
Microsoft later said high demand meant it had to restore services in stages, checking stability at each stage. The company said this took longer but was intended to keep services stable during recovery.
Email delays continued as access returned
At 3:40 p.m. on November 13, 2026, Lewisham and Greenwich NHS Trust said Microsoft 365 services were beginning to return. Emails still waiting to be processed were causing intermittent service, the trust said, and replies to emails sent on November 13, 2026, might take longer.
The trust said its services were operating as usual and planned procedures were going ahead. Its update described continuing email problems while Microsoft 365 access was starting to return.
Microsoft’s update reproduced by the THERS Account Help Center said customers could regain access to applications before all accumulated messages had been processed. Email delivery and processing could therefore still be catching up after access returned. During recovery, engineers continued clearing queued messages and adjusting how traffic was distributed.
Microsoft promises a fuller report
In later updates, Microsoft said it was monitoring the email backlog and checking that its mitigation steps were still working. It also tracked unresolved problems in related products before announcing that services were back for the remaining affected customers and regions.
Microsoft said it would publish a full post-incident report once its review was complete. Its account so far identifies the network changes involved and describes the work to restore capacity and process delayed messages.
The promised report is expected to explain more fully how the outage began, which failures happened first and why it took so long to restore services.








