Microsoft’s extensive outage of its 365 cloud services began Thursday midday and continues to challenge the tech giant, affecting millions of users worldwide and prompting urgent mitigation efforts.
- Outage affects Microsoft email, cloud, and AI services globally
- Impacts governments, hospitals, courts, and financial institutions
- Cause traced to server health check failures, not hacking
What happened
On Thursday afternoon, Microsoft 365 experienced a large-scale outage impacting a broad range of its cloud-based services including email, AI tools, and other enterprise offerings. The disruption has affected users worldwide, including critical sectors like healthcare, public safety, and government agencies. Early investigations by Microsoft identified the problem as a failure in automated server health checks, which led to widespread server unavailability across multiple regions.
Despite intensive efforts by Microsoft’s engineers, attempting infrastructure isolation and component restarts, intermittent problems persisted through Friday. The company extended email timeout to 48 hours to reduce the risk of data loss as they continue recovery. Microsoft's updates indicate gradual improvements in some areas but confirm ongoing issues with service stability, especially under traffic loads.
Why it matters
This outage is potentially one of the largest and most disruptive cloud service failures recorded, with an estimated 450 million Microsoft 365 commercial subscriptions worldwide. The impact has been severe and wide-ranging: hospitals struggled to send critical patient updates, financial institutions could not process transactions due to missing verification codes, and courts including the Philippines Supreme Court experienced operational interruptions.
Governments such as in Japan reported IT infrastructure disturbances, and law enforcement agencies encountered difficulties in administrative functions. These cascading failures highlight the high dependency global organizations place on Microsoft’s cloud infrastructure and emphasize the risk posed when such centralized services experience downtime.
What to watch next
Microsoft is expected to release a detailed post-incident report once mitigation efforts are complete, outlining the root causes and planned steps to prevent recurrence. Critical for stakeholders will be the company’s proposed strategies for improving resilience against similar failures, especially as reliance on cloud services continues to grow.
Industries and governments will likely reassess their contingency plans and reliance on single-cloud providers to mitigate future risk. Observers will monitor how quickly Microsoft restores full service stability and whether improvements to monitoring and health check mechanisms reduce the risk of future outages at this scale.