Microsoft is working to restore its Microsoft 365 services after a global outage disrupted Outlook, Teams, Copilot, Word, Excel, SharePoint and OneDrive for more than 12 hours, affecting businesses, public agencies and individual users across multiple regions. The company reported early signs of improved server stability on Friday, November 13, but said service degradation was continuing and that recovery would be gradual.

The disruption began on Thursday afternoon in the United States and spread across the Asia-Pacific region before affecting users in Europe. Downdetector recorded nearly 130,000 reports of Outlook problems at the peak. Microsoft said it had no indication that the incident was caused by a cyberattack and promised a detailed post-incident report once services are fully restored.

Building 92 at Microsoft's headquarters in Redmond, Washington
Building 92 at Microsoft’s headquarters in Redmond, Washington. Photo: Coolcaesar via Wikimedia Commons, CC BY-SA 4.0. Image source · Licence.

Outage Disrupts Email, Meetings And Cloud Applications

Microsoft said the incident affected services connected to Exchange Online and email infrastructure. Users reported being unable to open Outlook inboxes, send or receive messages, join or schedule Teams meetings, and access some Microsoft 365 web applications. Copilot and other connected services also experienced problems in some regions.

The outage began shortly after midday Eastern Time on Thursday, November 12. Microsoft initially reported elevated infrastructure load and connectivity errors in multiple regions. Engineers later said some servers had become unexpectedly unavailable after failing automated health checks, reducing the amount of capacity available to handle user requests.

As traffic shifted to a smaller pool of functioning servers, the remaining infrastructure came under additional pressure. Microsoft said it was restoring affected servers in stages, moving traffic to alternative routes and applying changes intended to improve serviceability. Some early recovery measures did not work as expected, forcing engineers to examine other ways to increase capacity.

Road intersection and Microsoft campus sign at the company's Redmond campus
An intersection on Microsoft’s Redmond campus. Photo: Jonathan Schilling via Wikimedia Commons, CC BY-SA 4.0. Image source · Licence.

Microsoft Reports Early Signs Of Recovery

In an update on Friday morning, Microsoft said it was seeing positive results for server stability after applying a patch to an upstream authentication and routing component. The company said it would continue monitoring the patch and expand it to servers supporting active regions as they came back online.

That update did not amount to a full restoration. Microsoft continued to list service degradation for business, enterprise and consumer products, and warned that users could experience gradual recovery as capacity returned and clients reconnected. The company said it was not aware of malicious activity causing the incident and would publish a full root-cause analysis and details of corrective measures after mitigation.

Teams had been restored for many users in North America earlier in the incident, but Outlook and other services continued to experience disruption. The company did not provide a firm time for complete global recovery in the latest public updates available at the time of this report.

Close-up of network cables and illuminated server equipment inside a data centre
Server equipment and network cables inside a Wikimedia Foundation data centre, photographed in 2015. This is illustrative infrastructure imagery, not a Microsoft facility. Photo: Victor Grigas / Wikimedia Foundation, CC BY-SA 3.0. Image source · Licence.

Businesses, Governments And AI Tools Also Affected

The disruption extended beyond personal email. The Associated Press reported that government operations in Japan and Australia were affected, while companies in Asia struggled with internal communications and customer support. Some Indian airlines said email support channels were disrupted, although they reported that flights themselves were operating normally.

OpenAI and Anthropic also reported problems with Microsoft 365 connectors used by their AI services. Those integrations allow users to connect work data and applications to AI tools. When Microsoft’s authentication and email infrastructure became unstable, some new connections failed and existing tools did not work as expected.

The outage also affected financial and corporate workflows. The Associated Press reported that a company earnings call was delayed, while the Guardian cited examples of portfolio managers who had difficulty checking email and confirming trades. These incidents show how deeply cloud productivity systems have become embedded in everyday business operations.

Microsoft 365’s Scale Raises Questions About Resilience

Microsoft says more than 430 million people use its Microsoft 365 applications. A disruption affecting Outlook, Teams and related services therefore has consequences far beyond a single software product. Many organisations rely on Microsoft identity systems, email, document storage, calendars and collaboration tools to coordinate staff and serve customers.

Technology experts told the Guardian that a network configuration or routing problem may have triggered a cascading failure, in which unavailable servers pushed more traffic onto the remaining infrastructure. That explanation remains an expert assessment rather than Microsoft’s final root-cause finding. The company has said it will provide a full report after the incident is resolved.

The disruption has revived comparisons with the 2024 CrowdStrike outage, although the two incidents involved different systems and failure mechanisms. Microsoft’s latest incident was not reported as a cyberattack, and the company has not confirmed that a single software update caused the initial failure.

HeadlinesXtra Analysis

The Microsoft outage is a reminder that cloud convenience comes with concentration risk. When email, meetings, file storage, identity and business applications depend on a common infrastructure provider, a technical failure can affect organisations that have no direct connection to one another. The scale of the disruption is therefore not only a Microsoft reliability issue; it is also a question of how businesses design their own continuity plans.

Microsoft’s early recovery update is encouraging, but the company will need to explain why automated checks failed, how the infrastructure became overloaded and why initial recovery changes did not work as expected. A credible post-incident report should set out the technical cause, the duration and scope of the impact, the safeguards that failed and the changes being made to prevent a repeat.

For customers, the lesson is to maintain practical alternatives for critical communications and workflows. That does not mean abandoning cloud platforms, but it does mean testing backup email routes, keeping emergency contact lists outside the primary system and ensuring that essential operations can continue during a prolonged outage. The companies most prepared for the disruption will be those that treat resilience as part of daily operations rather than an emergency document that is rarely tested.

Sources And Further Reading