Microsoft 365 logo on a screen, showing the suite that suffered the outage.
Tech

Microsoft blames a July bug for last week’s Microsoft 365 outage

By Abbas Jaffar Ali3 min readNov 16, 2026
Change language to
0:00

A bug from a July fix, set off by heavy load, brought down the gateway behind many Microsoft 365 services last Thursday.

The gateway’s capacity was already reduced, and Teams traffic had shifted onto it hours earlier. Windows Report says more than 80% of its servers stopped responding at the low point. Microsoft hasn’t said whether the Gulf was singled out, and the explanation gives users no workaround.

According to Microsoft’s post on X, Charles Lamanna, its Executive Vice President of Copilot, Agents and Platform, laid out the cause on Monday. The cause had been missing from Tbreak’s earlier coverage, when Microsoft would only say servers were unavailable and that it didn’t believe the outage was malicious. Lamanna wrote that three factors together caused a global outage of the networking gateway that fronts many Microsoft 365 services, and apologised to customers. Business Standard and MyBroadband, which quotes Microsoft’s post-incident report, carry the detail below.

Subscribe to our Newsletters for more Tech Stories

The three factors

  1. A latent defect. Under certain load conditions, lock contention inside an internal process made servers overwhelmed and unresponsive.
  2. A Teams failover. About 15 hours before the outage, Teams failed over from the alternative gateway to the primary gateway, which also supports Exchange Online.
  3. Reduced capacity. Business Standard’s account of the post says nearly 14% of the gateway’s server capacity was out of service because of an unrelated issue the day before.

The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers. Neither the defect nor the fix applies to broader Windows deployments. The change began rolling out in July and ran worldwide for more than three months without impact.

Load testing missed it. The test labs used a different traffic and hardware mix, and the contention worsens on machines with more cores and newer hardware. Business Standard reports the tests focused on weaker hardware.

How it spread

Lower capacity and higher load pushed the gateway into the July bug during peak US traffic, and requests built up until servers stopped responding. Traffic redirected from failed servers then overloaded the rest. MyBroadband, quoting Microsoft’s report, says the previously unknown defect hit servers across the fleet in under two hours.

Microsoft’s account says a separate issue also stopped the usual barriers between partitions from containing the failure, so it spread globally instead of staying within regions.

Why email stayed down longer

Teams, OneDrive, SharePoint and Office apps could fail out of the faulty gateway, which is why they came back earlier. Exchange Online can’t, so Outlook users waited longer.

Recovery was slow for other reasons too. Servers returning to service were immediately swamped by waiting traffic and failed again, and Microsoft’s automated recovery wasn’t designed for a failure this broad. Rollback, flighting and feature flags couldn’t quickly revert a change that had been latent for months.

The fix was a code update restoring the earlier known good state. Engineers took groups of servers out of service, applied it, restarted them and returned them to service in turn.

What’s still open

Microsoft says a final post-incident review with more detail will follow later this week. The outage’s total length isn’t confirmed: XDA says about a day, while MyBroadband’s headline says 20 hours.

Copilot has gone dark before, as in September’s outage. Admins can still check incidents MO1550821 and EX1550543 in the admin center while the full review is pending.