
Update 7/23/26 9:55 PM ET: Article updated that the outage has been resolved.
Microsoft is impacted by a massive outage affecting Teams and Microsoft 365 services, primarily affecting users in North America.
At 11:11 AM ET on July 23, Downdetector recorded 2,403 reports, sharply above its normal baseline of 29. SharePoint accounted for 78% of the complaints, followed by Excel at 11% and the Microsoft 365 Admin Center at 6%
"We're investigating reports of issues with Microsoft 365 services," Microsoft said in a statement, directing administrators to incident MO1437424 in the Microsoft 365 Admin Center.
Microsoft has confirmed that multiple services are degraded, and you will run into issues when opening OneDrive. Likewise, SharePoint Online users may encounter a "Something went wrong" error.
- Microsoft OneDrive - Access to OneDrive is intermittent.
- SharePoint Online - Error message, "Something went wrong"
- Microsoft Teams - Degraded chat functionality, including images not loading.
- Microsoft 365 Admin Center - Admin Center is loading slowly or not at all.
- Power Automate - Automate flows not loading.
- Copilot Chat - Intermittent delays or failures in any Copilot Chat action and query.
- Microsoft Loop - Unable to open or load Loop pages.
According to the company, Microsoft Teams chat functionality is also degraded, with some users reporting that images are not loading.
The Microsoft 365 Admin Center may load slowly or fail to open, while Power Automate flows may not load.
The outage began at 10:44 AM. ET on July 23 and affects users accessing Microsoft 365 through certain network paths in North America.
Microsoft says it has rerouted traffic for some of the affected infrastructure, and its initial telemetry indicates that the change has resulted in a partial recovery for some users. However, services still remain impacted for many, with Microsoft saying that its initial attempts were unsuccessful and that there was no ETA for when the outage would be resolved.
This led the company to warn customers to review their business continuity and disaster recovery plans.
"Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment," read an earlier status update.
As of 1:55 PM ET, Microsoft says it may have found the cause of the issue and is deploying mitigations, and expects to share results at approximately 2:30 PM ET.
"We may have identified the likely cause of the issue and are actively deploying mitigation actions," reads Microsoft's latest status update.
"Based on our current progress, we expect to have additional information on the effectiveness of these actions within approximately 30 minutes. We are closely monitoring service recovery as this action is rolling out. "
Update 9:55 PM ET: Microsoft tweeted earlier this evening that it reverted a network update that resolved the issue, and that most people should now see services recovered.
"We’ve completed reverting the networking update and confirmed through service telemetry and customer reports that this issue is resolved," Microsoft posted on X.
Test every layer before attackers do
Security teams log 54% of successful attacks and alert on just 14%. The rest move through your environment unseen.
The Picus whitepaper shows how breach and attack simulation tests your SIEM and EDR rules so threats stop slipping by detection.
Get the whitepaper
