Microsoft 365 and Teams Hit by Major North American Outage
A significant outage impacted **Microsoft Teams** and **Microsoft 365** services, primarily affecting users across North America. The disruption, which began on July 23, caused intermittent access to key services like **SharePoint Online**, **OneDrive**, and **Copilot Chat**, prompting **Microsoft** to advise customers to review their business continuity plans.
A widespread outage on July 23 significantly disrupted **Microsoft 365** and **Teams** services for users primarily in North America.
At its peak, **Downdetector** recorded over 2,400 incident reports, a sharp increase from its typical baseline. **SharePoint** accounted for the majority of complaints (78%), followed by **Excel** (11%) and the **Microsoft 365 Admin Center** (6%).
**Microsoft** acknowledged the issues, directing administrators to incident **MO1437424** in the **Microsoft 365 Admin Center**. The company confirmed that multiple services were degraded.
Impacted services included:
* **Microsoft OneDrive**: Intermittent access.
* **SharePoint Online**: Users encountered "Something went wrong" errors.
* **Microsoft Teams**: Degraded chat functionality, with images failing to load.
* **Microsoft 365 Admin Center**: Slow loading or complete failure to open.
* **Power Automate**: Automation flows not loading.
* **Copilot Chat**: Intermittent delays or failures in chat actions and queries.
* **Microsoft Loop**: Inability to open or load Loop pages.
The outage, which started at 10:44 AM ET, affected users accessing **Microsoft 365** through specific network paths in North America.
Initially, **Microsoft** attempted to reroute traffic for some affected infrastructure, reporting a partial recovery for a segment of users. However, services remained impacted for many, with initial mitigation attempts proving unsuccessful and no immediate ETA for resolution.
During the prolonged disruption, **Microsoft** advised customers to "review their business continuity and disaster recovery plans and take actions appropriate for their environment."
By 1:55 PM ET, **Microsoft** indicated they had likely identified the cause and were deploying mitigation strategies. They expected to share further results within approximately 30 minutes.
Later in the evening, **Microsoft** confirmed that reverting a network update had resolved the issue, with most services reported as recovered.
"We’ve completed reverting the networking update and confirmed through service telemetry and customer reports that this issue is resolved," the company stated.