Rewterz

Fortinet2Shell Flaw Enables RCE Attacks Through Malicious Websites

November 12, 2026

Microsoft 365 Infrastructure Failure Causes Widespread Service Disruptions

Severity

High

Analysis Summary

Microsoft 365 experienced a major global outage on November 12–13, 2026, disrupting access to several cloud services, including Outlook, Teams, SharePoint, Copilot, and Microsoft Defender XDR. Microsoft confirmed that connectivity issues could affect users across all regions, although not every customer was impacted. The disruption is being tracked under incident MO1550821, while Exchange Online mailbox connectivity issues are separately monitored under EX1550543.

Initial investigations indicated that the outage resulted from infrastructure capacity problems rather than increased user traffic. Several servers unexpectedly became unavailable, forcing the remaining infrastructure to handle additional connections and creating further service instability. Microsoft engineers began rerouting traffic across global infrastructure to reduce pressure on affected systems.

Microsoft identified failures in automated server health checks as a key factor complicating recovery. These checks determine whether servers are available to process requests. Engineers tested alternative health-check methods, restarted affected servers, and deployed configuration adjustments to restore capacity. However, some recovered servers became unresponsive again when traffic resumed, making restoration more difficult.

To address the ongoing disruption, Microsoft paused certain deployments, explored configuration rollbacks, and shifted traffic to alternative routes. Additional recovery measures included traffic optimization, throttling, protocol adjustments, and failover routing. Engineers also expanded controlled testing to improve traffic monitoring and infrastructure stability.

The outage raised concerns for security teams because reported Microsoft Defender XDR disruptions could affect access to security alerts and investigation workflows. However, Microsoft has not confirmed that endpoint protection or background threat detection services stopped functioning.

Microsoft stated that it was not aware of any malicious activity causing the disruption. Recovery efforts remained ongoing, with no confirmed timeline for full restoration. The company plans to publish a post-incident report explaining the root cause and outlining additional safeguards after the outage is mitigated.

Impact

  • Operational Disruption

Remediation

  • Monitor Microsoft 365 service health updates through the admin center and public status page.
  • Track incidents MO1550821 and EX1550543 for recovery progress and service-specific impact.
  • Implement alternative communication channels to maintain business operations during service disruptions.
  • Maintain backup procedures for critical business applications and cloud-based services.
  • Monitor Microsoft Defender XDR availability and use alternative security monitoring capabilities where necessary.
  • Verify service stability before resuming critical business workflows.
  • Review Microsoft post-incident findings and implement recommended configuration and resilience improvements.

Reading this advisory was a good start.

Make it a habit.

Rewterz publishes threat advisories ahead of mainstream cybersecurity media, informed by an AI-Native Autonomous SOC that sees regional threat actor activity in real time. Subscribe to receive each new advisory as it publishes, plus a monthly Middle East threat landscape brief drawn from our own SOC telemetry. For teams evaluating their detection coverage, a 30-minute consultation with a senior analyst is also available, at your pace, when you're ready.