Microsoft 365 experienced a significant global outage lasting about 24 hours, starting Thursday midday ET, due to a faulty network upgrade. The outage affected services including Outlook, Teams, and Copilot, disrupting governments, airlines, hospitals, and emergency services in over 70 countries before service was gradually restored.
- Outage originated from a flawed network capacity upgrade, not cyberattack or AI.
- Over 70 countries experienced disruptions, affecting critical public and private sectors.
- Queued emails delayed up to 48 hours, causing notification surges upon service restoration.
What happened
On Thursday around noon Eastern Time, users began reporting outages in Microsoft 365’s services, initially appearing localized to North America before spreading globally. Key tools such as Outlook, Teams, and Copilot became inaccessible, impacting tens of millions worldwide. The disruption severely affected operational capabilities in government institutions, airlines, healthcare, and emergency response organizations, rendering communication and coordination difficult during critical periods.
Microsoft quickly investigated the issue and found it was caused by a fault introduced during a recent network capacity upgrade, which led to widespread server failures. The company emphasized that neither a cyberattack nor AI systems were involved. Throughout the outage, Microsoft’s status updates confirmed a progressive restoration of services as engineers worked to resolve the root technical flaw.
Why it matters
The outage exposed the dependence of multiple critical sectors on Microsoft’s cloud infrastructure, revealing how a single technical error can cascade into extensive global disruptions. Many governments and emergency systems reported operational slowdowns, showing the risks tied to concentrated cloud service reliance. Airlines’ communication broke down, hospitals faced interruptions, and law enforcement encountered challenges, underscoring how digital infrastructure outages can affect real-world outcomes.
This event also illustrates challenges in cloud service restoration logistics, such as handling delayed message deliveries. Microsoft extended email queue duration to 48 hours to ensure message delivery, but users should expect a surge in notifications as systems come back online, temporarily complicating inbox management. The incident serves as a cautionary example for businesses and governments to evaluate their cloud dependence and consider failover strategies.
What to watch next
Microsoft has committed to delivering a full post-incident report that will provide a comprehensive analysis of the outage’s causes and lessons learned. This report will be critical for industry stakeholders seeking to understand how to prevent similar disruptions. In parallel, attention will be on how Microsoft and other cloud providers strengthen network upgrade testing procedures and incident response capabilities to bolster global digital infrastructure resilience.
Users and organizations reliant on Microsoft 365 should monitor ongoing service status updates closely and prepare for residual notification surges as queued emails and messages continue processing. The broader tech ecosystem will also be watching for any regulatory or operational changes prompted by this major outage, as stakeholders reassess the risks of centralizing critical communication systems under one platform.