A Global Standstill
On Thursday, November 12, reports began to flood in from across the globe. Users were unable to access core Microsoft 365 services. In India, the outage started being felt late on Thursday evening. By Friday morning, thousands of employees at IT firms,
financial institutions, and other businesses found themselves locked out of their primary communication tools. The disruption affected a wide array of products, including Outlook, Microsoft Teams, SharePoint, and even the AI-powered Copilot. Downdetector, an outage tracking website, registered nearly 140,000 reports at its peak, with disruptions logged across 74 countries. The impact was swift and severe, grinding productivity to a halt for countless organisations that rely on Microsoft's cloud infrastructure for daily operations.
The Primary Trigger: An Overwhelmed System
In the immediate aftermath, speculation ran wild, but Microsoft was quick to state there was no evidence of malicious activity or a cyber-attack. Instead, the primary trigger was an internal failure. According to Microsoft's own investigation, a core process responsible for establishing secure connections on its servers became overwhelmed. This led to a cascade of failures, as servers began to stop responding to requests. The problem was exacerbated when a number of servers became 'unexpectedly unavailable,' which dramatically increased the workload on the remaining infrastructure. This domino effect strained the entire system, leading to the widespread connectivity errors users experienced. In simple terms, a crucial part of the system couldn't handle its workload, causing a traffic jam so severe that it brought a significant portion of Microsoft’s global network to its knees.
The Ripple Effect in India and Beyond
The outage underscored the profound dependency of modern business on a handful of tech giants. In India, the financial services sector was hit hard, with traders struggling to access research reports and communicate with clients. Airlines including IndiGo, Air India, and Akasa Air reported disruptions to their customer email support systems. Globally, the story was the same. Government agencies in Japan, Australia, and the US were impacted. In some cases, businesses reverted to using fax machines and phone calls to conduct critical operations. The incident served as a stark reminder that when a major cloud provider falters, the ripple effects are felt across every sector, from aviation and finance to healthcare and logistics.
Microsoft's Response and the Road to Recovery
Microsoft's engineers worked urgently to resolve the crisis. The company's initial attempts to apply a fix did not proceed as expected, prolonging the disruption. Engineers then focused on rerouting traffic and bringing servers back online in a measured way to avoid further overloads. The company provided regular updates via its status pages and social media, noting that a software patch was being applied to stabilize the servers. To protect user data, Microsoft extended the email timeout window to 48 hours, ensuring that delayed messages would not be lost. By Friday, November 13, services began a slow and gradual return to normal, with Microsoft reporting 'encouraging recovery progress' and improving stability, though some intermittent issues remained as the system was fully restored.
