AnswersPublished29 sources
Microsoft 365 Outage: What Failed and Why Recovery Took So Long
The November 12 Microsoft 365 outage continued into Friday, with more than 130,000 Downdetector reports of Outlook problems at the peak. The disruption affected Outlook, Teams and other Microsoft services across multiple regions, including government agencies and Microsoft 365 connectors used by OpenAI and Anthropic...
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer
Key takeaways
- The November 12 Microsoft 365 outage continued into Friday, with more than 130,000 Downdetector reports of Outlook problems at the peak.
- The disruption affected Outlook, Teams and other Microsoft services across multiple regions, including government agencies and Microsoft 365 connectors used by OpenAI and Anthropic.[5][26][41]
- Microsoft said it was not aware of malicious activity causing the incident, but early Friday it had not announced a full restoration time or definitive root cause.[5][8][43]
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: How did the global Microsoft 365 outage beginning Thursday afternoon, November 12, 2026, unfold—including Microsoft’s initial mailbox-access. Article summary: The Microsoft 365 outage that began Thursday afternoon, November 12, continued into early Friday, disrupting Outlook, Teams and other workplace tools for more than 12 hours worldwide.[3][5] Microsoft attributed the infra. Topic tags: general, general web, news. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers
A Microsoft 365 disruption that began shortly after noon Eastern Time on Thursday, November 12, affected Outlook, Teams, Copilot and other services into Friday. Downdetector logged more than 130,000 Outlook problem reports near the peak, while reports spread across 74 countries and territories. Those figures describe user-submitted outage reports, not a verified count of people affected.2
3
23
Microsoft said the strain was caused by servers unexpectedly becoming unavailable—not by a surge in traffic. By early Friday, the company reported better stability from a patch applied to part of its infrastructure, but the available updates did not confirm full recovery or provide a restoration deadline.1
38
43
How the outage unfolded
The first reports appeared shortly after noon ET Thursday. Initial reporting focused on problems accessing Exchange Online mailboxes in the Americas, before reports described broader trouble with Microsoft 365 apps and services.2
15
Downdetector reports for Outlook rose to more than 130,000 at about 1:15 p.m. ET, according to reporting that cited the outage tracker. CNN reported that outage reports had reached 74 countries and territories within about an hour.2
3
23 Downdetector figures are a measure of submitted reports, not a census of affected customers.
3
The disruption carried into Friday and Asia-Pacific business hours. Reports described problems with Outlook, Teams, Copilot and other Microsoft services, although the effect varied by service and location.5
19
26
What Microsoft said caused the disruption
Microsoft said several servers had become unexpectedly unavailable, putting additional load on the infrastructure that remained in service. It said the elevated load was not driven by increased traffic.1
Microsoft later identified an overwhelmed process on affected servers that handled secure connections, which could stop those servers from processing requests.7 A secondary account of the incident updates also described an effort to revert a recent network configuration change. The available reporting did not establish that this change was the definitive root cause; early Friday coverage said Microsoft had not confirmed a final cause.
36
43
Microsoft said it was not aware of malicious activity causing the incident. That was the company’s assessment at the time, not a published final forensic conclusion.5
Recovery: early improvement, no all-clear
Recovery efforts did not produce an immediate, consistent return to normal. Reports said earlier changes were “not taking as expected,” while Microsoft continued working to restore affected infrastructure.16
44
Early Friday, Microsoft reported positive server-stability results after applying a patch to an upstream authentication and routing component on part of its infrastructure. The company said it would monitor the result and work to expand the patch; the update did not mean all affected servers or services were restored.38
50
Microsoft’s status was still described as service degradation, and no full-restoration time had been announced in the early-Friday updates cited in reporting.8
43 The evidence supports partial improvement, not a confirmed end to the disruption.
Who and what was affected
The outage reached beyond individual inboxes. Reporting described effects on government agencies in Australia and Japan, US city email systems, and Microsoft 365 connectors used by OpenAI and Anthropic.26
33
41
- Public services and schools: The UK Parliament said alternative communication arrangements were in place, and schools asked parents to call rather than email. Reporting also described disruption affecting government agencies in Australia and Japan, but the available excerpts do not establish the specific services affected in each country.
17
26
- US city governments: Miami Beach, Austin and Jacksonville reported problems with incoming or outgoing email and directed residents to contact local offices by phone when needed.
33
- AI-service integrations: OpenAI and Anthropic reported issues with their Microsoft 365 connectors. This affected Microsoft integrations; it does not establish that either company’s entire AI service was unavailable.
41
When email or workplace tools are unreliable, organizations may need alternate contact routes—but the specific workarounds reported here varied by organization. The documented examples include phone contact for schools and residents, and alternative communications for the UK Parliament.17
33
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "Microsoft 365 Outage: What Failed and Why Recovery Took So Long"?
The November 12 Microsoft 365 outage continued into Friday, with more than 130,000 Downdetector reports of Outlook problems at the peak.
What are the key points to validate first?
The November 12 Microsoft 365 outage continued into Friday, with more than 130,000 Downdetector reports of Outlook problems at the peak. The disruption affected Outlook, Teams and other Microsoft services across multiple regions, including government agencies and Microsoft 365 connectors used by OpenAI and Anthropic.[5][26][41]
What should I do next in practice?
Microsoft said it was not aware of malicious activity causing the incident, but early Friday it had not announced a full restoration time or definitive root cause.[5][8][43]
Sources
insurancebusinessmag.comMicrosoft email, teams goes out globally puts cloud concentration risk back on brokers' radar
us.cnn.comMicrosoft outage live updates: Services including Outlook ...
learn.microsoft.com