MediumDisruptionTechnical fault statedOngoing

Outlets report Microsoft 365 outage across 74 countries, full report pending

Outlets report a Microsoft 365 outage hit Outlook and Teams in 74 countries; check the status page and ignore unsolicited outage messages.

Published
Updated
Exploitation
No. Microsoft says the incident was not related to cyber, as reported by Wired and BusinessLine.

What happened

According to BusinessLine, citing ANI, Microsoft apologised on Friday (local time) after a global outage disrupted Outlook, Teams, Copilot and other services across at least 74 countries, including the United States. BusinessLine says the outage left users without access for nearly 18 hours, and that businesses, schools, government agencies and airline operations were disrupted. It also says AI service connectors used by OpenAI and Anthropic were affected.

Reported durations differ between outlets. India Today describes an outage of over 17 hours, and Indian Express’s headline says 20 hours. Wired says 24 hours. Start times also differ across reports. Wired says users reported Outlook problems to Downdetector just after 12 pm ET on Thursday, and Indian Express says the disruption was first flagged on Thursday, November 12, at around 7:40 am Pacific Time.

Scale, as reported:

  • BusinessLine says Downdetector reports of Outlook outages peaked at 138,058 around 1 pm ET, then fell to 34,490 by Thursday evening.
  • Indian Express says Downdetector registered close to 130,000 user reports at the peak.
  • India Today says Outlook, Teams, Copilot, OneDrive and SharePoint were affected, including government offices and courts.
  • Wired says governments from Japan to the United States reported disruptions, airlines had trouble communicating with customers, and hospitals reported interruptions. Wired also says Microsoft increased the email queue time to 48 hours so that messages sent during the outage are delivered.
  • Inc42 reports that IndiGo said its email support was affected, Akasa Air reported delays in email support, and Equitas Small Finance Bank asked customers to use its helpline instead of email.

Indian Express reports that Microsoft later traced the disruption to a process used by affected servers to establish secure connections, and that Microsoft began reversing certain configuration changes. Inc42 reports a similar account. Microsoft’s full post-incident report has not been published yet, according to BusinessLine and Wired.

What has been said

  • November 13, 2026, Microsoft spokesperson (via Wired): “We are seeing broad recovery and stability across our services.” Wired also quotes: “This was a technical issue not related to cyber or AI/agents.” And: “The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.” Wired adds that the company promised a “full post-incident report” after its review.
  • November 13, 2026, Microsoft 365 Status on X (via Indian Express): “We’re continuing to see improvements in service availability, with email queues significantly reduced and approaching normal levels.” Indian Express reports that Microsoft said some users may still see intermittent access issues or delayed email delivery.
  • November 13, 2026, Microsoft latest update (via Infosecurity Magazine): “We are seeing early signs of stabilization, but service capacity has not yet returned to normal levels and health remains variable as traffic is carefully reintroduced.” This is from Infosecurity Magazine, which describes the update as the latest at the time of writing.
  • Published November 14, 2026, Microsoft statement on X (via BusinessLine): “We are deeply sorry for the disruption this incident has caused our customers and partners.” BusinessLine reports that Microsoft said it would provide a full post-incident report once its review is complete, and that it had addressed the underlying issue and was continuing to restore customers and regions still affected.
  • November 13, 2026, Australian National Cyber Security Coordinator Michelle McGuiness (via Infosecurity Magazine): people should “remain vigilant and be cautious of unsolicited contact”. Infosecurity Magazine also reports that the UK National Cyber Security Centre recommended caution around unexpected calls and messages, especially those containing links.

Is it a cyberattack?

Not according to Microsoft. Wired and BusinessLine both report the company saying the incident was not related to cyber or AI/agents and giving a technical origin, an issue during an earlier network capacity upgrade. Indian Express reports Microsoft saying there is currently no evidence that a cyberattack triggered the outage. Wired says the full cause remains unknown and that Microsoft repeatedly ruled out a cyberattack in its status page statements.

Not confirmed: the full root cause. Microsoft’s post-incident report is still pending, and no independent verification of its account appears in the sources. That report, or any change in Microsoft’s statements, is what would alter this assessment. Infosecurity Magazine reports the outage is not believed to be cyber-related, but warns that criminals may exploit the confusion.

What to do now

  1. Check Microsoft’s official status page (status.cloud.microsoft) or the Microsoft 365 admin center for the current state of your services. Indian Express quotes Microsoft pointing to both.
  2. Do not click links in unexpected emails, calls or texts about the outage. Infosecurity Magazine reports that the UK NCSC and Australia’s National Cyber Security Coordinator both urged caution, and that experts quoted there warn of phishing and fake IT support calls.
  3. Expect a backlog. Wired quotes researcher Jonathan Leitschuh saying users may get a flood of notifications as subsystems come back, and Microsoft extended its email queue time to 48 hours.
  4. Security teams: Binalyze’s Marie Wilcox, quoted by Infosecurity Magazine, advises reviewing sign-ins, mailbox rules, account changes and endpoint activity from the hours when visibility dropped.
  5. Wait for Microsoft’s full post-incident report before drawing conclusions about the cause.

Sources