Home / Blog / Microsoft says months-old bug caused global Microsoft 365…
Tech News

Microsoft says months-old bug caused global Microsoft 365 outage

A latent July bug and an automated Teams failover triggered a cascading outage that left over 80 percent of Microsoft 365 gateway servers unresponsive.

By Dillip Chowdary • Nov 16, 2026 • Source: BleepingComputer

Microsoft says months-old bug caused global Microsoft 365 outage
Image: BleepingComputer

At a glance

Affected services
Outlook, Exchange Online, Teams, Copilot
Outage start
November 12, 2026, at 11:20 AM ET
Outage restoration
November 13, 2026, at 11:10 AM ET
Gateway failure rate
Over 80% of servers rendered unresponsive
Offline capacity
Nearly 14% offline prior to incident
Root cause
July gateway update with multi-core bug

Microsoft confirmed that a latent software bug introduced in a July update caused a worldwide Microsoft 365 outage that knocked out communication tools for nearly a day. According to BleepingComputer's report, the defect triggered a cascading failure leaving over 80 percent of gateway servers unresponsive. The disruption paralyzed Exchange Online, Outlook, Teams, and Copilot, preventing mailbox access and delaying message delivery globally.

This technical analysis examines the preliminary findings published in the Microsoft 365 Admin Center, reviewing the multi-core contention flaw, testing hardware discrepancies, and operational triggers behind the global collapse. The report is written for enterprise administrators, systems architects, and engineering teams managing cloud infrastructure dependencies.

01Preliminary report on the November disruption

The service disruption began at 11:20 AM ET on Thursday, November 12, and continued until Microsoft confirmed full recovery at 11:10 AM ET the next day. During the nearly 24-hour incident, corporate users experienced widespread failures across Outlook, Exchange Online, Teams, and Copilot. In its preliminary post-incident report, Microsoft attributed the collapse to three factors: an undetected bug, an automated Teams failover, and reduced capacity.

The outage locked users out of corporate mailboxes and triggered severe transmission delays across global communication channels. Microsoft launched an emergency investigation across its networking gateway fleet as enterprise tenants submitted a flood of connection tickets. On X, Charles Lamanna, Microsoft executive vice president of Copilot, apologized to affected organizations for the severe disruption to their daily operations.

02Latent gateway update and multi-core lab testing

The software defect entered production in July through an update developed for Microsoft 365 networking gateway servers. Although the update ran for over three months without operational issues, it harbored a dormant flaw capable of freezing servers under heavy loads. Standard pre-release testing failed to uncover the vulnerability because testing environments utilized lower-tier hardware configurations.

Microsoft stated in its preliminary disclosure that load testing failed to surface the defect due to the specific traffic mix and SKUs evaluated in internal labs. The contention issue worsened on machines featuring newer hardware and higher core counts, whereas lab testing focused on weaker hardware with fewer cores. Consequently, standard test cycles could not simulate the multi-core contention that paralyzed production nodes.

03Teams failover traffic and reduced gateway capacity

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

The latent defect was triggered after Microsoft Teams automatically shifted its networking traffic onto the Exchange Online gateway infrastructure approximately 15 hours before the outage. This traffic redirection significantly heightened connection volume on the shared servers. The sudden influx of network requests created the exact high-concurrency conditions required to activate the underlying software bug.

Compounding the surge, nearly 14 percent of the gateway server capacity was already offline due to an unrelated problem. While the infrastructure possessed sufficient capacity to absorb that initial reduction, combining reduced capacity with increased Teams traffic triggered the dormant bug. The concentrated request volume quickly overwhelmed the remaining operational servers across the gateway tier.

Note: Microsoft Teams also experienced a separate outage earlier that day, though Microsoft has not confirmed whether the two incidents were related. That initial disruption added operational pressure across Microsoft services shortly before the traffic failover began.

04Cascading server failures across global networking gateways

As gateway servers began freezing, automated traffic management systems redirected incoming requests to surviving servers across the fleet. This redirection quickly overloaded the remaining functional nodes, causing them to encounter the same defect and stop responding. In less than two hours, the failure spread across the fleet, leaving more than 80 percent of servers unresponsive at its lowest point.

Built-in regional safeguards designed to prevent localized failures from spreading across geographic boundaries failed to contain the cascading breakdown. This containment failure allowed the disruption to expand across worldwide infrastructure, transforming an isolated routing problem into a global outage. Systems monitoring showed widespread gateway unresponsiveness across multiple continents.

Other Microsoft 365 services, including Teams, OneDrive, and SharePoint, switched to alternative infrastructure to restore operations earlier, but Exchange Online lacked an equivalent fallback path. Consequently, users remained unable to access mailboxes. Recovery proved exceptionally difficult because rebooted gateway servers were instantly overwhelmed again by backed-up network traffic queues.

05Hotfix deployment and revised operational safeguards

Engineering teams developed a targeted software fix after identifying the defect and deployed it across affected gateway servers throughout Friday. This deployment broke the restart overload cycle, allowing gateway nodes to stabilize and resume packet processing. Service restoration progressed steadily across regional clusters as the software patch took effect.

Microsoft confirmed that active customer impact ended by 11:10 AM ET on Friday, November 13, concluding the nearly 24-hour global incident. Since the recovery, the company has expanded server capacity, upgraded monitoring tools, and deployed safeguards to prevent traffic redirection from causing cascading collapses. A final post-incident report is scheduled for release later this week.

Frequently asked questions

What caused the November 2026 Microsoft 365 outage?

A latent software bug in a July gateway update triggered a cascading failure when combined with an automated Teams failover and reduced server capacity. Under heavy load, the multi-core contention bug caused gateway servers to become unresponsive.

Which Microsoft services were affected during the disruption?

The outage disrupted Exchange Online, Outlook, Microsoft Teams, and Copilot worldwide. Users could not access email and experienced severe delays in message delivery.

Why was the gateway bug not caught during pre-release testing?

Microsoft load-tested the update on weaker lab hardware with fewer CPU cores, which failed to reproduce the contention defect. The flaw only manifested on production servers with higher core counts and newer hardware architectures.

How long did the Microsoft 365 outage last?

The incident began at 11:20 AM ET on Thursday, November 12, and concluded when Microsoft confirmed full restoration at 11:10 AM ET on Friday, November 13. The total service disruption lasted nearly 24 hours.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →