Microsoft 365 outage due to July update bug

Published November 16, 2026

The Microsoft 365 outage was caused by a bug from a July networking gateway update.

In a post on X, Charles Lammana, Microsoft's executive vice president of Co-Pilot, Agents and Platform, said the July update was deployed globally with no impact. The defect then caused servers to be overwhelmed and unresponsive in newer servers.

Lammana said that under certain loads servers would become unresponsive. Normal load testing didn't detect the bug because Microsoft examined different traffic and SKU mix in test lab. The load testing used by Microsoft focused on weaker hardware with less cores. The machines that stumbled were newer machines with more cores.

He also added:

"A surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts."

Meanwhile, that issue was compounded because Microsoft said 14% of server capacity for the networking gateway was out of service for an unrelated issue.

Lammana said typically Microsoft would have routed users to other healthy servers, but the redirected traffic also flooded machines. At the worst point, Microsoft had 80% of its server fleet unresponsive.

To fix the issue, Microsoft returned the code to its previously known good state. However, that move too time given the cascading failure of servers.