Microsoft blames week-long Exchange Online outage on defect from July update
Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version
Published
What happened
Microsoft's preliminary PIR attributes the Microsoft 365 outage to a defect introduced in July 2026 in a network gateway fix, which caused lock contention in an internal Windows process and resource exhaustion, worse on machines with more cores. A Teams failover at 0107 UTC on 12 November, combined with roughly 14 percent gateway capacity loss, triggered a cascading failure, with over 80 percent of servers unresponsive at the low point. Rollback was not possible, so engineers deployed a fix that returned the code path to a previous known good state, with mitigation applied at 0720 UTC on 13 November. Defenders should review the final PIR due 20 November and note that load testing focused on weaker hardware.
For security analysts · Written by AI from 1 source · Report an error
- Sources
- 1
Sources and verification
Sources and editorial review
No named human review has been recorded for this story. See the source evidence below.
No vendor or government source is linked to this story yet. Read the source reports; attribution is not independent verification.
How severity and exploitation labels work · All source reports · Report an error
What to do
- No action needed: this one is for your information.
General advice for this kind of story
Source timeline (UTC) · 1 update
Explore this report
Ask AI about this story
Optional follow-up answers generated from our coverage. Check the linked sources before acting.
Ask your own questionWho and what is in it
Companies
Products