Skip to content
Source: Ars Technica

🌩️Microsoft 365 Outage Hits 450 Million Paid Subscribers for Nearly a Day

Your Microsoft stack just went dark. Here's the fallout.

TL;DR

A global Microsoft 365 outage hit email, cloud, and AI services from Thursday midday into Friday morning. Banks, courts, and police offices were stuck working around it. If your team depends on Outlook or Teams, build a fallback plan now.

Microsoft 365 went down globally Thursday and was still limping along Friday morning. Email, cloud, and AI services all took hits, and Microsoft's answer was to stretch email timeouts to 48 hours so messages don't just vanish while recovery drags on. If your team runs on Outlook, Teams, or anything calling Microsoft APIs, this is a reminder that one shared infrastructure failure can take out your whole day. Bank transfers were blocked by verification code failures, and a Colorado sheriff's office said bail postings got harder. Your incident runbook should assume your identity and mail layer goes away for hours. The root cause was a piece of infrastructure under elevated load across multiple regions. It wasn't traffic. Servers started failing automated health checks and dropped out, and some came back only to go unresponsive again once they got traffic. Microsoft put 450 million paid commercial subscriptions on the line, and it still took more than four hours just to be in the weeds on the fix. Microsoft says intermittent access issues and delayed email could linger while mitigation continues. Watch the post-incident report for how they validate alternate health check methods.

Microsoft 365 Outage Hits 450 Million Paid Subscribers for Nearly a Day — Ars Technica

Key Points

1

Microsoft estimated more than 450 million paid Microsoft 365 commercial subscriptions were affected by the disruption across email, cloud, and AI services globally.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

Microsoft 365OutageAzureIncident ResponseEmail

Comments

Subscribe to join the conversation...

Be the first to comment