"Microsoft outage" is the biggest technology search of the week. Google Trends shows more than 10 million searches in the US and over a million in India in 48 hours, alongside "outlook outage", "is outlook still down" and "microsoft outage reason". Outlook, Teams, Copilot and other Microsoft 365 services were disrupted for more than a day from November 12, 2026. Here is what happened, what Microsoft says caused it, what it means if your email went missing, and what developers can learn from it.
Is Microsoft still down?
No, according to Microsoft. On Saturday, November 14, the company said it had addressed the underlying issue and restored service to the remaining affected customers and regions. A few people may still see slow sync or late emails while backlogs clear. For the live picture, use the official Microsoft 365 service status page. If you manage a work or school tenant, check Service health in the Microsoft 365 admin center. Third-party outage trackers are useful, but they count user reports, not confirmed faults.
Timeline of the Microsoft 365 outage
These times come from Microsoft's public updates as reported by CNBC and collected on Wikipedia. India Standard Time (IST) is UTC + 5:30.
- Nov 12, about 17:00–18:00 UTC (10:30–11:30 pm IST): problems begin, shortly before 1 pm US Eastern time.
- Nov 12, 17:54 UTC (11:24 pm IST): Microsoft first acknowledges that users in the Americas cannot reach Exchange Online mailboxes.
- Nov 12, 18:07 UTC: Microsoft warns that the problem is wider and affects users globally.
- Nov 12, around 21:00 UTC (4 pm ET): Microsoft says it has validated an alternative service health check method that brings some servers back, and starts applying it more widely.
- Nov 12, 23:04 UTC: some affected servers return to service.
- Nov 13, 04:36 UTC (10:06 am IST): Microsoft reports partial recovery in some regions. Asia Pacific is among the first to normalise.
- Nov 13, through the day: the outage narrows mostly to Exchange, the system behind Outlook email. Microsoft reports "encouraging recovery progress" and says email queues are approaching normal levels. It also apologises publicly.
- Nov 14 (Saturday): Microsoft says service is fully restored.
What caused the Microsoft outage?
Microsoft has not yet published its full post-incident report, and says it will once its assessment is complete. Its statements so far describe this chain of events:
- A change during an earlier network capacity upgrade. Microsoft says the disruption came from "an issue during an earlier network capacity upgrade". It also said it was rolling back a recent network configuration change.
- Servers failed automated health checks. As a result, servers were treated as unavailable and taken out of service.
- Load piled onto the remaining servers. Microsoft described a "number of servers being unexpectedly unavailable; straining the remaining infrastructure", with elevated load across several regions.
- Secure connections became the bottleneck. According to Microsoft, the process that sets up secure connections was overwhelmed, so servers stopped handling requests.
Microsoft says it found no malicious activity and that the outage was not caused by a cyber attack or by AI agents. Expect more detail, and possibly corrections, when the formal review is out.
Why a health-check problem can take down a whole service
Microsoft has not shared engineering details, so treat this as a general explanation of the pattern it described, not a description of its internal systems. Large services sit behind load balancers that send traffic only to servers that pass a regular health check. If a change makes healthy servers look unhealthy, the load balancer removes them. The servers that remain get more traffic than they were sized for, slow down, start failing their own checks, and are removed too. Engineers call this a cascading failure. Setting up encrypted (TLS) connections costs real CPU time, so a flood of reconnecting clients makes it worse: each retry adds work to servers that are already struggling.
That is why recovery took so long. Microsoft had to switch to a different health-check method, restart unresponsive servers, and bring systems back in stages. Bringing everything back at once would have triggered the same overload again.
Who was affected?
Problems were reported in more than 70 countries. Around 430 million people use Microsoft 365, according to figures cited in coverage of the outage. Reported impacts included:
- India: IndiGo and Akasa Air reported that their email support was affected. Air India said it had temporarily rerouted emails to keep receiving customer messages and that its flight operations were not affected.
- Healthcare: parts of the UK's National Health Service lost access to email and calendars, and some operations were reported cancelled.
- Governments and courts: disruption was reported in Australia, Japan, the Philippines, Singapore and the United States.
- Business: Richemont delayed its results announcement, and Workhorse Group moved its earnings release. The Anderson Economic Group estimated lost productivity at about $7 billion. That is an outside estimate, not an official figure.
What to do now if your email went missing
- Give it time. Microsoft said it extended the retry window for delayed email to 48 hours, so messages sent during the outage may still arrive late.
- Resend anything urgent. If an important message (an offer letter, an exam or application confirmation, an invoice) has not arrived after that window, ask the sender to send it again.
- Check the official status, not rumours. Social media filled with cyber attack theories. Microsoft's own status page and statements are the reliable sources.
- Do not reinstall Office or reset your password because of the outage. This was a server-side problem. Nothing on your device needed fixing.
Lessons for developers and IT teams
Even if you never run anything at Microsoft's scale, the same patterns show up in a small app with a database and a load balancer. They are also useful topics for interviews:
- Roll changes out in stages. Push a network or config change to a small slice of servers first, watch it, and keep an instant rollback path ready.
- Design health checks carefully. A health check that is too strict, or that depends on the thing you just changed, can remove good servers. Many teams cap how many servers a load balancer may remove at once.
- Make clients back off. Retries with exponential backoff and jitter stop a recovering service from being hit by a wave of reconnections.
- Plan for your provider failing. A backup way to communicate (phone, a second chat tool, a status page hosted somewhere else) kept some teams working while Outlook and Teams were down.
If you want to practise this hands-on, our Cloud & DevOps project guide covers packaging a service, health checks and release checklists. For the security side, the Cybersecurity & Secure Coding guide covers the defensive basics of protecting accounts, data and web apps.
Quick revision questions
Major technology events like this often appear in current affairs sections of UPSC, SSC and banking exams.
- When did the global Microsoft 365 outage begin? November 12, 2026, with full restoration reported on November 14.
- Which Microsoft system powers Outlook email and was most affected? Exchange Online.
- Did Microsoft call it a cyber attack? No. Microsoft said it found no malicious activity.
- What did Microsoft link the cause to? An issue during an earlier network capacity upgrade that led servers to fail health checks.
- Which 2024 incident was it widely compared with? The CrowdStrike update failure that disrupted airlines and banks.
For more practice, visit the UPSC exam hub and the banking exams page.
Frequently asked questions
Is Microsoft still down?
As of November 14, 2026, Microsoft says it has addressed the underlying issue and restored service to the remaining affected customers and regions. Check the official Microsoft 365 service status page for the live picture.
What caused the Microsoft outage?
Microsoft linked it to an issue introduced during an earlier network capacity upgrade. Servers began failing automated health checks, the remaining servers were overloaded, and a process that sets up secure connections became overwhelmed. Microsoft has said a full report will follow.
Was the Microsoft outage a cyber attack?
Microsoft says it has not detected any malicious activity, and it has said the outage was not caused by a cyber attack or by AI agents.
Will emails sent during the outage still arrive?
Microsoft said it extended the retry window for delayed email to 48 hours to protect messages. If an important email has still not arrived after that, ask the sender to resend it.
Sources and further reading
- Microsoft 365 service health status (official)
- CNBC: Microsoft apologises for outage that took down Outlook and other 365 services
- Wikipedia: 2026 Microsoft outage (timeline and references)
- The Hindu: Microsoft outage impacts IndiGo and Air India's email support services
- India Today: Microsoft outage hits businesses, Air India and IndiGo
Facts in this article reflect Microsoft's statements and public reporting as of November 14, 2026. Microsoft's full post-incident report may add or change details, so check the official source before relying on them.