The First Signs of Trouble
On Thursday, November 12, 2026, reports began to trickle in, quickly becoming a flood. Users from Asia to North America found they could not access core Microsoft 365 services. Outlook mailboxes were inaccessible, Microsoft Teams became unreliable, and
other connected services like SharePoint and Copilot began to fail. According to the tracking website Downdetector, user-reported issues spiked dramatically, with over 140,000 complaints logged by Thursday evening, confirming the disruption was widespread and impacting at least 74 countries. For countless businesses and public sector organisations, the workday was thrown into chaos as essential communication and collaboration tools vanished.
The Technical Culprit Revealed
Microsoft quickly confirmed it was investigating the global incident, stating early on that there was no evidence of a malicious cyberattack. The root cause, as identified by the company's engineers, was an internal issue. A recent network configuration change, likely related to a 'Patch Tuesday' update, had gone wrong. This faulty update overwhelmed a core process responsible for establishing secure connections on its servers. As a result, a number of servers unexpectedly became unavailable, which in turn strained the remaining infrastructure as it struggled to handle the traffic. In essence, a routine update designed to improve the system had instead brought large parts of it crashing down.
A Global Scramble for a Fix
The path to recovery was not smooth. Microsoft's initial attempts to fix the problem by restarting servers and rerouting traffic did not produce the expected results; in some cases, servers brought back online were immediately swamped by the backlog of connection requests and failed again. Engineers then focused on rolling back the problematic configuration change across the company's vast global infrastructure. This was a measured, region-by-region process. While the fix was being deployed, the company extended the email timeout window to 48 hours to prevent messages from being lost permanently during the delay. Throughout the ordeal, Microsoft provided regular updates via its status pages, even as it struggled to provide a firm timeline for full restoration.
The Widespread Impact and Aftermath
The outage was one of the longest in Microsoft's recent history, with significant effects on the global economy and public services. Government agencies in Australia, Japan, the UK, and the US were disrupted. Financial trading desks in Asia resorted to using phones, WhatsApp, and even fax machines to communicate with clients and confirm trades. Airlines like Air India and Singapore Airlines reported disruptions to their customer support email channels. The incident served as a stark reminder of the world's deep reliance on a handful of major technology providers. For millions of organisations, the inability to send an email or join a virtual meeting highlighted a critical vulnerability in the architecture of modern business.
