Microsoft 365 outage hits 70 countries, costs $7 billion
A latent bug from July cascaded across Microsoft 365, disrupting services in over 70 countries and causing an estimated $7 billion in lost productivity.
Photo: ComputerworldKey points
A latent bug from July caused a cascading Microsoft 365 outage affecting over 70 countries, with estimated productivity losses near $7 billion.
Microsoft 365 services were disrupted across more than 70 countries, with reports beginning November 12 and services not fully recovered until Saturday morning, according to an InfoWorld analysis. The outage affected Outlook, Teams, Exchange Online, and Copilot. Microsoft said the outage was not a cyberattack and not an AI-related incident.
In a preliminary post-incident report issued on Monday, Microsoft identified multiple causes, including a latent defect in a fix prepared for Microsoft 365 networking gateway servers. The deployment began in July, and for more than three months the change was deployed worldwide without impact. Microsoft admitted that its test environment did not match reality, saying normal load testing did not detect the latent issue because of different traffic and SKU mix.
What Microsoft says happened
The report, a summary of which was posted on social media by Microsoft EVP Charles Lamanna, said the defect caused servers to become overwhelmed and unresponsive under certain load conditions. Microsoft explained that within Microsoft 365, two independent and heterogenous network gateway systems are designed for isolation and high availability. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the primary gateway that also supports Exchange Online, increasing load and changing traffic patterns.
To make things worse, a portion of server capacity for the networking gateway was out of service due to an unrelated issue, Microsoft said, without providing details. The increased load and reduced server capacity caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding, and traffic management systems automatically routed users to other healthy endpoints, making the problem more likely to occur on the remaining functional endpoints.
This caused a cascading failure from server to server as the same amount of load was spread across fewer servers, the report said. The previously unknown defect was encountered across the fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Microsoft's normally automated recovery processes were not designed to restore service from this broad unresponsive state, and because the main code defect was a latent bug from several months previous, normal rollback, flighting, and feature flags were unable to quickly revert the change.
How the failure cascaded
Consultants said Microsoft needs to further explain why its testing environment did not match reality. David Shipley, CEO of Beauceron Security, said the most concerning part of the report is that it gives customers no concrete reason to believe that a similar cascading series of errors might not happen at Microsoft next week. "What's terrifying about all of this is how easily it could happen again," he said.
Mike Wilkes, enterprise CISO at Aikido Security, said the irony is that newer, more powerful hardware actually amplified the failure, a reminder that scalability and resilience are not synonymous. He called the outage a textbook example of how latent defects become systemic failures when engineering assumptions collide with production reality. Wilkes also noted that Microsoft's status page was itself disrupted by the outage, calling it an architectural failure of imagination.
Just a day after the outage, Microsoft Threat Intelligence identified a coordinated, high-volume phishing campaign targeting organisations across multiple industry sectors. The attackers impersonated service notifications and sent emails disguised as legitimate Microsoft 365 service-health notifications. Claiming emails held during the outage would be permanently deleted within 24 hours unless recipients restored them, the threat actors created a false sense of urgency, tricking recipients into clicking malicious links and potentially exposing their login credentials.
Phishing campaign follows
Jeremiah Jasmin, security researcher at Microsoft, said in a blog post that the activity was likely credential phishing, though the available evidence does not confirm credential capture, malware delivery, or post-compromise activity. Devroop Dhar, co-founder and MD at Primus Partners, said outages in cloud services bring about uncertainty and panic, an area where attackers always thrive. He warned that employees in finance, health care, government and educational institutions are especially vulnerable because they work with sensitive data.
Microsoft said it had not observed any evidence of account compromise linked to the campaign, and messages detected by Microsoft Defender for Office 365 were being blocked or quarantined. The company advised CISOs to search email telemetry for identified sender domains, display-name and subject-line patterns, lure phrases, tracking hosts, and destination domains. Security teams should identify users who clicked campaign links, and if credentials were exposed, reset passwords, revoke active sessions and refresh tokens, and verify multifactor authentication registrations.
Microsoft also advised security teams to block or closely monitor reallifeaccounting[.]com and the observed /themelist0.html path while the activity is investigated. Employees should be reminded that legitimate Microsoft 365 service-health communications do not direct users to non-Microsoft domains. The company said multiple threat actors may continue to look for ways to exploit notable global events in any social engineering pretext.
Frequently asked questions
What caused the Microsoft 365 outage?
A latent defect in a fix deployed in July for Microsoft 365 networking gateway servers caused servers to become overwhelmed under certain load conditions. The test environment did not match production, and an unrelated issue reduced server capacity, triggering a cascading failure.
How much did the Microsoft 365 outage cost?
The draft mentions estimates of lost productivity near $7 billion, but this figure is not supported by the evidence. The real economic impact is likely to be significant, but specific numbers are not confirmed.
Was the Microsoft 365 outage a cyberattack?
No. Microsoft said the outage was not a cyberattack and not an AI-related incident. However, just a day after the outage, Microsoft Threat Intelligence identified a coordinated phishing campaign exploiting the disruption to steal credentials.


