Microsoft details how three problems combined for a global outage
Microsoft's preliminary incident report says a latent bug in its cloud gateway, shifts in traffic and lower server capacity together caused a nearly 24-hour Microsoft 365 and Exchange outage. The company classes it as a technical issue unrelated to cyberattacks or AI agents.

Microsoft has published a preliminary post-incident report on last week's widespread service failure, which hit much of its Microsoft 365 productivity suite and the Exchange email infrastructure. The company says a hidden defect in its cloud gateway, dormant since July, was to blame. The outage affected businesses and public offices that rely on Microsoft's cloud and email services.
Timeline
The report places the disruption between 16:20 UTC on November 12 and 16:10 UTC on November 13, just under 24 hours. Extra monitoring of affected systems continued through November 14. The incident is tracked under the IDs EX1550543 and MO1550821. The full report is visible only with Microsoft 365 admin credentials, but the trade site Office Watch has reproduced the preliminary version, and the University of Pennsylvania keeps an archive of Microsoft's service-health updates.
Three causes
The first factor was a change deployed to the cloud gateway starting in July. Under certain conditions it created a bug that could exhaust CPU and memory resources and leave the system unresponsive. Microsoft says the defect escaped pre-release testing because the hardware used was less powerful than some systems already running in production. Higher CPU core counts on newer machines apparently contributed to the lockout.
The second factor was load. Microsoft says traffic shifts during standard network maintenance and upgrades exposed the latent bug. The company runs two independent gateway systems for resilience: if one fails, the other takes over. About 15 hours before the outage, Teams traffic was moved from the alternate gateway to the primary one, which also maintains Exchange Online access. This was a standard fail-safe, but it left the gateway handling more traffic with a different mix of requests. As requests piled up, the affected servers exhausted their capacity and refused new connection requests.
Microsoft's report lists the incident's final status as a technical issue not related to cyber activity or AI agents.

