Microsoft 365 Outage: Microsoft Reports Major Recovery Progress as Services Gradually Stabilize

Microsoft is reporting significant progress in restoring its Microsoft 365 services following a widespread outage that began Thursday, November 12, and continued into Friday. The disruption, which originated in Exchange Online, affected email access, calendar functions, and numerous interconnected workplace applications used by businesses and government agencies worldwide.

By Friday afternoon, recovery efforts were producing measurable improvements. Email queues were approaching normal levels, and infrastructure stability was improving across North America, Europe, and the Asia-Pacific region, according to reports from the Associated Press.

However, Microsoft has not confirmed that every affected service has returned to normal. Some users may continue to experience intermittent connectivity problems, delayed messages, or disruptions involving features dependent on Exchange Online. The distinction is important: Microsoft has made substantial progress toward restoring operations, but technical recovery does not necessarily mean every affected customer has regained full functionality.

How the Outage Spread

Microsoft's initial investigation identified a series of infrastructure problems that caused servers to become unavailable and placed additional pressure on the remaining systems. Several servers began failing automated health checks, forcing them out of service. As workloads shifted to functioning infrastructure, the resulting pressure contributed to broader connectivity failures.

Engineers subsequently identified problems involving a server process responsible for establishing secure connections. When overwhelmed, the process prevented affected servers from handling incoming requests. Microsoft also investigated recent network configuration changes and implemented corrective measures involving authentication, routing, traffic management, and server recovery.

By Friday, the company reported improved stability after applying a patch to an upstream authentication and routing component. Engineers began expanding that patch across additional infrastructure, prioritizing regions experiencing peak business activity. These findings help explain the technical failures, but Microsoft has not yet published its final root cause analysis.

Which Microsoft Services Were Affected?

The outage affected multiple Microsoft 365 products, although the extent of disruption varied according to each service's dependence on Exchange Online.

• Outlook and Exchange Online: Users experienced difficulties accessing mailboxes, sending and receiving messages, and using calendar functions. Email delivery delays remained possible during recovery.
• Microsoft Teams: Calendar integration, meeting scheduling, and other Exchange-dependent features were affected, while core messaging and online meetings remained largely functional.
• Microsoft 365 Copilot: Some users encountered difficulties loading Copilot Chat, receiving responses, or accessing connected workplace information.
• Microsoft 365 administration: Certain administrative pages, management functions, and configuration tools experienced disruptions.
• Microsoft Defender and Purview: Selected security, compliance, and data protection functions were affected.
• Microsoft Planner and To Do: Users reported reliability problems involving task management and application access.
• Microsoft Graph: API requests involving Exchange Online data, including email, contacts, and calendars, experienced failures or timeouts.
• SharePoint Online: Certain Exchange-dependent integrations were affected, although direct access to hosted files generally remained functional.

Microsoft emphasized that features operating independently of Exchange Online could continue functioning normally.

Governments and Businesses Report Disruptions

The outage affected organizations across multiple countries, demonstrating how extensively Microsoft 365 is integrated into public administration and private-sector operations. In San Francisco, some municipal employees reportedly relied on telephone calls and in-person meetings when email communications became unreliable. Singapore's government technology agency acknowledged email-related disruptions, while the Supreme Court of the Philippines reported interruptions involving certain administrative operations. Japanese authorities also experienced problems affecting government technology infrastructure.

Private-sector organizations encountered similar challenges. Workhorse Group postponed an earnings call, while Indian airline IndiGo reported problems involving its customer service email system. Flight operations continued despite those communication difficulties. Air India temporarily redirected email communications, while technology companies OpenAI and Anthropic reported difficulties involving integrations connected to Microsoft 365.

According to the Associated Press, outage reports originated from 74 countries, with Outlook complaints reaching more than 2,000 times their normal levels at the peak of the disruption. These figures reflect the extraordinary geographic reach of the incident, although outage reports do not necessarily represent unique users or complete service failures.

