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.
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.
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.
Microsoft fixes outage affecting MFA setup, MySignIn service
Microsoft warns of surge in ACR Stealer attacks on customers
CISA warns admins to patch actively exploited SharePoint flaws
CISA: Microsoft SharePoint RCE flaw now actively exploited
Microsoft adds smarter bot protection to Teams meetings
This is bigger than just M365. Broad Azure outage: TRACKING ID: ZJV6-SGG TYPE: Incident STATUS: Active COMMUNICATION: Starting at approximately 14:44 UTC on 23 July 2026, customers may have experienced intermittent connectivity failures, increased latency, or difficulty accessing Azure services associated with the West US region. Customers whose traffic traverses affected West US network infrastructure may also experience downstream impact. Impacted services include: API Management, Application Gateway, Azure AD B2C, Azure AI Search, Azure Bastion, Azure Bot Service, Azure Database for PostgreSQL, Azure Databricks, Azure Firewall, Azure Kubernetes Service (AKS), Azure VMware Solutions, ExpressRoute Circuits, ExpressRoute Gateways, Network Infrastructure, Power BI Embedded, Virtual WAN, VPN Gateway We are actively investigating networking and traffic-routing anomalies associated with the onset of impact. We have successfully redirected portions of traffic away from potentially affected network paths and tested mitigation actions. At this time, those actions have not produced a broad improvement in impacted service telemetry. Engineering teams continue investigating routing and network-path anomalies that align with the start of the incident and are evaluating additional mitigation options. While we do not have an estimated time for mitigation at this stage, we will provide updates as they become available. Customers may wish to review their business continuity and disaster recovery plans and take actions appropriate for their environment.
Edit seems to be broke today on Bleeping.
Chick-fil-A discloses data breach after credential stuffing attacks
Critical Palo Alto VPN bug now exploited by Qilin ransomware gang
OpenAI says its AI models hacked Hugging Face during testing
Calculate what you’d save by replacing your MDR.
Privacy by policy or privacy by architecture? See how age checks work when the face never leaves the device.
Overdue a password health-check? Audit your Active Directory for free
Rev5 is ending. See what your FedRAMP 20x transition really requires
Do you have what it takes to challenge DARKROOM? Signup for an exclusive DEFCON CTF!
AI agents can speed up ransomware attacks. See how Acronis helps reduce the risk.
Terms of Use – Privacy Policy – Ethics Statement – Affiliate Disclosure
Read our posting guidelinese to learn what content is prohibited.
