What Happened on November 12?
On Thursday, November 12, 2026, users from the Americas to the Asia-Pacific region began reporting widespread issues accessing Microsoft 365 services. The problems started around 4:17 PM UTC, with users finding themselves unable to connect to their Exchange
Online mailboxes. This quickly snowballed, affecting a wide range of interconnected platforms. Outage tracker Downdetector recorded a massive spike in reports, with over 130,000 people flagging issues with Outlook alone as the disruption unfolded globally. The outage stretched on for more than 16 hours for many, disrupting workdays, government services, and communications for millions of people who rely on Microsoft's ubiquitous software suite.
Which Services Were Affected?
The outage was centred on Exchange Online, the cloud infrastructure that powers Microsoft's email services. This had a direct and severe impact on Outlook, preventing users from sending, receiving, or even accessing their emails. However, due to the interconnected nature of Microsoft's ecosystem, the failure cascaded. Microsoft Teams, the vital communication and collaboration hub for countless businesses, also experienced significant connectivity problems. Other impacted services included SharePoint Online, OneDrive, Microsoft Copilot, and even the company's cybersecurity tool, Defender XDR, highlighting just how deeply integrated these platforms have become.
The Root Cause: A Server Meltdown
Microsoft quickly ruled out a malicious cyberattack as the cause of the outage. Instead, the company pointed to an internal technical failure. In statements, Microsoft explained that a large number of its servers had become unexpectedly unavailable after failing automated health checks. This sudden drop in server capacity put an immense strain on the remaining infrastructure. The elevated load overwhelmed the systems responsible for establishing secure connections, causing a domino effect that led to widespread service degradation. While the company continued to investigate the specific configuration change or update that may have triggered the initial server failures, it was clear that the issue stemmed from an internal process gone wrong, not an external threat.
The Global Impact on Business and Government
The fallout from the outage was immediate and widespread. Businesses across the globe ground to a halt as their primary communication tools failed. In India, airlines like IndiGo and Air India reported disruptions to their customer support emails. The impact was felt across critical sectors worldwide, with Britain's National Health Service (NHS) and London's Metropolitan Police reporting significant issues. Government agencies in Australia, Japan, and the United States were also affected, with some organisations forced to resort to telephones and even fax machines to conduct business. The incident served as a stark reminder of the financial cost of such downtime, which includes lost productivity, interrupted transactions, and delayed revenue, with experts estimating the global economic impact in the billions.
Microsoft's Response and What Comes Next
Microsoft's engineers worked around the clock to resolve the crisis. The company issued regular updates via its status pages and social media accounts, acknowledging the problem and detailing its recovery efforts. The primary fix involved rolling back a recent network configuration change that was suspected to be the trigger and working to safely bring the failed servers back online. By Friday, November 13, services were beginning to stabilize for many users, though intermittent issues and email backlogs remained. Microsoft has promised to release a full post-incident report detailing the root cause. For businesses and IT leaders, the event has become a critical case study, prompting urgent conversations about the risks of dependency on a single cloud provider and the need for robust contingency plans.
