Source time Edition date
Microsoft 365 Crawls Back to Life After a 24-Hour Outage
Microsoft 365 历经24小时中断后恢复运行
Microsoft 365 users worldwide felt this 24-hour outage, and the company's clarification that a bad update, not a cyberattack or AI, caused it limits how the incident should be read.
Judgment
Microsoft’s decision is whether its promised full post-incident report will disclose the network-capacity-upgrade change and recovery timeline in enough detail for enterprise and government customers to reassess continuity risk; the cost is exposing its own upgrade process to scrutiny.
Basis
Microsoft said the outage began just after 12 pm ET Thursday, spread from North America to more than 70 countries, and was caused by a technical issue—not cyber or AI/agents—introduced during an earlier network capacity upgrade and surfaced after a recent network change. A Microsoft spokesperson said the company had addressed the underlying issue and was restoring remaining customers and regions. Microsoft also increased email queue time to 48 hours so messages sent during the outage could be delivered. Independent researcher Jonathan Leitschuh warned users may get a flood of notifications as subsystems return. Governments from Japan to the United States, airlines, law enforcement and emergency services, and hospitals reported disruptions. The mechanism matters: a capacity-upgrade change cascaded into core Microsoft 365 services, so the report’s detail will determine whether customers treat this as a contained upgrade failure or a continuity-risk signal.
Unclear The source does not identify the specific network change, the affected Microsoft 365 components by region, or the financial and safety impact beyond reported disruptions.
Next Check Microsoft’s status page for the promised full post-incident report and whether it names the network-capacity upgrade, affected regions, and remaining restoration dates.