Microsoft 365 users suffered a cascading global outage, with infrastructure capacity problems leaving servers unexpectedly unavailable. The incident details and remediation efforts are reported by 3 outlets: Bleeping Computer, rewterz, and SecurityOnline.

What do we know about the Microsoft 365 outage incident?

According to Bleeping Computer, the disruption began at 11:20 AM ET. The issue was resolved around 11:10 AM ET on November 13 after Microsoft deployed a fix. Microsoft states a months-old bug introduced in July in the Microsoft 365 networking gateway update caused the global outage. This defect combined with a Teams failover that redirected traffic to Exchange Online. It also compounded a pre-existing 14% capacity shortfall. As a result, more than 80% of gateway servers were left unresponsive for nearly 24 hours. Production-like load tests using different traffic mixes did not detect the defect. Safeguards designed to contain cross-region failure and traffic redirection were insufficient before capacity boosts and enhanced monitoring were put in place.

According to rewterz, the disruption in 2026 disrupted multiple applications and raised security-operations concerns regarding Defender XDR disruptions. Microsoft attributes the incident to infrastructure capacity problems occurring after several servers unexpectedly became unavailable. Furthermore, automated health checks failed to reflect availability, complicating the recovery process for responders. Engineers rerouted traffic across the global fabric to address the outages. They paused certain deployments, implemented configuration rollbacks, applied traffic throttling, and managed failover routing. The engineering teams expanded windowed testing and monitoring to restore capacity across the affected network. Microsoft has not confirmed malicious activity regarding this event. A post-incident report is planned detailing the root cause and resilience-improvement steps.

Disrupted Application
Outlook
Teams
SharePoint
Copilot
Defender XDR

The table shows five distinct applications directly affected by the availability failure, including SharePoint, a platform previously detailed in Microsoft SharePoint CVE-2026-45659 (CVSS 8.8) RCE.

What do several outlets confirm, and what does only one report?

According to Bleeping Computer and rewterz, the incident involved cascading problems that forced immediate traffic rerouting across the global fabric. The Microsoft infrastructure failure required engineers to execute configuration rollbacks, failover routing, and capacity boosts to restore server availability. Engineers expanded windowed testing and monitoring while pausing certain deployments to mitigate the disruption.

According to SecurityOnline, direct financial remedies are available for the outage. Microsoft 365 SLA credits are available after a global disruption and are applied to the affected applications. The credits apply to the affected applications and exclude the entire bundle. Analysts note that prolonged outages trigger service-credit tiers depending on contract terms. To claim this compensation, direct customers file via the Microsoft 365 Admin Center with comprehensive outage documentation. This required documentation includes workloads, timestamps, affected user counts, and error logs. Cloud Solution Providers coordinate through their resellers using tenant IDs, incident IDs, and proof of impact. There is a strict filing window post the affected billing month. Once approved, the credit appears on the reseller's next invoice.

What should defenders check after the Microsoft 365 outage incident?

Review automated health checks to verify they correctly reflect server availability and do not complicate recovery. Monitor traffic throttling and failover routing configurations used during capacity expansion efforts. Track recovery progress and planned root cause details under identifiers MO1550821 and EX1550543. Compile comprehensive outage documentation containing workloads, timestamps, affected user counts, and error logs. File SLA credit claims via the Microsoft 365 Admin Center within the strict one-month filing window post the affected billing month.

Organizations managing this outage recovery can deploy the JINX and BUGSY products to document affected workloads, and access the dark web monitoring solution to detect external threats targeting systems during the capacity shortfall.