Microsoft's preliminary Post-Incident Report says a hidden defect in its cloud gateway caused one of the largest outages in the company's history. The outage ran from November 12 at 16:20 UTC to November 13 at 16:10 UTC, just under 24 hours. The report lists the cause as "a technical issue not related to cyber or AI/agents."

Microsoft attributes the outage to three factors. First, a change deployed to the cloud gateway starting in July created a bug. Under certain conditions, CPU and memory resources could become exhausted and unresponsive. Microsoft says pre-release testing missed the defect because the test hardware was less powerful than some newer production systems, where higher CPU core counts apparently contributed to the lockout.

Second, traffic shifts exposed the bug. About 15 hours before the outage, Teams traffic was moved from the alternate gateway to the primary gateway, where Exchange Online access is maintained. Microsoft calls this a standard fail-safe, but the primary gateway then handled more traffic with a different mix of requests. Third, Microsoft says its gateway server fleet was operating 14 percent below optimal conditions, which removed the headroom that could have absorbed the extra demand.

As US business hours began, the gateway servers froze. Backup gateways received the redirected requests but also locked up. Microsoft's report says more than 80 percent of the affected gateway servers froze. The report does not explain why the systems meant to isolate affected servers by region failed.

Recovery took longer than usual because it required a targeted update from Microsoft engineers. Restarting the servers did not work. When they came back online, large request queues triggered the same resource exhaustion. Microsoft says Teams, OneDrive, and other Office applications could be routed away from the affected infrastructure, but scaling limits prevented Exchange Online from doing the same. Rollbacks also failed because the July defect had not been identified.

Microsoft says it has added capacity and traffic-distribution guardrails. It also extended delivery timeouts for affected email so delayed messages would not bounce as undeliverable. The company expects to publish its full final incident report on November 20. Microsoft says all its cloud services appeared online and operational as of Monday morning.