Key takeaways
- Microsoft experienced a roughly 18-hour outage Thursday-Friday that disabled Outlook, Teams, cloud storage, Copilot and Defender across its global infrastructure.
- The company stated servers became unexpectedly unavailable but provided no technical explanation or timeline for completing its investigation.
- This marks Microsoft's second major outage in three months, following a September failure the company attributed to a core authentication configuration issue.
- The incident will likely prompt enterprises to evaluate their dependence on a single cloud provider and strengthen disaster recovery procedures.
Microsoft restored service Friday morning after an outage that lasted approximately 18 hours and disrupted email, video conferencing, cloud storage and artificial intelligence services worldwide. The company disclosed that a “large number of servers being unexpectedly unavailable” triggered the cascade but has not identified the technical cause.
The incident began Thursday affecting Outlook email and Microsoft Teams in the U.S. and the Americas. By Thursday evening, the problem had spread globally across Microsoft’s infrastructure, disabling cloud services that millions of users depend on for daily work. By Friday morning on the U.S. east coast, Microsoft reported that recovery had begun, with Outlook functionality returning and email traffic resuming to affected accounts.
Timeline: From Regional Disruption to Global Crisis
The outage commenced Thursday with Outlook and Teams functionality going offline for users in North America. Microsoft’s engineers immediately began investigating but could not quickly identify the failure point.
As hours passed, the problem expanded beyond email and video conferencing. Microsoft’s cloud services that store files, host documents, and enable collaborative work went down. Artificial intelligence services, including Copilot, became unavailable. Defender security software, which provides malware and threat scanning, also went offline.
By Friday morning, approximately 18 hours into the incident, Doug Madory from Kentik, which monitors global internet traffic, noted on Bluesky that traffic to Microsoft services had resumed, indicating the infrastructure had begun accepting requests again. Emails started trickling back into affected inboxes, though some users experienced delays before full restoration.

Services Knocked Offline
Email and Collaboration
Outlook email service went offline, preventing users from sending or receiving messages. Microsoft Teams video conferencing and chat features became unavailable, blocking real-time communication.
Cloud Storage and Documents
Microsoft 365 cloud storage, including OneDrive and SharePoint, went offline. Users could not access saved files or collaborate on documents stored in the cloud.
Artificial Intelligence and Security
Copilot, Microsoft’s AI assistant available standalone and integrated into Windows and Microsoft 365, became unavailable. Defender security software, bundled with Windows and Microsoft 365, went offline.
Administrative Tools and Infrastructure
System administrators managing Microsoft cloud infrastructure through Intune lost access to management dashboards. Some users with cloud-hosted Windows systems reported they could not access those machines.
Scope Across Industries
The outage affected organizations across financial services, healthcare, government, education and media sectors. TechCrunch reported its own email was knocked offline by the incident. Many businesses that operate entirely on Microsoft 365 for email, file sharing and team communication experienced complete disruptions to their ability to work.
Microsoft’s Explanation: Limited Detail
Microsoft provided minimal technical information about the cause. In public statements, the company said only that servers had become “unexpectedly unavailable,” without explaining whether the failure was caused by a software bug, configuration error, hardware malfunction or another issue.
The company stated in Friday updates that it found “no evidence of malicious activity associated with this incident.” However, Microsoft did not explain what monitoring systems, logs or other evidence it reviewed to reach that conclusion. When asked whether the company possessed the technical capabilities to detect intrusions or provide a detailed explanation of what occurred, Microsoft did not respond.
Recurring Pattern of Outages
In September, Microsoft experienced a multi-day outage that the company attributed to “a core authentication configuration” issue. That incident prevented access to cloud services globally. The September outage and the Thursday outage represent two significant infrastructure failures within a three-month window.
The recurrence raises questions about whether Microsoft’s infrastructure possesses adequate redundancy, real-time monitoring and rapid recovery procedures. Companies and individuals whose business operations depend on Microsoft’s platform rely on a level of stability and availability that recurring major outages may undermine. Each incident creates risk for dependent organizations, from lost productivity to potential revenue impact and damaged customer relationships.
Recovery and Remaining Questions
By Friday morning U.S. east coast time, Microsoft’s services were recovering. However, full restoration of service took longer than the initial recovery began, and some users experienced intermittent issues as systems came back online.
Microsoft has not provided a timeline for completing its investigation into the cause or shared plans for preventing future similar incidents. The outage has renewed questions about Microsoft’s infrastructure resilience, including whether its systems possess adequate geographic redundancy, whether monitoring tools can detect failures in real time, and whether incident response procedures can accelerate recovery.
The incident will likely prompt customers to evaluate their dependence on a single cloud provider and review their internal disaster recovery procedures. For organizations that operate entirely within Microsoft’s ecosystem, the outage demonstrated the risk of centralized infrastructure and the value of backup systems and contingency plans.
Source: TechCrunch
Frequently Asked Questions
When did Microsoft's outage occur and how long did it last?
The outage began Thursday and lasted approximately 18 hours, with recovery beginning Friday morning on the U.S. east coast. Doug Madory from Kentik noted that traffic to Microsoft services had resumed after about 18 hours of downtime.
Which Microsoft services were affected by the outage?
The outage affected Outlook email, Microsoft Teams, cloud storage and document collaboration, Copilot AI, Defender security software, Intune administrative dashboards and some cloud-hosted Windows systems. It impacted organizations across financial services, healthcare, government, education and media sectors.
What did Microsoft say about the cause of the outage?
Microsoft stated that a large number of servers became unexpectedly unavailable but has not disclosed the technical cause. The company found no evidence of malicious activity, but did not provide details about its investigation timeline, monitoring systems or technical capabilities to detect intrusions.