Microsoft traces Microsoft 365 worldwide outage to hidden Windows defect
Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version
Published
What happened
Microsoft's preliminary report on the Microsoft 365 incident (12 to 13 November 2026, roughly 4:20 PM to 4:10 PM UTC the next day) attributes it to a lock contention defect in an internal Windows process on Microsoft 365 networking gateway servers. The fix had run globally since July without visible problems. Traffic shifting from Teams plus about 14% gateway capacity loss triggered the fault, and automated failover spread it across regions. Tracking references are EX1550543 and MO1550821. No CVE is cited, and Microsoft says no customer action is needed. Full repair details are due 20 November.
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
- Check the Microsoft service health records for incidents EX1550543 and MO1550821 for updates.
- No tenant or device configuration changes are needed, according to Microsoft.
Written by AI from the sources, checked against them
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