Microsoft Outage Hits Outlook, Teams, Xbox and Azure

Microsoft Outage Takes Down Outlook, Teams, Xbox, and Azure for Thousands

Thursday started rough for a lot of office workers, gamers, and IT admins alike. Just after 10:30 a.m. ET on July 23, 2026, reports started flooding in for Microsoft 365, Outlook, Teams, SharePoint, OneDrive, Copilot, Azure, Xbox Live, and the Microsoft Store. For a company whose products sit at the center of daily work and play for hundreds of millions of people, that's a lot of core services to lose at once. Yahoo! Geo News

Downdetector, the site that tracks user-submitted outage reports, showed the spike clearly. At 11:11 a.m. ET, the platform recorded 2,403 reports — sharply above its normal baseline of 29. That's not a minor blip; that's the kind of jump that tells you something broke at the infrastructure level, not just for one unlucky user in one office. Bleeping Computer

What Exactly Broke

Not every service failed the same way, and that's part of what made the outage confusing to track in real time.

• SharePoint accounted for 78% of the complaints, with users unable to open shared directories or load team libraries. Bleeping Computer

Teams users had their own headaches. Some got kicked mid-call, others watched chat messages simply refuse to load. On the Outlook side, people described stuck outboxes and repeated login prompts — the kind of thing that makes you wonder if you forgot your own password. [VERIFY: exact percentage breakdown of Outlook-specific complaints]

It wasn't just Microsoft's ecosystem feeling it either. Downdetector also logged access issues around the same window for Amazon Web Services, Cloudflare, OpenAI, Fortnite, and Dropbox — a reminder of how tangled the modern internet's plumbing really is. When one major cloud provider stumbles, the ripple effects show up in places you wouldn't expect. Geo News

The Root Cause: An Azure Network Issue in the West

Microsoft didn't stay quiet for long. The company opened an internal incident, tracked as MO1437424, and confirmed the disruption was affecting several Microsoft 365 applications used for collaboration, file storage, automation, AI, and admin functions. Nationalcioreview

Behind the scenes, the trouble traced back to Azure's networking layer. Microsoft said the issue began at approximately 14:44 UTC on July 23, 2026, and confirmed customers whose traffic passed through West US network infrastructure could see downstream impact. In plain terms: a networking hiccup in one region ended up dragging down services for users who had nothing to do with that region directly, simply because their traffic happened to route through it. Data Center Dynamics

Microsoft's engineering team leaned on a familiar fix for this kind of problem. The company rerouted traffic away from the affected infrastructure, and early telemetry showed that move led to partial recovery for some users. It wasn't an instant fix, but it was a start. Bleeping Computer

How Long Did It Last?

This is the part that matters most for anyone who lost hours of productivity. Reports on the exact timeline vary slightly depending on the source, but the shape of the day looks like this:

1. Morning: Complaints spike starting around 10:30–10:44 a.m. ET, with SharePoint, Excel, and Teams hit hardest.

2. Midday: Microsoft acknowledges the issue publicly and opens an internal incident ticket, pointing affected admins to the Microsoft 365 Admin Center for updates.

3. Afternoon: Traffic rerouting begins showing results, with complaint volume dropping to under 30 users by around 2 p.m. FOX 5 DCFOX 7 Austin

4. Evening: By 9:55 p.m. ET, the outage was confirmed resolved. Bleeping Computer

So, start to finish, this was roughly an 11-hour disruption — long enough to derail a full workday for teams that depend on SharePoint and Teams to function.

Not Microsoft's First Rodeo This Year

If this felt familiar, it's because it kind of was. Earlier in the year, a separate Microsoft 365 service degradation affecting email and calendaring was discovered on January 22, 2026, and wasn't fully resolved until 5 a.m. the next day — roughly 15 hours of disruption that time. Microsoft attributed the recovery in that case to load-balancing adjustments rather than a single quick patch. bu
Two significant outages within the same year raises a fair question for IT departments: how much single-vendor dependency is too much? That's not a knock on Microsoft specifically — every major cloud provider has had its bad days — but it's the kind of thing that pushes companies toward multi-cloud backup plans, offline file caching, and communication tools that don't all live under one roof.

What Users Can Do When This Happens Again

Outages like this aren't rare anymore, and they probably won't stop happening. A few practical habits make the next one easier to ride out:

• Check Downdetector or the Microsoft 365 Admin Center first before assuming it's your own connection or device.

• Keep a secondary communication channel (a personal phone number, a non-Microsoft messaging app) for urgent coordination during Teams outages.

• Enable offline access for critical Excel and Word files so a SharePoint hiccup doesn't lock you out of your own work.

• Don't panic-reset your password after repeated login prompts — that's a known symptom of these outages, not necessarily a sign your account is compromised.

The Bottom Line

Big cloud outages are the price of convenience. Microsoft's 365 suite, Azure, and Xbox Live all sit on shared infrastructure, and when one piece of that infrastructure buckles — this time a networking issue in the West US Azure region — the effects fan out fast and wide. Microsoft got things stabilized within a day, which is roughly in line with how it handled January's incident. Whether this becomes a once-a-year headache or a more frequent one is the thing worth watching going forward.

Got hit by Thursday's outage? Drop your experience in the comments — and if you're relying on Microsoft 365 for business-critical work, it might be worth reviewing your backup plan before the next one hits.