Microsoft 365 outage reportedly affects 100,000 users worldwide

By Tom Whitfield

More than 100,000 users worldwide were reportedly struggling to reach their email inboxes as a global Microsoft 365 outage hit Outlook and other enterprise services. Microsoft confirmed service degradation on its Service Health Status page across Microsoft 365 Business and Enterprise services, warning that the issue could block access to affected services.

Microsoft wrote earlier: “We’re aggressively pursuing all pathways to reduce impact.” That commitment covered several courses of action, but no restoration schedule.

The affected portfolio reached well beyond email. Microsoft listed these services as potentially affected:

• Exchange Online
• Microsoft Teams
• SharePoint Online
• Copilot
• Microsoft Defender XDR
• Multiple Purview services

One outage, several headline risks. The company reported no separate failure counts for those products.

How did Microsoft respond to the server failures?

Microsoft said elevated loads followed a large number of servers becoming unexpectedly unavailable, which shifted demand onto the remaining infrastructure. It was investigating what made the servers fail while working to return them safely to service.

As a precaution, Microsoft paused all deployments and configuration changes while its engineers reviewed recent changes for any correlation with the event. The pause narrowed the field of recent changes that could explain the outage.

What did Microsoft validate?

In an update released around 10 a.m. NZT, Microsoft disclosed: “We’ve validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we’re now applying this change more broadly.”

Microsoft also prepared an automated recovery process to detect and restart unresponsive servers continually, keeping them in service while the change progressed. Its review of recent changes had identified a small number of configuration updates as potential contributors, which the company said it was still investigating.

Validation then produced its own complication. While Microsoft tested the targeted change, many affected servers became unresponsive, preventing the company from confirming whether the change worked. Microsoft said it was restarting those servers so they could return online with the change applied, then extending the same approach to additional affected infrastructure.

The distinction matters. Microsoft had restored servers in the validated subset, but a broader return to service still depended on restarting unresponsive machines and testing the result. Recovery and validation were proceeding at different speeds.

What does this change for Microsoft 365 administrators?

The immediate change is procedural: deployments and configuration changes remain paused during Microsoft’s review, while the alternative health check expands across affected infrastructure. The automated restart process adds another layer of recovery, but Microsoft did not provide a full restoration timetable.

For administrators, that means continued uncertainty across Outlook, Exchange Online, Teams, SharePoint Online, Copilot, Defender XDR and Purview until the remaining infrastructure stabilises. The cause also remains open: a small number of configuration updates are under investigation, rather than a confirmed root cause.

How large was the disruption?

Media reports put the number of users struggling to access email inboxes above 100,000 worldwide. Down Detector showed a spike of almost 1,400 local reports of Outlook issues by 7.30 that morning.

The scale matches Microsoft’s description of a global incident affecting business and enterprise tenants. It does not settle the cause. Until the restart work and configuration review produce a clear answer, the operational picture remains incomplete.