Microsoft Reports Significant Recovery Progress

By Friday afternoon, Microsoft was reporting improved infrastructure capacity and more stable service performance. Recovery efforts focused on several technical priorities: restoring affected servers, redistributing connection traffic, applying corrective configuration changes, and gradually returning infrastructure to normal operation. The company also expanded deployment of a patch targeting an upstream authentication and routing component after observing improved stability in the systems where it had been applied.

Email processing showed signs of improvement, with message queues approaching normal levels. Recovery was reported across major geographic regions, including North America, Europe, and Asia-Pacific. Nevertheless, Microsoft continued monitoring the infrastructure to ensure that restored servers remained stable under normal workloads. Some users could still experience delayed email delivery, intermittent access, or temporary problems with applications that depend on Exchange Online.

The remaining challenge is ensuring that recovery is sustained across Microsoft's interconnected services, rather than merely restoring individual components temporarily.

Was the Outage Caused by a Cyberattack?

Microsoft has reported no evidence indicating that malicious activity caused the incident. Its investigation has instead focused on infrastructure instability, authentication and routing components, server availability, and network configuration changes. The company has not published a final post-incident report establishing the complete sequence of technical failures.

Microsoft has indicated that a detailed report will follow mitigation, including the underlying cause and measures intended to prevent similar incidents. Until that investigation is complete, attributing the outage to a single definitive cause would be premature.

The Bigger Lesson: Cloud Reliability Requires Operational Resilience

Cloud computing has transformed how organizations communicate, collaborate, and manage essential operations. Yet the same interconnected architecture that makes these platforms efficient also introduces shared dependencies. When email, calendars, administrative tools, authentication services, and application programming interfaces rely on common infrastructure, a failure in one critical component can affect systems that initially appear unrelated.

The Microsoft 365 outage illustrates how a disruption originating in email infrastructure can extend into artificial intelligence tools, enterprise security operations, scheduling systems, and government communications. For IT administrators and business owners, the lesson is not to abandon cloud computing. It is to understand the dependencies within their technology environments and prepare for circumstances in which essential services become temporarily unavailable.

Organizations should maintain alternative communication channels, establish business continuity procedures, identify critical application dependencies, and implement safeguards for delayed transactions and messages. They should also test recovery procedures to prevent duplicate processing or data inconsistencies when interrupted systems reconnect.

Reliability is ultimately measured not only by uptime, but by how effectively an organization continues operating when something goes wrong.

A resilient technology infrastructure is not simply one that performs efficiently under normal conditions. It is one designed to respond predictably when essential components fail. For organizations increasingly dependent on cloud platforms and AI-powered productivity systems, that distinction is becoming more important.

What Happens Next?

Microsoft's immediate priority remains completing service restoration and confirming that recovered infrastructure can sustain normal traffic without additional failures. Although Friday's progress represents a substantial improvement over the conditions reported Thursday, full restoration across every affected organization has not yet been independently confirmed.

The company is also expected to publish a post-incident report explaining the technical causes, corrective actions, and preventive measures associated with the outage. The incident raises broader questions about cloud infrastructure concentration, operational redundancy, and the ability of organizations to maintain essential services when a major technology provider experiences a widespread disruption. For now, Microsoft 365 users and administrators should continue monitoring official service health advisories for information specific to their organizations.

This is a developing story. Updated November 13, 2026, at approximately 4:00 p.m. Eastern Time. Service conditions may change as recovery continues.

Sources

• Microsoft 365 Service Health — Official service health and recovery information.
• Microsoft Exchange Online Incident EX1550543 and Microsoft 365 Incident MO1550821 — Published incident updates, infrastructure findings, and mitigation measures.
• Associated Press — Microsoft global outage recovery updates — International disruptions, recovery progress, and affected organizations.
• San Francisco Chronicle — Microsoft Outlook outage — Effects on municipal operations.
• Associated Press — Worldwide Microsoft 365 disruptions — Business and public-sector impacts.