Advisory Microsoft 365 outage (Nov 12–13): service is restored. SLA credit claims are due by Dec 31.

OutageResolved · final report due Nov 20

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.

Updated

Where it stands

Microsoft says customers stopped seeing active impact at 4:10 PM UTC on November 13. It closed both incidents (EX1550543 and MO1550821) on November 14 after a period of monitoring. Its preliminary Post Incident Report, dated November 15, puts the cause down to a software defect, not an attack. The final report, with Microsoft’s full list of repair items, is due November 20, 2026. Microsoft has already reverted the defective code, added capacity, added monitoring for traffic redirection and connection handling, and put guardrails on how traffic is spread so a failure can’t cascade the same way.

What happened

  • When: Thursday, November 12, 2026, 4:20 PM UTC (11:20 AM Eastern) to Friday, November 13, 4:10 PM UTC (11:10 AM Eastern).
  • Who was affected: most Exchange Online users couldn’t open their mailboxes in Outlook or other mail clients, and email was delayed. Parts of Copilot, Teams, SharePoint, OneDrive, Defender and Purview that rely on Exchange Online were affected too.
  • Why: a fix built for Microsoft 365’s networking gateway servers, rolled out from July 2026, contained a latent defect that made servers lock up under heavy load. About fifteen hours before the outage, Teams traffic failed over onto the same gateway, and nearly 14% of the gateway’s servers were already out of service because of an unrelated issue.
  • How it spread: as servers stopped responding, traffic moved to the remaining ones, which then failed as well. At the worst point more than 80% of the gateway servers were unresponsive, and the boundaries between regions didn’t contain it.
  • Why recovery took a day: restored servers were immediately overwhelmed by waiting traffic. Microsoft fixed it by reverting the code to its previous state and restarting servers in large groups.

What to do now

  1. 1

    Check whether you qualify. Paid business, education and government plans are covered; consumer plans aren’t. Credits apply to incidents, not advisories, and only to the service that was affected.

  2. 2

    Collect the evidence now: the incident details for EX1550543 and MO1550821 from Health → Service health in the Microsoft 365 admin center, your tenant ID, when problems started and ended for your users, how many people and which locations were affected, error messages, and helpdesk tickets.

  3. 3

    If you buy directly from Microsoft, an admin files the claim as a support request in the Microsoft 365 admin center, quoting the incident IDs and your tenant ID.

  4. 4

    If you buy through a partner, reseller or MSP, they file it for you. Ask them in writing from an email address on your company’s domain, and ask for their deadline, which will be earlier than Microsoft’s.

  5. 5

    Expect a credit on a future invoice, not a refund. Microsoft aims to decide within 45 days.

When email went down, did your team know how to reach customers and each other, and who made that call? A day-long outage is the right moment to write that down, check what your contracts and SLA actually promise, and decide whether any critical process depends on a single provider.

More field notes

  1. 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.

  2. 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.

  3. Security

    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.

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