Skip to main content
Emerging ThreatsData Breaches

Microsoft 365 Outage Disrupts Teams, SharePoint Services

Busy office with people working on laptops, some looking frustrated, amidst empty computer screens and papers.

At 11:11 a.m. ET on July 23, Downdetector recorded 2,403 reports — a surge from its normal baseline of 29 — as Microsoft Teams and multiple Microsoft 365 services experienced an ongoing outage affecting access for many users.

Downdetector spike on July 23

Downdetector's timestamped count captured a sudden and pronounced increase in user reports tied to Microsoft services. The 2,403 reports logged at 11:11 a.m. ET on July 23 stood in stark contrast to the platform’s typical baseline of 29 reports, signaling an incident that pushed both end users and administrators to seek status information and workarounds.

Services affected: SharePoint, Excel, Teams and the Microsoft 365 Admin Center

According to the reporting compiled during the outage, SharePoint accounted for the majority of complaints, making up 78% of the reports tracked by Downdetector. Excel represented 11% of complaints and the Microsoft 365 Admin Center represented 6%. Microsoft Teams and other Microsoft 365 services were also reported as affected, with users reporting problems accessing those services.

Microsoft response: incident MO1437424

Microsoft acknowledged the disruption and said it was investigating. In an official message quoted in the reporting, Microsoft stated: “We’re investigating reports of issues with Microsoft 365 services,” and directed administrators to incident MO1437424 in the Microsoft 365 admin center for additional information and future updates. The company’s referral to a single incident record creates a central point for status updates and administrative guidance as the situation develops.

Security telemetry cited: Picus whitepaper statistic

The reporting included a referenced statistic from a Picus whitepaper noting that security teams log 54% of successful attacks and alert on just 14%, with the remainder moving through an environment unseen. The whitepaper is presented as a resource that “shows how breach and attack simulation tests your SIEM and EDR rules so threats stop slipping by detection.” These figures appear alongside the outage coverage as a reminder of how service disruptions and security visibility concerns can intersect for organizations that depend on cloud productivity platforms.

What this means for administrators, security teams, and end users

  • Administrators: Microsoft directed administrators to incident MO1437424 in the Microsoft 365 admin center for updates and additional information. Administrators monitoring service status and user impact will rely on that incident record as the authoritative source for remediation steps and timelines provided by Microsoft.
  • Security teams: The report’s inclusion of the Picus whitepaper statistic underscores a broader telemetry concern: organizations may be tracking service problems at the same time they must maintain visibility into successful attacks. The whitepaper advertised in the report frames breach-and-attack simulation as a tool for testing SIEM and EDR rules, material that security teams may consider while assessing detection gaps during platform outages.
  • End users: Individuals attempting to access SharePoint, Excel, Teams or the Microsoft 365 Admin Center were among those reporting problems. The Downdetector data indicates the majority of impacted reports were related to SharePoint, suggesting collaborative file and site access was a principal pain point at the time of the spike.

Microsoft’s acknowledgement and the referral to incident MO1437424 make clear that the company is treating the event as an active incident. The immediate facts recorded by Downdetector — 2,403 reports at 11:11 a.m. ET and a complaint distribution heavily weighted toward SharePoint — provide a snapshot of the outage’s shape, while the Picus whitepaper statistic included in the reporting adds a security-visibility frame to the operational disruption. How long Microsoft’s investigation will take and what the underlying root cause proves to be are not yet reported; the company’s incident record is the stated channel for those answers as the situation develops.

Original reporting: https://www.bleepingcomputer.com/news/microsoft/microsoft-365-outage-affects-teams-sharepoint-and-other-services/