Microsoft 365 Outage Disrupts Teams, Copilot, and Purview for North American Users
A widespread Microsoft 365 outage, identified as MO1437424, impacted key services including Teams, Copilot, and Purview for users in North America due to a network configuration error.
Microsoft 365 services experienced a significant disruption on July 23-24, 2026, affecting a broad range of enterprise applications for users primarily in the North American region. The outage, tracked under incident ID MO1437424, began around 8:14 PM IST on July 23rd and was officially resolved by 11:56 PM IST the following day. The incident temporarily impacted productivity, collaboration, and compliance operations for organizations heavily reliant on Microsoft's cloud ecosystem.
The affected services spanned a critical portion of the Microsoft 365 suite, including Microsoft Teams, SharePoint Online, OneDrive, Copilot Chat, Power Automate, Microsoft Loop, Microsoft Purview, Microsoft Fabric, Power BI, Power Apps, and Copilot Studio. Users reported difficulties accessing applications, loading web interfaces, retrieving files, participating in Teams meetings, running automated workflows, and utilizing AI-powered Copilot features. While specific error messages were not detailed by Microsoft, the company confirmed that the issue was concentrated among users whose traffic was routed through the North American network infrastructure.
Microsoft's official Microsoft 365 Status account on X acknowledged the reports of issues, directing administrators to incident MO1437424 within the Microsoft 365 admin center for updates. The company's investigation quickly pointed to a recent network configuration change as the likely culprit behind the widespread service degradation. This type of issue can cascade through complex, globally distributed cloud infrastructure, preventing access to multiple applications simultaneously even if the individual services and customer tenants remain technically operational.
In response, Microsoft initiated a two-pronged approach to restore services. The company began reverting the problematic network configuration change while simultaneously working to reroute traffic across alternative network paths. This strategy aimed to mitigate the immediate impact and expedite the restoration process. Microsoft stated that telemetry data indicated an "increasing relief" in service availability as these measures took effect.
By 12:06 AM IST on July 24th, Microsoft confirmed the completion of the network configuration rollback. Subsequent telemetry confirmed that services had recovered following the reversion. The company continued to monitor the environment and engaged with a sample of affected users to verify the return to normal operations. The incident was officially marked as "Service restored."
This outage underscores the critical dependency businesses have on the underlying network infrastructure that powers cloud services. A single misconfiguration can have far-reaching consequences, disrupting essential functions from communication and data storage to business automation and AI-driven insights. Organizations affected by the outage are advised to review their Microsoft 365 admin center health alerts and assess any operational impacts.
Administrators may need to follow up on delayed workflows, file synchronization issues, or interrupted Power BI reporting and Purview compliance activities. While Microsoft has not yet released a detailed post-incident report, further technical information may become available through the Microsoft 365 admin center under incident MO1437424. The incident serves as a reminder of the potential vulnerabilities inherent in complex, interconnected cloud environments.