Microsoft blames latent gateway bug and traffic shift for 365 outage

A hidden defect in Microsoft's cloud gateway, dormant since July, was to blame for one of the largest outages in the company's history, according to Ars Technica's reading of a preliminary Post-Incident Report (PIR) from Microsoft. The report says the latent bug, changes in traffic and reduced server capacity combined to knock much of Microsoft 365 and Exchange infrastructure offline. Microsoft lists the incident's final status as "a technical issue not related to cyber or AI/agents."
The report places the outage between November 12 at 16:20 UTC and November 13 at 16:10 UTC, just under 24 hours in total. Additional monitoring stayed in place for any affected systems through November 14. The outage began on November 12 and quickly rippled through businesses and public offices that depend on Microsoft's cloud and email exchange infrastructure. It is covered by Microsoft incident IDs EX1550543 and MO1550821.
Microsoft attributes the outage to three factors. The first is the bug itself. A change deployed to Microsoft's cloud gateway starting in July created a flaw where, under certain conditions, CPU and memory resources could become exhausted and unresponsive. Microsoft contends the defect was never found in pre-release testing because the test hardware was less powerful than some systems already running in production, where higher CPU core counts on newer machines apparently contributed to the lockout.
The second factor was server load. Microsoft said: "Traffic shifts during standard network maintenance and upgrades exposed a latent bug." The company keeps two independent gateway systems for access to Microsoft 365, so that if one has trouble and users cannot get through the front door, the other is opened to keep traffic flowing. According to the report, about 15 hours before the outage, traffic from Teams was shifted from the alternate gateway to the primary one, where Exchange Online access is maintained. The switchover was a standard fail-safe, but it left the primary gateway handling more traffic, with a different mix of requests than before. As requests kept piling up, the affected servers exhausted their capacity and refused new connection requests.
The third factor, reduced server capacity, is named in the opening of the article but not explained further in the text. Seeing the full report on Microsoft's status pages requires Microsoft 365 admin credentials. Office Watch has reproduced the preliminary report, and the University of Pennsylvania maintains an archive of Microsoft's service-health updates.
Key facts
- Microsoft's preliminary report puts the Microsoft 365 and Exchange outage between November 12 at 16:20 UTC and November 13 at 16:10 UTC, just under 24 hours.
- A change deployed to the cloud gateway starting in July created a bug that, under certain conditions, could exhaust CPU and memory resources and leave them unresponsive.
- Microsoft contends testing missed the defect because the test hardware was less powerful than some production systems; higher CPU core counts on newer machines apparently contributed.
- About 15 hours before the outage, Teams traffic was shifted from the alternate gateway to the primary gateway, where Exchange Online access is maintained; the servers then exhausted capacity and refused new connections.
- Microsoft lists the final status as "a technical issue not related to cyber or AI/agents"; the incident IDs are EX1550543 and MO1550821.
Why it matters
Ars Technica calls this one of the largest outages in Microsoft's history. It ran just under 24 hours and quickly reached businesses and public offices that rely on Microsoft's cloud and email infrastructure. The report's account is a case of small things stacking up: a gateway change from July sat dormant, a routine traffic shift exposed it, and reduced server capacity is listed as the third element. The traffic shift was itself a standard fail-safe between two independent gateway systems, which shows how a resilience measure can move load onto a part that carries a hidden flaw.
Who it affects
The outage hit organisations that use Microsoft 365 and Exchange, including businesses and public offices that depend on Microsoft's cloud and email exchange infrastructure. Teams traffic was part of the shift that preceded the failure, and Exchange Online access runs through the primary gateway that ran out of capacity. The text gives no count of affected users, organisations or regions.
How to use it
Administrators can look up the incident under the IDs EX1550543 and MO1550821. The full report on Microsoft's status pages requires Microsoft 365 admin credentials. Anyone without them can read the preliminary report as reproduced by Office Watch, or consult the archive of Microsoft's service-health updates kept by the University of Pennsylvania.
How solid is it
The primary document is Microsoft's own report, so the cause is Microsoft's account of itself. It is labelled preliminary, and the article relays it rather than testing it independently. The explanation for why testing missed the bug is hedged even in the source: Microsoft contends it, and the role of higher CPU core counts is described as apparent. The timing, the incident IDs and the quoted lines come straight from the report as Ars Technica presents it.
Risks and caveats
The report is preliminary. The third factor, reduced server capacity, is named only in the opening paragraph of the article and not explained, so the full chain of events is not laid out here. No customer compensation, SLA consequences or remediation steps are given. Microsoft's "not related to cyber or AI/agents" classification is the company's own statement of final status. No specific CPU core counts or hardware models are named, and no Microsoft spokesperson or executive is quoted.
“Traffic shifts during standard network maintenance and upgrades exposed a latent bug.”
— Microsoft, preliminary Post-Incident Report