According to the report, posted in the Microsoft 365 admin centre and quoted by BleepingComputer, three factors combined: an undetected bug, extra traffic after Teams automatically failed over to Exchange Online's infrastructure about 15 hours before the outage, and roughly 14% of server capacity already offline because of an unrelated issue. Load testing missed the bug because it ran on weaker hardware with fewer cores than the production servers.
"In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive," Microsoft wrote. Systems redirected users to other servers, which failed in turn, and safeguards between regions did not contain the spread. Teams, OneDrive and SharePoint switched to alternative infrastructure and recovered earlier, but Exchange Online could not, leaving users without access to their mailboxes.
The outage ran from 11:20 a.m. ET on 12 November to 11:10 a.m. the next day. Among other effects, it stopped a hotel safety system in Germany from sending alerts about a chlorine leak. Microsoft said it has added capacity, improved monitoring and added safeguards, with a final report expected later this week.