Advisory Microsoft 365 outage (Nov 12–13): service is restored. SLA credit claims are due by Dec 31. Where it stands and what to do

SecurityPatched · check your servers

SharePoint “ToolShell” attacks, July 2025

Attackers exploited a critical flaw in on-premises SharePoint Server to take over servers before a patch was available. SharePoint Online in Microsoft 365 wasn’t affected.

Updated

Where it stands

Microsoft released security updates for all affected versions. Servers that were exposed before patching may still need cleanup.

What happened

  • The flaw, CVE-2025-53770 (CVSS 9.8), let attackers run code on on-premises SharePoint Server without signing in. Microsoft released fixes for SharePoint Server 2016, 2019 and Subscription Edition; older versions such as 2010 and 2013 are affected too and no longer get updates.
  • Microsoft confirmed active attacks in July 2025 and released emergency updates.
  • Microsoft’s guidance: install the update for your version, turn on AMSI integration, and rotate the server’s ASP.NET machine keys, because stolen keys can let attackers back in after patching.

Internet-facing servers on your own premises need an owner, a patch schedule and a plan for emergency updates. If nobody can say who patches yours, that’s the risk.

More field notes

  1. Outage

    Microsoft 365 outage, November 12–13, 2026

    A software defect in the networking gateway in front of many Microsoft 365 services left most users unable to reach their mailboxes for about a day. Service is restored. If your organization was affected, you may be owed an SLA credit, and the claim deadline is close.

  2. Outage

    Microsoft 365 outage in North America, January 22, 2026

    Outlook, Teams and other Microsoft 365 services failed for users across North America for most of a working day, and the Microsoft 365 admin center went down with them.

  3. Outage

    Azure Front Door outage, October 29, 2025

    A configuration problem in Azure Front Door, the global network edge in front of many Microsoft and customer services, caused failures worldwide for about eight and a half hours.

Facts come from the sources listed with each note and are current as of the date shown. This isn’t legal or contract advice. Check your own agreements and Microsoft’s official records before you act.

You don’t have to know the answer before you call.

Tell us what you’re trying to solve. We’ll help you make sense of it and point you in the right direction.

Let's Get Started