Microsoft recovers services after global Outlook and cloud disruption

Microsoft services begin recovering after broad outage
Microsoft is recovering from a day-long service disruption that began on Thursday and expanded from Outlook email and Teams video conferencing into a wider global cloud incident. The outage affected consumer and business email, files and documents, while Microsoft Copilot, Defender security screening software and Intune administration features were also unavailable for some users.
By Friday morning on the US East Coast, Outlook had begun to recover and some emails were arriving again. Doug Madory, director of internet analysis at Kentik, said internet traffic was returning to Microsoft services after roughly 18 hours of downtime.
Microsoft initially identified problems in the United States and the Americas, but the impact quickly spread internationally as engineers worked to restore affected servers. Some users also reported difficulties accessing cloud-based Windows computers.
Cause remains under investigation
Microsoft has not identified the root cause. In a status update, the company said a large number of servers had become unexpectedly unavailable and that its investigation was continuing.
The company also stated that it had found no evidence of malicious activity associated with the incident. The failure nevertheless reached far beyond a single application: organisations relying on Microsoft’s hosted collaboration, productivity, security and endpoint-management tools faced simultaneous disruption across multiple operational functions.
The breadth of the affected products illustrates how an interruption in underlying cloud infrastructure can become visible through many separate services. Email and meetings may be the first symptoms staff notice, but administrative access, endpoint controls, AI tools and hosted desktops can be affected at the same time.
A repeat concern for cloud-dependent organisations
Microsoft experienced another major cloud-services incident in September that lasted several days. In that case, the company attributed the access problems to a core authentication configuration issue. No equivalent explanation has yet been provided for the latest outage.
For businesses, the practical implication is to treat a Microsoft 365 or Azure-related interruption as a multi-service continuity event rather than an email-only failure. Teams should test alternative communications, define access to essential documents and maintain clear procedures for work that normally depends on Intune, Defender or cloud-hosted Windows systems.

