Microsoft 365 Services Fail Across North America

A broad Microsoft failure interrupted both workplace and gaming platforms on Thursday morning, cutting off thousands of users across North America from the tools they rely on every day. Teams, OneDrive, SharePoint, Outlook, Copilot, and Xbox Live all became difficult or impossible to reach during the same window, turning an ordinary weekday into a scramble for administrators and end users alike.

Complaints started piling up on the outage-tracking site Downdetector shortly after 10:30 a.m. ET on July 23. SharePoint dominated the reports at 78 percent of all complaints, with Excel accounting for 11 percent and the Admin Centre making up 6 percent. The distribution points to collaboration and file-access layers taking the hardest hit, which is consistent with the range of services users flagged as unreachable.

Microsoft confirmed the disruption publicly, acknowledging that a portion of its North American user base could not access or properly use a range of Microsoft 365 services. The company said it was reviewing service telemetry and diagnostic data in an effort to pinpoint where the impact originated.

Which Microsoft Services Were Affected

The company's Service Health Status page listed degraded service across multiple products for traffic moving over certain network routes. Administrators were pointed toward incident MO1437424 inside the Microsoft 365 admin center for tracking details.

The affected lineup covered a wide slice of Microsoft's ecosystem:

  • Microsoft 365
  • Teams
  • Outlook
  • SharePoint
  • OneDrive
  • Copilot
  • Microsoft Store
  • Power Automate

That spread meant email, chat, document storage, AI assistance, and workflow automation could all be interrupted at once for the same user — a reminder of how tightly bundled these products have become inside a single account.

Xbox Live Goes Dark During the Same Window

Gaming services fell over alongside the productivity stack. Xbox tech support said on X that it was aware of users hitting errors while trying to connect to Xbox services and features, and that its engineers were working to reduce the impact.

According to the Xbox Support website, the disruption reached across nearly every consumer-facing part of the platform, including:

  • Store and subscriptions
  • Friends and social activity
  • Cloud gaming and remote play
  • Games and gaming
  • Apps and mobile

Those problems were felt on Xbox Series X|S, on PC, and on handhelds compatible with Cloud Gaming. The timing landed badly for players trying to jump into the early access launch of Halo: Campaign Evolved, who found themselves locked out at exactly the moment they expected to be playing.

A Separate Azure Incident in West US Compounded the Damage

While Microsoft 365 and Xbox users were struggling, a second and distinct problem hit Microsoft's Azure cloud platform in the West US region. Starting at roughly 14:44 UTC on July 23, customers ran into intermittent connectivity failures, higher latency, and trouble reaching Azure services.

The impacted Azure services included Application Gateway, Azure Kubernetes Service, Azure Firewall, ExpressRoute, VPN Gateway, and Power BI Embedded, among others. For organizations running production workloads in that region, the failure touched networking, container orchestration, security, and analytics simultaneously.

Microsoft said it had pinpointed the likely cause and had begun rolling out mitigation steps. Its most recent update at the time, posted at 18:12 UTC, indicated the company was watching service recovery closely as those fixes propagated.

No Firm Restoration Timeline Was Provided

By early Thursday afternoon, Microsoft still had not committed to a timeline for bringing everything fully back online. The cause behind the Microsoft 365 disruption remained under investigation.

The picture was complicated further by activity elsewhere on Downdetector. During the same period, the tracker registered access problems at Amazon Web Services, Cloudflare, and OpenAI. That overlap raises the possibility that the underlying network trouble reached past Microsoft's own systems and into infrastructure shared more broadly across the internet.

What Administrators Could Do During the Outage

With no estimated fix time available, the practical options were limited. IT teams were directed to incident MO1437424 in the Microsoft 365 admin center, which served as the reference point for status updates on the degraded services. Because the degradation was described as affecting traffic over particular network routes rather than every connection uniformly, the experience varied from user to user — some sessions worked while others failed against the same service.