A major Microsoft 365 outage disrupted access to multiple enterprise cloud services on July 23, 2026, affecting organizations primarily in the North America region. The incident impacted critical productivity tools including Microsoft Teams, SharePoint Online, OneDrive, Copilot Chat, Microsoft Purview, and Power BI, creating widespread challenges for businesses relying on Microsoft’s cloud infrastructure.
Microsoft tracked the disruption under incident ID MO1437424, with the outage beginning at approximately 8:14 PM IST on July 23, 2026. The company declared service restoration at 11:56 PM IST the same evening, bringing an end to several hours of disrupted operations for affected customers.
Which Services Were Affected by the Outage?
The outage impacted a substantial portion of the Microsoft 365 suite. Affected services included Microsoft OneDrive, SharePoint Online, Microsoft Teams, Copilot Chat, Power Automate, Microsoft Loop, Microsoft Purview, Microsoft Fabric and Power BI, Power Apps, and Copilot Studio. Users encountered difficulties accessing services, loading web applications, retrieving files, collaborating through Teams, running automated workflows, and utilizing Microsoft’s artificial intelligence-powered Copilot features.
Microsoft confirmed on its official Microsoft 365 Status account on X that it was investigating reported issues and directed administrators to review incident MO1437424 in the Microsoft 365 admin center. The disruption particularly affected customers whose Microsoft 365 traffic was routed through the North American network region, though Microsoft did not specify exact error messages users encountered.
What Caused the Service Disruption?
Microsoft’s investigation identified a recent network configuration change as the probable cause of the service disruption. At 11:22 PM IST, the company announced it had begun reverting that configuration change while simultaneously working to reroute traffic across alternative network paths.
The incident highlighted how problematic networking updates can prevent users from accessing multiple cloud applications simultaneously, even when individual applications and customer tenants remain operational. Microsoft explained that its globally distributed infrastructure relies on complex networking configurations to support collaboration, document storage, business automation, AI assistants, analytics, and compliance operations.
How Did Microsoft Restore Service?
Before completing the configuration rollback, Microsoft identified alternate network paths and validated the optimal steps to improve availability. The company expanded traffic-rerouting efforts across its service infrastructure and observed increasing relief in internal telemetry data.
By 12:06 AM IST on July 24, 2026, Microsoft confirmed that its network configuration reversion had completed. Telemetry data indicated services had recovered following the rollback. The company continued monitoring the environment and contacted a sample of previously affected users to validate that normal service had returned. The incident was ultimately marked as “Service restored.”
Microsoft has not yet published a detailed root-cause analysis or post-incident report. Organizations that experienced the outage should review Microsoft 365 admin center health alerts and assess whether delayed workflows, file synchronization, Teams meetings, Power BI dashboards, or Purview compliance activities require follow-up actions. Further technical details may be released through the Microsoft 365 admin center under incident MO1437424.
Source: Cybersecurity News