Microsoft 365 Outage Disrupts Teams, SharePoint, OneDrive for North American Users
What Happened — On July 23 2026 Microsoft reported a widespread outage across Microsoft 365 services—including Teams, SharePoint, OneDrive, the Admin Center, Power Automate, Copilot Chat and Loop. The incident began at 10:44 AM ET and affected users accessing the platform via certain North‑American network paths, causing degraded functionality and intermittent errors.
Why It Matters for Compliance & Audit Readiness
- Availability is a core SOC 2 Trust Services Criterion; an unplanned service disruption tests the effectiveness of your Business Continuity (BC) and Disaster Recovery (DR) controls.
- Continuous evidence of incident response, traffic‑rerouting decisions, and mitigation timelines is essential to demonstrate due diligence during a SOC 2 audit.
- Mapping this outage to your control framework helps prove that you have documented, tested, and exercised recovery procedures—key audit artifacts for the “Availability” principle.
Who Is Affected — Enterprises and SaaS users relying on Microsoft 365 (tech‑SaaS, finance, healthcare, education, etc.).
Recommended Actions
- Verify that your BC/DR playbooks include cloud‑service‑outage scenarios and that recovery time objectives (RTOs) are still realistic.
- Capture Microsoft’s incident updates, traffic‑reroute logs, and internal mitigation steps as audit evidence for the Availability control.
- Conduct a post‑mortem to map any gaps in monitoring or alerting to your SOC 2 control matrix. Source: BleepingComputer
Technical Notes
- The outage appears tied to a network‑path routing issue; Microsoft is testing mitigation actions and has not disclosed a specific vulnerability.
- Affected services: Teams (chat), SharePoint (error “Something went wrong”), OneDrive (intermittent access), Admin Center (slow/failed loads), Power Automate, Copilot Chat, Loop. Source: BleepingComputer