Microsoft says global Microsoft 365 outage ended, final report due
Microsoft says Microsoft 365 services are restored after a global outage; final report is pending, so check the Service health dashboard.
- Published
- Updated
- Ecosystem
- Critical infrastructure
- Exploitation
- No, no source reports exploitation; GBHackers says the preliminary report describes an operational defect, not attacker exploitation
What happened
According to Microsoft’s preliminary post-incident report, as relayed by BleepingComputer, a global Microsoft 365 outage began at 11:20 AM ET on Thursday, November 12 and ran until 11:10 AM ET on November 13, when Microsoft confirmed services were fully restored. BleepingComputer The outlet reports that Outlook, Exchange Online, Teams and Copilot were disrupted and that users could not reach their email, with significant delays in message delivery.
GBHackers reports the same window as 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13, a total of 23 hours and 50 minutes. It says the disruption mainly affected Exchange Online mailboxes and email delivery, and that other applications were affected where they depended on Exchange Online. GBHackers
Reported scale varies by outlet:
- The Hindu says the outage affected tens of millions of people around the world, including businesses, governments and hospitals. The Hindu
- Mint says governments, courts, healthcare services, businesses, airlines and banks across more than 70 countries were brought to a near-standstill for hours. Mint
- India Today says millions of users were affected and that Microsoft took nearly 36 hours to resolve the issue. India Today
- Mint says services were restored on Saturday, while BleepingComputer and GBHackers give November 13 as the end of customer impact. The outlets do not agree on the duration or the end date.
BleepingComputer says that at the lowest point more than 80% of the affected gateway servers were unresponsive. It also says Microsoft’s investigation is continuing and a final post-incident report is expected later this week. BleepingComputer
What has been said
The sources do not give a date for every statement. They are listed earliest first where a date is known.
- Microsoft, early statement (undated), as reported by Mint on November 15: Microsoft attributed the disruption to “elevated load” on its infrastructure. Mint
- Microsoft, post on X (date not stated in the sources), as reported by India Today: the company said it had “completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions”. India Today also says Microsoft traced the outage to a network capacity upgrade and ruled out a cyberattack. That description comes from this one outlet and differs from the preliminary report as described by other outlets. India Today
- Microsoft, preliminary post-incident report dated November 15 (per GBHackers): it describes a latent software defect in a fix for Microsoft 365 networking gateway servers, deployed from July. It says this was triggered by a Teams traffic failover combined with nearly 14% of gateway capacity being offline for an unrelated reason. GBHackers says Microsoft stated that neither the defect nor the fix applies to broader Windows deployments. GBHackers BleepingComputer quotes the report: “Our normal load testing did not detect the latent issue” and “At its lowest, more than 80% of servers were unresponsive”. BleepingComputer
- Microsoft, customer report issued late Sunday (November 15), as reported by BusinessLine (Bloomberg): the report says the bug had gone undetected in data centres since July. BusinessLine says Microsoft took 30 hours to identify and fix the problem. BusinessLine
- Charles Lamanna, Microsoft executive vice president, early Monday, per BusinessLine: BusinessLine says he apologized in a post on X that offered more detail on what went wrong. It does not give his wording. BusinessLine
- Charles Lamanna, in a separate statement on X, as quoted by BleepingComputer (date not stated): “We are deeply sorry for the impact to all our customers”. BleepingComputer
- US Transportation Secretary Sean Duffy, as reported by India Today: he said a separate FAA ground stop on November 13 was not linked to Microsoft’s outage. India Today
Is it a cyberattack?
No source in this set reports that the outage was a cyberattack. What each outlet says:
- GBHackers says the preliminary report “describes an operational defect, not attacker exploitation”. This is the outlet’s own summary of the report, not a quotation from Microsoft. GBHackers
- India Today says Microsoft ruled out a cyberattack. India Today
The cause described so far comes from Microsoft’s preliminary report, which the company says is not final. BleepingComputer says a final report is expected later this week. GBHackers says it will supersede the preliminary findings and that Microsoft listed November 20 for its comprehensive repair plan. Any change to the cause or scope would come from that report. Independent verification of Microsoft’s account is not confirmed in the sources.
What to do now
- Check your tenant’s status in the Microsoft 365 Admin Center and the Service health dashboard. GBHackers says administrators tracking advisories EX1550543 and MO1550821 can review them there, and that the dashboard separates active incidents from resolved ones. GBHackers
- Treat any email, call or text about the outage that you did not expect as suspect, and do not click its links. GBHackers notes that outage-themed phishing uses misleading recovery messages. Go to the official status page yourself instead. GBHackers
- Check for mail delivered late or missing during November 12 and 13. BleepingComputer reports significant delays in message delivery. BleepingComputer GBHackers says Microsoft extended email delivery windows. GBHackers
- If you want to seek compensation, an India Today headline says Microsoft may owe customers money for the outage and explains how to claim. Eligibility and terms are not confirmed in the material available here. India Today
- Read Microsoft’s final post-incident report when it is published and compare it with the preliminary account above.
Update, 14 November 2026
- BusinessLine, citing ANI, reports the outage reached at least 74 countries, including the United States, and says AI service connectors used by OpenAI and Anthropic were also affected. BusinessLine It says the outage lasted nearly 18 hours and that Downdetector Outlook reports peaked at 138,058 around 1 pm ET. Indian Express puts the peak at close to 130,000 and its headline says 20 hours. Wired says 24 hours, and India Today describes over 17 hours.
- Wired says Microsoft raised the email queue time to 48 hours so that messages sent during the outage are delivered. Inc42 reports that IndiGo and Akasa Air had email support problems and that Equitas Small Finance Bank told customers to use its helpline.
- Indian Express reports that Microsoft traced the disruption to a process servers use to establish secure connections, and began reversing certain configuration changes. Inc42 gives a similar account.
- Wired quotes a Microsoft spokesperson saying the incident was “a technical issue not related to cyber or AI/agents”, introduced during an earlier network capacity upgrade. Wired adds that the full cause was still unknown at the time.
- Infosecurity Magazine reports that Australia’s National Cyber Security Coordinator, Michelle McGuiness, urged people to “remain vigilant and be cautious of unsolicited contact”, and that the UK NCSC advised caution with unexpected calls and messages, especially those with links. Infosecurity Magazine also quotes Binalyze’s Marie Wilcox advising security teams to review sign-ins, mailbox rules, account changes and endpoint activity from the hours when visibility dropped.
Sources
- BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage
- GBHackers: Microsoft Reveals Windows Bug That Crashed Over 80% of Servers During Global Microsoft 365 Outage
- BusinessLine: Microsoft 365 outage: Bug went undetected in data centres since July
- India Today: Nightmare November for tech: Microsoft, banks, airlines and more hit by outages
- India Today: Microsoft may owe you money for 36-hour Outlook outage, here is how to claim it
- Mint: From Microsoft 365 to CrowdStrike - Biggest tech outages that almost brought the world to a standstill
- The Hindu: Outlook outage: On Microsoft and dangers of centralising digital systems