Root Cause and Timeline
The disruption first emerged on Thursday when users began reporting inability to access Microsoft 365 products. Microsoft formally acknowledged the issue at 17:54 GMT on Thursday, initially noting that users in the Americas were unable to access Exchange Online mailboxes. Shortly after, the company warned that the disruption might be affecting Microsoft 365 services globally.
Microsoft stated that the technical issue was introduced during a “network capacity upgrade.” The company explicitly clarified that the outage was not caused by a cyber-attack or an artificial intelligence agent. Engineers worked through the night to restore services, but by 04:36 on Friday, the company reported only a “partial recovery” in some regions. By 13:32 on Friday, Microsoft indicated “broader improvements” in North America, “sustained improvements” across much of Europe, and “encouraging recovery signals” in the Asia-Pacific region. The company noted that services were restored gradually to ensure stability given the scale of the problem.
Global Impact on Critical Services
The far-reaching nature of the outage affected institutions ranging from government bodies to critical infrastructure. In the United Kingdom, parts of the National Health Service (NHS), schools, and police forces were affected. However, UK Cyber Minister Liz Lloyd stated that the incident had a “limited” impact on critical frontline services, such as 999 emergency calls, and that there was no disruption to the transport network.

In North America, the impact was severe. The Canadian national rail network reported that passengers might not receive email updates about their trips, and hospitals across the country faced email issues. In the United States, staff from the House of Representatives indicated to Politico that the outage set back an entire day of legislative work, as their operations were heavily dependent on Microsoft’s Outlook.
Internationally, the Japanese government and the Supreme Court of the Philippines experienced disruptions. In Australia, the spy agency was among those affected. The outage also impacted the COP31 climate summit in Antalya, Turkey, where officials and advisers were unable to access Outlook. In India and Singapore, government systems and general business operations were disrupted on Friday.
Economic and Personal Consequences
The outage did not just affect large institutions; it also halted operations for smaller businesses and individuals. Peter Pentz, a winemaker in South Africa, described his business as being brought to a “standstill.” He reported that communication with export partners was halted and “critical production work” stopped because his Cape West Coast winery relies on these systems for day-to-day operations.
In England, a resident named Georgia from Staffordshire reported that the outage delayed her first house purchase after an eight-month wait. Her solicitor indicated that delays were likely due to an inability to contact other agencies, noting that hundreds of house completions were scheduled for that day, making phone-based coordination unfeasible.

Expert Analysis and Resilience Concerns
While some workers may have viewed the loss of email access as an opportunity for a break, cybersecurity and IT experts emphasized the incident’s implications for corporate resilience. Rob Demain, chief executive of cybersecurity firm e2e-assure, described the event as a “stark reminder” of how heavily businesses and vital services rely on a small group of big tech providers.
Matt Saunders, field chief technology officer at tech consultancy Adaptavist, noted the difficulty in mitigating such risks. “Classic IT disaster planning strategies suggest using a second service for resilience, but in practice, it’s almost impossible for a business to function without tools such as Microsoft,” Saunders said. He argued that organizations must now develop concrete plans for operating without these specific tools when similar incidents occur.
Microsoft apologized for the disruption, stating, “We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously.” A full post-incident report is expected to be released once Microsoft has completed its internal review.



