The 38-odd hours of global disruption has also given rise to opportunistic phishing campaigns; insured losses expected to be under US$350m
After experiencing one of the longest outages in its history (roughly 38 hours when the entire event is counted), Microsoft has now declared that a hidden software bug — not hackers — had caused the global cloud software outage that disrupted Outlook, Teams, and Copilot beginning 12 November 2026.
The firm has apologized for the disruption, and has warned that attackers are exploiting it with phishing emails. Cyber risk analytics firm CyberCube estimates insured losses will likely remain below US$100m. Its spokesperson Jon Laux has noted: “This event once again reminds us how the technology world is concentrated in the hands of a few key providers.”
Earlier, Microsoft had explained that the fault had arisen from an earlier network capacity upgrade, and had surfaced after a recent network change.
Three factors behind the crash
Charles Lamanna, a Microsoft executive, has provided a fuller explanation on X, which PCMag has described as three issues combined that brought down the networking gateway that sits in front of many Microsoft 365 services:
- First, a defect introduced in July 2026 as part of a fix for gateway servers had gone undetected because Microsoft’s test laboratories use less powerful hardware with fewer processor cores than the systems where the problem appeared.
- Second, a small Teams issue on 11 November 2026 had caused Teams traffic to fail over to another gateway, adding load.
- Third, an unrelated problem the previous day had already removed 14% of gateway capacity.
When the bug triggered during peak US traffic, automated rerouting had spread the failure to more than 80% of servers. Engineers then had to patch the servers and restore them one at a time. Microsoft said it would publish a full post-incident report.
Phishing follows outage
An opportunistic phishing campaign has been using emails that appeared to be Microsoft 365 service-health notices and cited “EX1550543”, the genuine incident number. Some messages had maliciously claimed that emails held during the outage would be deleted within 24 hours unless recipients clicked a link.
Microsoft said the activity was “consistent with credential phishing” and that its security products were blocking it. It has advised organizations to verify incidents directly through the Microsoft 365 admin center rather than relying on links in unsolicited messages.
