A widespread and prolonged outage of Microsoft 365 services, including Outlook, Teams, and Copilot, caused significant global disruptions throughout Thursday and Friday, November 12 and 13, 2026. The service failure impacted a vast array of essential institutions, including government agencies, hospitals, law enforcement, and transportation providers across Asia, Australasia, Europe, and North America. While Microsoft reported sustained improvements in service availability by Friday morning, the incident has reignited international debates regarding the risks associated with global reliance on a small number of dominant technology providers.
Microsoft has explicitly stated that there is no evidence to suggest the outage was the result of a cyberattack. Instead, the company’s internal investigations point to a technical failure involving server health monitoring. According to updates provided on the Microsoft 365 status dashboard, the incident originated from a specific component responsible for processing server health checks. This caused numerous servers to fail these automated checks and become unexpectedly unavailable. Consequently, the remaining infrastructure was subjected to an elevated load that, while not caused by an increase in user traffic, overwhelmed the operational machines and triggered a cascading failure across multiple data centers.
Initial attempts to resolve the issue on Thursday evening were unsuccessful, with the company noting that its recovery efforts were not yielding the expected results. The restoration process proceeded in stages, with Microsoft testing configuration changes to address the malfunctioning health-check component. By Friday, the company confirmed that it had not identified any recent system changes that correlated with the onset of the disruption, further complicating the immediate diagnosis of the root cause.
The operational impact of the outage was extensive. In Australia, medical clinics were forced to cancel scans due to an inability to access referrals, while Japanese government officials reported that staff had to revert to manual communication methods like phone calls. In the United Kingdom, police forces were unable to process online crime reports, and the National Health Service experienced significant backlogs as staff struggled to refer patients. Similar disruptions were reported by Deutsche Bahn in Germany, which faced restrictions in distributing train timetables, and by various public agencies in the Netherlands, France, Canada, and the United States.
Industry observers have noted that the scale of this disruption mirrors other historic infrastructure failures, such as the 2021 Facebook outage. The incident has drawn attention to Microsoft’s internal structure, specifically recent staffing changes. Following a series of layoffs, attrition, and buyout offers over the past year, some analysts have questioned whether the loss of institutional knowledge has impacted the company’s ability to respond to complex technical crises. Furthermore, the increasing integration of AI-generated code into Microsoft’s development pipeline has prompted speculation about the potential for unforeseen technical debt or stability issues.
In the wake of the disruption, government officials and policy experts have begun to call for a reevaluation of digital infrastructure resilience. In the United Kingdom, the chair of the Science and Technology Committee characterized the event as a warning regarding the dangers of excessive dependency on single tech giants for critical public services. These concerns are being voiced against a backdrop of shifting international relations, leading some nations to consider strategies for diversifying their digital dependencies to ensure continuity of government and essential services during future outages.





