What Exactly Went Down?
Starting late on November 12, 2026, users across the globe began reporting that they couldn't access core Microsoft 365 services. The disruption primarily hit Exchange Online, the engine behind Outlook email, but the problem quickly cascaded, affecting
Microsoft Teams, SharePoint, OneDrive, and even the Copilot AI assistant. For over 20 hours, businesses, governments, and individuals in at least 74 countries faced a digital blackout, unable to send emails, join meetings, or access critical files. Downdetector, an outage tracking site, registered it as the largest service disruption of the past year. Microsoft was quick to state that the issue was not a cyberattack but a technical failure.
The Ripple Effect Across India
In India, the outage began around 11 p.m. IST on Thursday, November 12, causing widespread disruption as the corporate workday began on Friday. The country's massive IT services industry, which relies heavily on Microsoft's enterprise suite, reportedly faced a potential billing loss of around $200 million due to lost productivity and project delays. Airlines were hit hard; IndiGo and Akasa Air reported that their email support services were down, advising customers to use other channels. Air India managed to avoid major disruptions by rerouting its email systems. Employees at major multinational firms and Indian IT giants like Infosys, Accenture, and Cognizant reported slow or non-functional services, forcing some companies like Tata Motors to switch from Teams to Zoom for important calls.
The Technical Cause: A Perfect Storm
In a preliminary post-incident report, Microsoft explained the outage was caused by a trio of unfortunate events. The main culprit was a latent software bug introduced in a July 2026 update that went undetected for months. This bug was triggered when Microsoft Teams automatically failed over to the same network infrastructure used by Exchange Online, causing a sudden traffic surge. Compounding the problem was a nearly 14% reduction in server capacity from an unrelated issue the previous day. This combination created a cascading failure, overwhelming servers and causing more than 80% of its networking gateway fleet to become unresponsive at the outage's peak. The automated systems designed to prevent such issues were overwhelmed by the scale of the failure.
A Wake-Up Call for Digital India
The incident has ignited conversations about the risks of over-reliance on a small number of global tech providers. While private enterprises struggled, India's sovereign digital infrastructure showed resilience. Critical government functions, including the NIC-led government email service, e-Office file processing, and UPI payments, remained operational and unaffected by the Microsoft outage. This highlighted the strategic value of India's investment in domestically managed digital public infrastructure. Experts suggest the event serves as a critical lesson for Indian businesses to strengthen their disaster recovery plans, consider multi-cloud strategies, and diversify their technology vendors to avoid putting all their operational eggs in one basket.
The Road to Recovery
Microsoft engineers worked through Friday to resolve the crisis. Restoring services was a gradual process, as simply bringing servers back online would cause them to be immediately overwhelmed again by the backlog of traffic. The fix involved taking servers offline in batches, applying a patch, and carefully restarting them. By Saturday, November 14, Microsoft announced that services had been fully restored to all affected customers and regions. The company apologized for the significant impact the nearly 24-hour outage had on businesses and operations worldwide. A final, more detailed post-incident report is expected to follow as the company continues its investigation.
















