Microsoft confirmed early Saturday that a 36-hour global outage affecting its Outlook email service and other Microsoft 365 products has been fully resolved. The disruption, which began at approximately 11:17 a.m. EST on November 12, impacted users across 74 countries and territories, including government agencies, healthcare systems, and businesses worldwide.
Microsoft restores services after technical network issue
In a statement posted to X at 1:09 a.m. EST on November 14, Microsoft’s official Microsoft 365 Status account announced: “We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions.” The company attributed the outage to a network capacity upgrade issue that surfaced following a recent network change, explicitly ruling out cyberattacks or malicious activity.
Scope of impact and recovery timeline
The outage disrupted Outlook, Teams, and Copilot, among other Microsoft 365 services, with users in 74 countries reporting issues within an hour of the initial disruption. Downdetector logged over 130,000 reports in the United States alone. Affected sectors included:
- Government agencies in the United States, Australia, Japan, Singapore, and the United Kingdom, where contingency measures were activated.
- Healthcare systems, such as the UK’s NHS, Canada’s Centre hospitalier de l’Université de Montréal, and hospitals in Australia, which reported delays in services.
- Businesses and financial institutions, including delays in stock exchange reporting and trading operations.
- Legislative bodies, such as the U.S. Congress, where staff reported challenges in accessing calendars and communications.
Microsoft stated that services were restored gradually to ensure stability, validating each stage before proceeding. The company noted that some users may still experience intermittent access issues or delayed email delivery as residual backlogs are processed.
Root cause and company response
Microsoft explained that the incident stemmed from an issue introduced during an earlier network capacity upgrade, which became apparent after a routine network change. Engineers initially reported “elevated load” across regions before identifying that servers unexpectedly became unavailable after failing automated health checks. The strain on remaining servers triggered cascading failures, particularly in a core process handling secure connections.
In a post-incident update, Microsoft expressed “deep regret” for the disruption and committed to publishing a full review once the analysis is complete. The company also acknowledged that the gradual restoration process, while time-consuming, was necessary to prevent further instability.
User and institutional reactions
While Microsoft emphasized the technical nature of the issue, affected institutions and individuals described significant operational challenges. A House staffer in the U.S. Congress told POLITICO that the outage had “been a challenge… with no access to our Bible,” referring to the reliance on Outlook for calendars and communications. In the UK, government cyber minister Baroness Lloyd of Effra confirmed that contingency measures were implemented, though she noted “limited reports of impact on frontline service delivery.”
Hospitals in Canada and the UK reported temporary disruptions but confirmed services were restored by Friday. The National Pharmacy Association in the UK warned of potential delays in medication processing, though no major incidents were reported.
Broader implications and historical context
This marks the second major disruption to Microsoft 365 services in 2025, following a nearly 10-hour outage in January attributed to maintenance at a data center in Wyoming. The company has faced multiple incidents this year, including a spam-filter update in October that caused widespread email delivery issues. Microsoft’s reliance on centralized systems has drawn attention to the risks of such dependencies, with experts noting both the convenience and vulnerabilities they introduce.
For users, Microsoft’s Service Level Agreement (SLA) guarantees 99.9% uptime, allowing for approximately 43 minutes of downtime per month. Customers experiencing prolonged disruptions may be eligible for service credits ranging from 25% to 100% of their monthly fees, though claims must be filed through their IT departments.
Further updates on the incident are available in the Microsoft 365 admin center under incident MO1550821.
What’s next
Microsoft has not announced a timeline for its post-incident review but has committed to transparency. The company continues to monitor for residual issues as it processes the backlog of emails and restores full functionality across all regions.