Microsoft blames July software bug for global 365 outage
Microsoft says a bug from a July gateway update, extra Teams traffic and reduced capacity caused the nearly 24-hour Microsoft 365 outage. More than 80% of gateway servers stopped responding at the lowest point.
By JetherVerse News

Microsoft says a software bug from July caused last week's global Microsoft 365 outage. BleepingComputer reported the findings on November 16, 2026, based on a preliminary post-incident report shared in the Microsoft 365 Admin Center.
The outage began at 11:20 AM ET on November 12 and ended at 11:10 AM ET the next day. Outlook, Exchange Online, Teams and Copilot were affected. Microsoft names three causes: a previously undetected bug, extra traffic after a Teams failover, and reduced server capacity. About 14% of the gateway capacity was already offline for an unrelated reason.
The bug came from an update to the networking gateway servers released in July. The update ran for more than three months without a problem. Microsoft says its load tests missed the flaw because labs used weaker hardware with fewer cores. The contention issue gets worse on machines with more cores and newer hardware.
About 15 hours before the outage, Teams switched automatically to the network used by Exchange Online. The added traffic triggered the bug. Servers stopped responding, and traffic moved to other servers, which failed in turn. At the lowest point, more than 80% of servers did not respond. Microsoft says safeguards meant to stop problems spreading between regions did not hold.
Exchange Online was unable to switch to other infrastructure, unlike Teams, OneDrive and SharePoint. Restarting servers failed at first, because backed-up traffic overwhelmed them again. Microsoft then built and deployed a fix. Microsoft says the company has added capacity, improved monitoring and added safeguards against cascading failures.
The report shows how a small test gap grows into a global outage. Hardware in test labs needs to match production hardware.
Nigerian lenders such as Wema Bank and Stanbic IBTC told customers their email was affected during the outage. Banks relying on one vendor for email should ask what their own tests leave out.
Check your own load tests against your real production hardware.
Source: BleepingComputer
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

