A global Microsoft outage crippled businesses and public services worldwide, affecting millions of users for more than 12 hours on Thursday and Friday. The tech giant said it was seeing “early signs of stabilisation” after the failure disrupted key services including Microsoft Teams and Outlook email.
Some but not all users reported problems, and Microsoft stated there were no indications that the outage was caused by a cyber-attack. The incident highlights the vulnerability of relying on a single provider for critical communication and productivity tools.
What Happened: Microsoft 365 Outage Details
The outage began on Thursday and persisted into Friday, impacting millions of users globally. Microsoft 365 apps, used by over 430 million people, were among the affected services. More than 90% of Fortune 500 companies use Copilot, Microsoft’s AI chatbot, according to the company, underscoring the widespread impact on enterprise operations.
Microsoft acknowledged the disruption and said it was working to restore services. By Friday, some users reported improvements, but the company cautioned that recovery was ongoing. “We’re seeing early signs of stabilisation,” Microsoft said in a statement, without providing a specific timeline for full resolution.
Impact on Businesses and Public Services
The outage disrupted everyday operations for businesses and government agencies alike. Teams and Outlook are integral to remote work and communication, and their failure left many organizations scrambling. Public services, including healthcare and education, also faced disruptions as they rely on Microsoft’s cloud infrastructure.

Small businesses and large enterprises alike felt the pinch. With millions unable to access email or collaborate via Teams, productivity took a hit. The incident serves as a reminder of the risks associated with concentrated reliance on a few tech giants for essential services.
Microsoft’s Response and Recovery Efforts
Microsoft quickly mobilized its engineering teams to address the outage. The company ruled out a cyber-attack as the cause, though it did not specify what triggered the failure. Recovery efforts focused on restoring services and communicating with affected customers.

As of Friday, Microsoft reported progress but stopped short of declaring full restoration. The company’s transparency during the crisis has been mixed, with some users criticizing the lack of detailed updates. However, the acknowledgment of “stabilisation” signals that a fix is underway.
Key Takeaways from the Microsoft Outage
- Widespread impact: Over 430 million Microsoft 365 users and 90% of Fortune 500 companies using Copilot were affected.
- No cyber-attack suspected: Microsoft stated there were no indications of a security breach.
- Services affected: Teams, Outlook, and other Microsoft 365 apps experienced disruptions.
- Recovery ongoing: Early signs of stabilisation emerged, but full restoration was not yet confirmed.
- Business continuity concerns: The outage highlights the risks of relying heavily on a single cloud provider.
Comparison of Major Cloud Outages
| Outage | Year | Duration | Affected Users/Services | Cause |
|---|---|---|---|---|
| Microsoft 365 Outage | 2025 | 12+ hours | 430M+ users, Teams, Outlook | Under investigation |
| AWS Outage | 2021 | ~7 hours | Multiple websites and apps | Network device failure |
| Google Cloud Outage | 2019 | ~4 hours | Google services, third-party apps | Configuration error |
The table above shows how major cloud outages compare in scale and duration. Microsoft’s latest incident stands out for its length and the number of users affected.

What to Watch Next
Microsoft is expected to release a root cause analysis in the coming days. Customers will be looking for assurances that steps are being taken to prevent similar failures. The outage may also accelerate discussions about multi-cloud strategies and redundancy planning. The background to this story is set out in Microsoft 365 Outage: Outlook and Teams Down Worldwide. A related thread runs through Microsoft Outage Hits Outlook, Teams and Government Services. Earlier coverage in Microsoft 365 Outage Hits Outlook and Teams Users Worldwide shows how the argument developed.
For businesses, the event underscores the need for contingency plans. Relying solely on one provider for critical services can leave organizations exposed. As Microsoft works to fully restore services, the focus will shift to accountability and resilience. A closer look at the same subject appears in Microsoft 365 Outage Sends Australia Back to Pre-Email Era. Anyone following the wider picture can start with Microsoft Outage: Millions Hit by Global Service Disruption. The same theme surfaces in Microsoft 365 Outage: Global Disruption and Recovery Timeline, which takes a different angle.

In the meantime, users should monitor official channels for updates. Microsoft’s status page and social media accounts will provide the latest information on recovery progress. Context on how this played out before sits in Claude Outage Hits Worldwide, Adding to Microsoft 365 Chaos. A companion piece, Microsoft Outage: 16-Hour Outlook and Teams Disruption Explained, approaches the same subject from another angle.
FAQ
What caused the Microsoft outage?
Microsoft has not yet disclosed the exact cause, but it stated there were no indications of a cyber-attack. An investigation is ongoing, and a root cause analysis is expected soon.

Which services were affected?
Microsoft Teams, Outlook, and other Microsoft 365 apps experienced disruptions. Some users also reported issues with Copilot, Microsoft’s AI chatbot.
Is the outage resolved?
Microsoft reported “early signs of stabilisation” but has not confirmed full resolution. Some users may still experience intermittent issues.

How can businesses prepare for similar outages?
Businesses should consider multi-cloud strategies, maintain offline backups, and develop contingency plans for critical services to mitigate risks.
As the situation develops, Microsoft’s handling of the outage will be closely scrutinized. The company’s ability to restore trust will depend on transparent communication and robust fixes. For now, users can only wait and watch as recovery efforts continue.
