What Happened and Which Services Were Hit?
Starting on Thursday, November 12, users began reporting widespread issues with Microsoft 365 services. The problems originated with Exchange Online, the backend service that powers Outlook email, and quickly cascaded to other interconnected applications.
Globally, users experienced disruptions with Microsoft Teams, SharePoint Online, OneDrive, and even the AI-powered assistant, Copilot. The outage was significant, with outage tracker Downdetector logging reports from over 70 countries and territories, making it one of the largest disruptions of the year. Indian users began reporting widespread issues late on Thursday night, with problems persisting through Friday.
What Caused the Widespread Failure?
Microsoft has stated there was no evidence of a cyberattack or malicious activity behind the disruption. Instead, the company pointed to an issue stemming from a network configuration change. According to preliminary reports, a problem introduced during a previous network capacity upgrade surfaced after a more recent change was made. This caused a cascading failure where servers began failing automated health checks and went offline. The traffic from those servers then overwhelmed the remaining infrastructure, leading to a widespread inability to connect to services. The recovery process was complex, as restored servers would sometimes crash again when traffic was reintroduced.
The Ripple Effect Across India
The impact in India was immediate and widespread, affecting corporate giants, airlines, and financial services. Companies like Tata Motors had to switch from Teams to Zoom for meetings, while employees at major firms including Infosys, Accenture, and EY reported slow email and unstable connections. Airlines such as IndiGo and Akasa Air reported disruptions to their email-based customer support services. The financial sector also felt the effects, with brokerages facing delays in accessing research reports and communicating with clients, forcing a temporary reliance on telephone calls. One market intelligence firm estimated the outage may have cost India's IT services industry around $200 million due to lost billable hours and project delays.
Microsoft's Response and Restoration
Microsoft's engineers worked for over 24 hours to resolve the complex issue. The company's official status page provided regular updates, first acknowledging the problem in Exchange Online before confirming the global scale of the incident. The recovery was gradual, with the company first rerouting traffic and rolling back the problematic configuration change. Services were progressively restored through Friday, November 13, with Microsoft announcing on Saturday, November 14, that all services, including backlogs of delayed emails, had been fully restored. Puneet Chandok, President of Microsoft India and South Asia, issued an apology for the disruption caused to customers.
A Wake-Up Call for Digital India
Beyond the immediate inconvenience, the outage served as a powerful illustration of the vulnerabilities in our increasingly digital infrastructure. The incident highlighted the profound dependency of Indian businesses and digital services on a small number of global technology providers. When a single provider like Microsoft experiences a failure, it can simultaneously halt communication, collaboration, and even AI-driven workflows that are built on top of its platform. Experts suggest this event underscores the need for businesses to develop robust contingency plans, maintain alternative systems, and understand the cascading risks of having critical operations—from email and calendars to AI assistants—tied to one ecosystem.
















