Skip to main content
Back to Guides
Microsoft 365

How to Claim Your Microsoft 365 Outage Credit

Microsoft 365 was down for about a day on 12 and 13 November 2026. Here's how your admin claims the SLA service credit, with the evidence Microsoft asks for, before the 31 December deadline.

By Tim Cakir 4 min read
How to Claim Your Microsoft 365 Outage Credit

Checked 15 November 2026 against Microsoft's Online Services Service Level Agreement (November 2026 edition). Each section names its Microsoft source.

Microsoft 365 went down for about a day on 12 and 13 November. If your people couldn't send or receive email, Microsoft's service level agreement may owe you a credit on your Exchange Online bill. Microsoft doesn't pay it automatically: an admin has to file a claim, with evidence, by 31 December 2026. Here's how, in about 15 minutes.

What happened

From about 16:17 UK time on Thursday 12 November, many Microsoft 365 customers couldn't use Outlook or send and receive email through Exchange Online, with knock-on problems in other Microsoft 365 apps. Microsoft says the problem lasted until about 16:10 on Friday 13 November, roughly 24 hours, and has since confirmed that all affected environments have recovered and the email backlog has been delivered.

Microsoft traced it to a fault left by an earlier network capacity upgrade, which surfaced after a later network change. It says this was a technical issue, not a cyber attack. Its post-incident report sits under the incidents below in your admin center.

Incident What it covers
EX1550543 Exchange Online: Outlook and email send and receive, from 16:17 UK time on 12 November
MO1550821 The wider Microsoft 365 incident, from 18:26 UK time on 12 November, now marked restored

A separate Teams incident (TM1550488) earlier on 12 November hit the Americas only, for about an hour. Teams calls, chat and meetings weren't part of the main outage, so a Teams credit claim for these dates is unlikely to qualify. Exchange Online is where the claim is.

Source: Microsoft's public status updates for incidents EX1550543, MO1550821 and TM1550488.

Are you likely to get anything?

For Exchange Online, Microsoft counts downtime in user minutes: every minute a user couldn't send or receive email in Outlook on the web, added up across your users and the whole month. The credit depends on the resulting monthly uptime.

Monthly uptime Roughly, per user in November Credit
Below 99.9% More than about 43 minutes down 25% of that month's Exchange Online fees
Below 99% More than about 7.2 hours down 50%
Below 95% More than about 36 hours down 100%

If most of your users were locked out for most of the outage, you're likely in the 25% or 50% band. 100% is unlikely, because the outage lasted about 24 hours, not 36. Users who were only slowed down don't count: the SLA excludes degraded performance without actual unavailability, and problems caused by your own configuration, your network or a third party.

Exchange also has service levels for email delivery time and guaranteed delivery, but those are measured across the whole month, so a single day rarely tips them. You can claim only one service level per incident, so the Outlook availability one above is usually the one to pick.

Source: Microsoft Online Services Service Level Agreement, November 2026, Exchange Online section.

Step by step

  1. Save the incident details now. In the Microsoft 365 admin center, go to Health → Service health → Issue history and open EX1550543 and MO1550821. Screenshot or export them, plus the post-incident report once it's posted. Issue history only goes back 30 days, so do this before mid-December.
  2. Check how you buy Microsoft 365. If you pay Microsoft directly, you file the claim yourself. If you buy through a reseller or Cloud Solution Provider (CSP), your partner files it for you in Partner Center, so send them your evidence and ask them to submit it.
  3. Gather the evidence Microsoft asks for. The SLA says claims missing any of these are rejected:
    • A detailed description of the incident (quote the incident IDs)
    • The time and duration of the downtime you saw
    • The affected services, for example Exchange Online
    • The number and locations of affected users
    • A description of the errors users saw, such as screenshots, error messages and help desk tickets
  4. Note your tenant ID. You'll find it in the Microsoft Entra admin center under Entra ID → Overview → Properties. Your partner needs it if you buy through CSP.
  5. File the claim. In the Microsoft 365 admin center, select Help & support (bottom right), then Contact support (the headset icon). Choose phone or email, say it's an SLA service credit claim for EX1550543 and MO1550821, attach your evidence and select Contact me. You need an admin role and at least one subscription bought directly from Microsoft.
  6. Submit by 31 December 2026. Claims are due by the end of the calendar month after the month of the incident. For a November outage, that's 31 December.
  7. Follow up. Microsoft says it typically decides within 45 days. An approved credit comes off a future bill for that service; it isn't paid out as cash.

Sources: Microsoft Online Services Service Level Agreement, November 2026, general terms. Microsoft Learn: "Get support for Microsoft 365 for business", "How to check Microsoft 365 service health", "Request a service credit" (Partner Center) and "Find your Microsoft Entra tenant ID".

Things to know before you file

Service credits are your only remedy under the SLA and are capped at that month's fees for the affected service, so they won't cover lost revenue or staff time. Free, trial and preview services aren't covered. If you buy through Open or Open Value licensing, you get extra service days instead of money off. You also need to be in good standing on your Microsoft agreement.

Microsoft's outage announcements aren't proof that you qualify, so your own evidence carries the claim. If you bought services separately rather than as a suite, each one can be claimed on its own, but only once per service per month. Microsoft 365 Copilot has its own, stricter service level (99.5%, measured on Copilot Chat errors), worth checking if your users rely on it.

Source: Microsoft Online Services Service Level Agreement, November 2026, general terms and Microsoft 365 Copilot section.

Written by

Tim Cakir

Tim Cakir is the founder of AI Operator and creator of The ADOPT Method™. He helps organizations turn AI curiosity into operational results, training leaders and teams to build durable Human + AI ways of working.

View full profile →

Want a hand with your claim?

We help teams get real value out of Microsoft 365 and Copilot. If you'd like us to look over your claim before you send it, get in touch.