Microsoft has finally declared all its major services operational again. After more than a day and a half of chaos that began around midday Thursday (US time) on 12 November 2026, the company’s service health page now shows “All products are operational” for Microsoft 365, Outlook, Teams, Copilot, and related tools. The company says it has fixed the underlying problem and restored access for the remaining affected customers and regions. Residual email backlogs are still being cleared, and a full post-incident report is promised later.
The disruption lasted longer than most recent Microsoft failures. Peak reports on Downdetector crossed 130,000 for Outlook alone, with problems recorded across more than 70 countries. Businesses, airlines, courts, healthcare systems and government offices were hit. Exchange Online was the epicenter. Servers began failing automated health checks after a network capacity upgrade and subsequent configuration change. The remaining servers were overloaded, creating a cascading failure. Microsoft has been clear: this was a technical infrastructure issue, not a cyberattack, not malicious activity, and not related to AI agents.
A separate problem is also running in parallel. Windows updates released since the October 2026 Patch Tuesday are causing SQL Server performance and stability issues. Linked-server queries that use OLE DB providers to reach external databases (including Oracle and PostgreSQL) leave connections open instead of closing them. These idle connections accumulate and gradually degrade performance. An out-of-band fix is expected soon; temporary workarounds involve manually closing idle connections or restarting the SQL service.
That is the technical summary. The larger story is political and structural.
India’s government has spent years selling “Digital India” as a transformative success. Ministries, public sector units, courts, banks, and private companies have been pushed—or incentivized—into deep dependence on Microsoft’s cloud stack. When that stack failed for more than 24 hours, the cost was paid in delayed official communication, stalled administrative work, disrupted court hearings, and lost business hours. The same political class that lectures citizens about self-reliance has built critical national workflows on servers and code controlled by a single American corporation. When those servers fail health checks after a capacity upgrade, Indian productivity stops.
This is not an accident of technology. It is the predictable result of policy choices that prioritized rapid adoption of foreign platforms over the hard, unglamorous work of building resilient domestic alternatives or enforcing genuine multi-vendor, multi-cloud requirements for critical systems. The same pattern appears elsewhere: heavy reliance on a handful of global cloud providers, weak pressure for data localization with real operational control, and little serious investment in sovereign cloud capacity that can actually run core government and economic functions if the foreign systems go dark.
Microsoft will publish its post-incident report and move on. Indian institutions will return to their Outlook inboxes and Teams meetings as if nothing fundamental has been revealed. The next outage—whether caused by another network change, a different vendor, or something more serious—will again catch a digitally “transformed” nation unprepared, because the system that claims to modernize India continues to outsource its most basic operational resilience to distant data centers and foreign engineers.
The servers are back online. The deeper vulnerability remains wide open.
Official sources
Microsoft 365 Status updates and service health page (incident MO1550821); Microsoft statements on X (@MSFT365Status); contemporaneous reporting from Reuters, BBC, India Today, The Hindu, Associated Press and Microsoft Windows release health dashboard regarding the separate SQL Server issue linked to October 2026 updates.
