Your Eyes in the DarkYour Eyes in the Dark — Proactive Intelligence

Knowledge/Threat Intelligence

Microsoft Reveals July Software Bug Behind Last Week’s Global Microsoft 365 Outage

2 min read

Microsoft says a software bug introduced in July caused last week’s worldwide Microsoft 365 outage. The bug set off a cascading failure that left more than 80% of its networking gateway servers unresponsive.

The nearly 24-hour outage on November 12 disrupted Microsoft 365 services worldwide, including Outlook, Exchange Online, Teams, and Copilot. Users couldn’t access their email, and message delivery was badly delayed.

Timeline

Time (ET)Event
July 2026Bug introduced through an update for Microsoft 365 networking gateway servers
~15 hours before the outageMicrosoft Teams automatically fails over to the networking infrastructure used by Exchange Online, increasing traffic
November 12, 11:20 AMOutage begins
Within 2 hoursThe defect spreads across the fleet; at its lowest, more than 80% of servers are unresponsive
November 13 (Friday)Fix deployed across affected servers; services stabilize
November 13, 11:10 AMMicrosoft confirms active customer impact has ended

Root cause: three problems combined
According to Microsoft’s preliminary post-incident report, shared in the Microsoft 365 Admin Center, the outage came from three problems:

  1. A previously undetected software bug: It was introduced in July through an update for Microsoft 365 networking gateway servers. The update had run for more than three months without issues, but it contained a bug that could overwhelm servers under certain traffic conditions and make them stop responding.
  2. More traffic after a Teams failover: About 15 hours before the outage, Microsoft Teams automatically switched to the networking infrastructure used by Exchange Online, increasing traffic on those servers.
  3. Reduced server capacity: Nearly 14% of the gateway’s server capacity was already offline because of an unrelated issue. The infrastructure had enough capacity to absorb that reduction, but together with the extra traffic, it triggered the bug.

Why testing missed the bug
Microsoft says its tests didn’t catch the bug because they used less powerful hardware than the production servers. According to the company, the contention issue gets worse on machines with more cores and newer hardware, while its load testing focused on weaker hardware with fewer cores.

How the failure spread
As servers stopped responding, Microsoft’s systems redirected users to other available servers. Those servers were then overwhelmed by the extra traffic and failed too. Microsoft said the defect spread across its fleet in less than two hours.

Safeguards meant to stop problems spreading between regions also failed to contain the cascading outages, so the disruption spread worldwide.

Why Exchange Online took longest to recover
Other Microsoft 365 services, such as Teams, OneDrive, and SharePoint, could switch to alternative infrastructure and recovered sooner. Exchange Online couldn’t make the same switch, leaving users unable to access their mailboxes.

Recovery was hard because restarted servers were quickly overwhelmed again by backed-up traffic. Once engineers identified the bug, they built a fix and deployed it across the affected servers, and services stabilized through Friday.

Microsoft’s response
Microsoft says it has since:

  • Increased capacity
  • Improved monitoring
  • Added safeguards to stop traffic redirection from triggering similar cascading failures

In a separate statement on X, Charles Lamanna, Microsoft’s Executive Vice President of Copilot, Agents, and Platform, apologized, saying: “We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations.”

Microsoft also had a separate Teams outage earlier that day; it is unclear whether the two incidents are related.

What’s next
Microsoft’s investigation is ongoing, and a final post-incident report is expected later this week.

Get the latest dark web news in your inbox

Ransomware, breaches and exploited vulnerabilities, from The Darkweb News.

Free. No spam. Unsubscribe in one click.

Latest news

Ruby Patches “Ruby2Shell” Vulnerability That Could Lead to Remote Code Execution

Zero-Day / Patch

Fresh security updates for the Ruby programming language fix seven vulnerabilities in its regular expression engine and in string case conversion. Proof-of-concept (PoC) code demonstrating remote code execution (RCE) exists for five of them. The main flaw: Ruby2Shell (CVE-2026-132825) The top vulnerability, CVE-2026-132825 (CVSS 7.4), is a heap-based buffer overflow in string case conversion that could lead to RCE in certain scenarios. It’s been dubbed Ruby2Shell. How it works The flaw affects

China-Linked Armory Castle Exploits VMware vCenter Zero-Day for Admin Access and Data Theft

Zero-Day / Threat Intelligence

The suspected China-nexus cyber espionage group Armory Castle (formerly UNC5221) has been attributed to the zero-day exploitation of a critical flaw in VMware vCenter Server, starting in early September 2026. The vulnerability Tracked as CVE-2026-123890 (CVSS 9.8), the flaw is an authentication bypass in the VMware Directory Service. According to Google Threat Intelligence Group and Mandiant, it’s an unauthenticated Secure Remote Password (SRP-6a) session key disclosure vulnerability over DCE/R

New Unpatched Windows Zero-Day Lets Someone Run Programs on a Locked PC

Zero-Day

A newly disclosed, unpatched zero-day technique called FastUnlock lets someone with physical access to a locked Windows computer start programs without signing in. Whoever uses it gets only a limited account, not administrator control of the machine. Who disclosed it The method was posted by a researcher using the handles MSNightmare and Nightmare Eclipse. Endpoint-security firm ThreatLocker tested it the same day and confirmed it works. There is no fix from Microsoft yet, and nothing shows the