A bungled network capacity upgrade knocked Microsoft’s core enterprise suite offline for millions of users worldwide, shuttering access to Outlook, Teams, and Copilot from late Thursday into Friday evening.
Microsoft ruled out hostile cyberattacks and rogue artificial intelligence agents. The company blamed internal infrastructure changes instead. Services buckled across dozens of countries, paralyzing corporate communication channels, disrupting government operations, and setting off frantic speculation online before engineers began stabilizing systems.
Systems went dark late Thursday. The disruption widened rapidly through Friday morning as enterprise users logged on to find their email queues frozen and video meetings disabled. Recovery began only by Friday afternoon, though users reported intermittent hiccups well into the evening.
Company engineers tracked the breakdown to a technical cascade triggered by an earlier capacity enhancement that backfired following a routine update.
The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change," Microsoft stated in an official advisory. "We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Microsoft issued an apology for the worldwide blackout, acknowledging the heavy toll on critical enterprise infrastructure across international markets. The disruption hit Microsoft 365, Copilot, Outlook, and Teams simultaneously. The sudden collapse of AI-driven Copilot tools spurred wild theories across social media alleging a cyber strike or unprompted AI automation failures, prompting executive intervention to clarify the purely technical nature of the incident.
| Outage Parameter | Official Detail |
|---|---|
| Affected Platforms | Microsoft Teams, Outlook, Copilot, Microsoft 365 |
| Root Cause | Network capacity upgrade fault following recent network change |
| Malicious / AI Origin | Excluded; confirmed purely technical |
| Timeline of Outage | Initiated late Thursday; gradual recovery Friday afternoon |
| Geographic Impact | Dozens of countries globally |
Microsoft opted against a sudden global reboot, fearing immediate traffic surges would collapse recovering servers.
Instead, technical teams staggered the revival region by region.
We are seeing broad recovery and stability across our services," Microsoft confirmed. "Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
Microsoft pledged to release a comprehensive post-incident report detailing the exact failure points of the network upgrade once internal teams conclude their post-mortem inquiry.