Microsoft's global service outage, which began on November 12, continued to disrupt businesses, government agencies, airlines and healthcare services on November 13, highlighting the risks of depending heavily on a single technology provider for everyday operations.
The disruption affected several Microsoft 365 products, including Outlook, Teams, SharePoint, Exchange Online and AI-powered Copilot. Users across dozens of countries reported difficulties accessing emails, scheduling meetings, retrieving information and using cloud-based applications.
India was among the affected markets, with airlines reporting interruptions to customer email support and cybersecurity specialists warning that disruptions to Microsoft's security infrastructure could weaken companies' ability to detect and respond to cyber threats.
Microsoft reported improving service stability in some regions, but a complete restoration had not been confirmed in its earlier recovery updates.
The problems emerged on Thursday evening as Microsoft servers handling essential cloud services began experiencing unusually high traffic and connectivity failures.
Outage-monitoring platform Downdetector recorded nearly 130,000 problem reports at one stage. However, the actual number of affected users remains unknown. Microsoft 365 has an estimated 430 million users worldwide, illustrating the potential scale of such a disruption.
Microsoft's investigation found that critical processes on some servers were becoming overloaded, causing them to stop responding. Traffic was subsequently redirected to other servers, increasing pressure on the remaining infrastructure.
Engineers attempted several recovery measures, including restarting servers, redistributing traffic, restricting certain connections and rebuilding affected systems using earlier configurations. However, some servers became unresponsive again when normal traffic resumed.
The company subsequently reported improved stability after applying a patch to part of its authentication and routing infrastructure. The precise initiating cause, however, had not been conclusively established.
Microsoft said it had found no indication that the outage resulted from a cyberattack.
The most visible disruption in India was in aviation customer support. IndiGo warned passengers that its email support was affected and that some messages might not reach the airline. Akasa Air similarly reported delays in receiving customer emails and directed passengers towards alternative support channels.
Air India said its flight operations and communication channels remained unaffected, adding that it had temporarily rerouted emails to maintain customer service.
Importantly, the airlines reported no disruption to flight operations because of the Microsoft outage.
For India's IT services companies, banks, financial institutions, outsourcing businesses and other enterprises that use Microsoft 365, the incident also exposed potential operational risks.
Email interruptions can delay approvals, customer communication, documentation and transaction-related coordination. Disruptions to Teams calendars and Copilot can affect workflows even when other applications remain accessible.
Not all Microsoft services stopped functioning simultaneously. Core Teams messaging and online meetings remained largely operational, while functions dependent on Exchange Online experienced greater disruption.
Beyond communication failures, the outage has raised concerns about the effectiveness of corporate cybersecurity monitoring.
Security Operations Centres (SOCs), which track suspicious activity across business networks, depend on a continuous flow of security alerts, software updates and threat intelligence.
Industry executives said that disruptions to Microsoft Defender services could interfere with the transmission of security information from endpoint devices to central monitoring systems.
Although Microsoft Sentinel, its security information and event management platform, continued functioning, problems involving connected services could affect automated security workflows.
If alerts arrive late or monitoring information accumulates during an outage, security teams may struggle to identify genuine threats quickly. Disrupted email and Teams services can also delay communication between cybersecurity providers and their clients.
These risks do not mean that corporate networks have been breached. They demonstrate how an infrastructure failure can reduce security visibility even without a cyberattack.
The disruption extended well beyond corporate offices. In the UK, National Health Service (NHS) staff reported difficulties accessing email and IT systems. Pharmacies experienced delays communicating with GP surgeries about prescriptions, while some remote healthcare appointments were disrupted.
Schools requested parents to use telephones instead of email. Police forces also advised people to use alternative reporting channels, while the UK Parliament activated contingency communication arrangements.
Government agencies in Australia and several Asian countries reported similar problems. In Japan, businesses faced difficulties processing orders and reservations, while some financial institutions encountered operational interruptions.
Even technology companies, including OpenAI and Anthropic, reported problems involving Microsoft 365-connected services.
The incident has renewed questions about the concentration of essential business functions within a handful of cloud technology platforms.
For Indian businesses, particularly banks, IT companies, healthcare providers and other service-dependent enterprises, the lesson extends beyond maintaining alternative email accounts.
Companies may need independent communication channels, backup authentication procedures, tested disaster-recovery systems and cybersecurity monitoring capabilities that remain operational when their primary cloud provider fails.