Skip to content
techworthit
techworthit

One question, one number. TechWorthIt reads the world's tech reviews and reporting, then tells you whether it's worth your money, with every source linked.

How we scoreAboutContactPrivacyTermsRSS
© 2026 TechWorthIt · We may earn a commission from links. It never changes a verdict.
LatestReviewsDealsSearchSaved 0
techworthit
01 Reviews02 Explainers03 News
SectionNews / Enterprise
AuthorTechWorthIt Desk
PublishedNov 16, 2026 · 3 min

Microsoft blames November 12 outage on a July software defect

A preliminary post-incident report says a months-old gateway bug, a Teams failover and reduced capacity combined to knock out Exchange Online. A final report is due November 20.

A network gateway appliance in a server rack with mostly unlit status lights and a cracked chain of cables trailing from it, suggesting a hidden fault that caused a wider outage.
Illustration
On this page
  1. Key facts
  2. How the failure unfolded
  3. Why it matters
  4. What to watch next
0% read
On this page · 4 sections ▾
  1. Key facts
  2. How the failure unfolded
  3. Why it matters
  4. What to watch next

Microsoft has traced the global Microsoft 365 outage of November 12 to a software defect introduced in July, according to a preliminary post-incident report published on November 15 and summarized by The Register. The bug sat unnoticed in network gateway servers until a load surge and a drop in capacity triggered it, producing a cascading failure that took Exchange Online offline for roughly a day.

Key facts

  • The defect arrived with a July 2026 update prepared for Microsoft 365 network gateway servers. It caused lock contention inside an internal Windows process, exhausting CPU and memory.
  • Two events coincided: Teams failed over to the primary gateway that supports Exchange Online, and almost 14% of gateway capacity was out of service.
  • At the worst point, more than 80% of servers were unresponsive, and the defect was hit across the fleet within two hours.
  • Microsoft's fix returned the code path to a previously known good state in Windows. It was applied to server groups in batches.
  • A final post-incident report is due on November 20.

How the failure unfolded

Microsoft's report says its load testing focused on weaker hardware with fewer cores, while the contention problem worsens on newer, multi-core machines. XDA notes that EVP Charles Lamanna described the same mechanism on X.

Neither trigger was a problem alone. The Register reports that the Teams failover was not unusually large, and Microsoft said the service had enough headroom despite the reduced capacity. Together they pushed the gateway into the defect. Traffic from failed servers was rerouted to healthy ones, which then hit the same bug.

Recovery was slow. Restored servers were overwhelmed again by pent-up traffic, and automated recovery was not designed for such a broad unresponsive state. A simple rollback was also impossible because the defect was months old. TechRadar adds that Microsoft said a separate issue kept its protections against cascading failure from working properly.

The Register's timeline puts the Teams failover at 0107 UTC on November 12 and the first detection of connectivity issues at 1603 UTC. Microsoft identified a mitigation at 0720 UTC on November 13, confirmed health at 1610 UTC, and sent its final customer update at 0415 on November 14. Services such as Teams, OneDrive and SharePoint could fail out of the faulty gateway, but Exchange Online could not for scale reasons.

Why it matters

Earlier statements were less specific. According to Android Authority, Microsoft first cited an issue during an earlier network capacity upgrade and said the incident was unrelated to cyber activity or AI agents. The report now gives a fuller root cause and rules out the theories that circulated during the outage.

The real-world effects were wide. Android Authority lists disruptions at courts, government agencies, schools, airlines and the NHS call handling in the UK. In Germany, WDR reported that a chlorine dosing fault at a Phantasialand hotel went unnoticed because the alert was sent by email. Fifteen guests were triaged and four went to hospital.

What to watch next

The November 20 final report should show whether Microsoft changes its testing to cover newer, high-core hardware and whether it redesigns recovery for large-scale unresponsive states. The Register questions how a defect that survived three months reached production with load tests that did not reflect conditions Microsoft controls.

Keep reading

News / Enterprise4d

Microsoft 365 and Outlook outage hits users worldwide on Nov. 12

Microsoft says a large number of unavailable servers overloaded Exchange Online and other 365 services, with no restoration estimate as of early evening ET.

An overloaded server unit with some dark status lights, a drooping bundle of cables, and a cracked cloud shape above it, representing a cloud service outage.
News / Business3d

FAA issues nationwide ground stop after telecom outage

The FAA halted departures at all US airports on November 13 after communication problems hit Air Route Traffic Control Centers. The cause was unknown as of the reports.

A dark, silent air traffic control tower overlooks an airfield where a lone jet sits parked beside a broken communication cable.

For IT buyers, the incident is a case for keeping alert paths independent of a single email provider, particularly for safety-critical systems.

Sources

  • XDAMicrosoft reveals why its services went down last week, and the problem had been hiding since July↗
  • Gadgets 360Microsoft Finally Explains Why Major Outlook, Microsoft 365 Outage Happened↗
  • The RegisterMicrosoft blames monster email outage on software defect introduced in July fix↗
  • TechRadarMicrosoft 365 outage led to chlorine gas poisoning of 15 people in Germany↗
  • Android AuthorityLast week’s Microsoft Outlook outage turned a hotel pool fault into a hospital trip for 15 guests↗
  • TechSpotMicrosoft 365 outage led to chlorine gas leak at German hotel, poisoning of 15 guests and sending four to hospital↗

HOW THIS WAS MADE · Written by the TechWorthIt Desk with AI assistance from 6 published sources, linked above. Facts are cross-checked against those sources before publishing; we never claim testing we didn't do. Last updated Nov 16, 2026. Spotted an error? Tell us.

News / Enterprise23h

Windows SignDrop zero-day lets standard users gain SYSTEM rights

A researcher published exploit code on November 10 that abuses a 2025 Microsoft log-file safeguard and Defender. Microsoft is investigating; no patch or CVE exists yet.

A laptop with a blank screen beside an open padlock and a large upright key, symbolising a security flaw that unlocks full control of a computer.
News / Enterprise9d

FAA to replace floppy-disk air traffic systems with E-IDS by 2028

The agency says the Enterprise Information Display System will replace four 1980s-era tools at 435 facilities, but funding for the wider modernization remains short.

An old floppy disk stands in front of a modern flat-panel display with simple abstract shapes, suggesting outdated air traffic control technology being replaced.