Microsoft 365, Teams Outage Spreads to OpenAI, Anthropic: Root Cause Analysis
On November 12, a Microsoft cloud outage took down Microsoft 365, Outlook, and Teams for hours, also disrupting OpenAI and Anthropic services; the root cause was servers failing health checks under load, triggering a cascading failure that Microsoft mitigated by pausing deployments and rerouting traffic, with recovery underway by November 13.
On November 12, Microsoft 365, Outlook, Teams, and other applications experienced a multi-hour outage affecting a large number of users. The disruption also impacted connectivity components used by OpenAI and Anthropic AI services.
According to outage-tracking data, problem reports peaked around 1:00 PM US Eastern Time: Outlook reports reached 138,058, Microsoft 365 reports exceeded 46,000, and Teams reports numbered about 3,000. By 6:00 PM Eastern Time, Microsoft stated it was still working to restore affected servers and had observed limited recovery, with users gradually reconnecting.
Microsoft identified the root cause as multiple servers unexpectedly going offline due to high load, not a traffic surge. Those servers failed automated health checks and were incorrectly marked unavailable, shifting excess load onto the remaining infrastructure and triggering a cascading failure. In response, Microsoft paused all deployments and configuration changes globally, redistributed connection traffic across its infrastructure, and moved traffic to backup paths to relieve pressure on overloaded nodes.
By 5:00 AM Beijing Time on November 13, Microsoft had validated an alternative health-check method on a subset of affected servers. Those servers successfully returned to service, and the fix was being rolled out more broadly.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
