Microsoft Says Outlook Testing Missed Bug Behind Worldwide Outage
Microsoft says a dormant software bug and an influx of Teams traffic overwhelmed newer servers during a global Outlook outage. Its final report identifies 13 steps to prevent a repeat, including tests that better match the hardware running its services.

Microsoft’s final Outlook outage report says testing on older servers missed a bug that overwhelmed newer machines serving Microsoft 365 users worldwide. Automatic safeguards then shifted traffic between servers and regions, spreading the failure instead of containing it. Microsoft has identified 13 steps to prevent a repeat.
The outage cut off email for people around the world. Microsoft said no business email was lost.
Older servers missed the bug
The flaw entered Microsoft’s network in July through a Windows update used on gateway servers, according to the company’s report. Those servers connect users to Outlook email and other Microsoft 365 services. Standard versions of Windows were not affected.
The bug sat dormant for more than three months. Under heavy demand, a process that establishes incoming connections could slow down until servers ran out of computing power and memory.
Newer servers were particularly vulnerable because they could handle more work at once. Microsoft had tested on older machines.
“Our testing did not adequately represent the combination of hardware and traffic mix encountered during this incident,” Microsoft said.
Microsoft plans to use test machines that match those running its services. The new testing is due by the end of March.
Teams traffic added to pressure
Three conditions coincided to trigger the failure, Microsoft said. Nearly 14% of gateway server capacity was offline for routine software updates, leaving fewer machines available to handle traffic.
A routing problem on the Teams gateway in Microsoft’s US East region also shifted Teams traffic worldwide onto the servers handling email. That automatic switch happened about 15 hours before the outage.
Widespread failures began around 8 a.m. Pacific as North American traffic climbed toward its daily peak. Microsoft said the three conditions would have been routine without the bug.
Automatic safeguards spread the outage
Microsoft’s systems moved traffic from unresponsive servers to nearby machines with the same flaw. Those servers then buckled under the extra load. At the low point, more than 80% of the gateway’s North American servers were unresponsive.
The system then moved traffic to other regions. “Within about two hours of the broad failures that began in North America, servers in every region were affected globally,” Microsoft said.
Servers that came back online faced a rush of accumulated demand and froze again. Microsoft plans to restore traffic gradually to recovering machines, though it has not set a date for that change.
Microsoft also plans to change how traffic shifts between regions and separate email servers from surges in other services. Teams traffic will switch gateways only within the affected region, rather than worldwide.
Some fixes are due by the end of the year and others by the end of March. Several have no date yet.
Microsoft said its first customer notice went out about 20 minutes after the outage took hold. It plans to shorten that interval by the end of the year.
Some delayed messages to consumer mailboxes inactive for more than 30 days bounced back to senders. Microsoft said the incident was not caused by a cyberattack and found no evidence of malicious activity.
Take the quizWhat Kind of Holiday Spender Are You? Take the Black Friday QuizStart →
Markets · FintechHow to Calculate Compound Interest: Formula, Examples and the Rule of 72
Lifestyle · Food & HealthNormal Blood Pressure Chart by Age: Healthy Ranges Explained
Lifestyle · Food & HealthWhat Is Raynaud’s Syndrome? Why Fingers Turn White in the Cold
Lifestyle · Food & Health4 Ways Walking After Meals Helps Your Body, Doctors Say



















