Saturday, 21 November 2026UK SME IntelligenceGet the weekly brief
Operations

Microsoft 365 outage compensation: what UK businesses can claim, and how

Business customers can claim a service credit, not cash, when Microsoft 365 uptime falls below 99.9%. The tiers, a worked example and the 31 December deadline.

Illustration of a balance scale with a small stack of coins, one orange, on the raised pan and a heavy navy cloud on the lower pan

If your business pays for Microsoft 365, the compensation on offer for this week’s outage is a service credit: a percentage off next month’s bill for the service that went down. It is not cash, it is not automatic, and it will not cover lost sales. For an outage that began on 12 November, the claim has to reach Microsoft by 31 December 2026.

That sounds thin, and it is. But the credit can be half or more of the monthly fee for the affected service, and filing is an admin task, not a court case. Below: who actually receives the credit if you buy through an IT provider, the thresholds and when this outage could cross each one, a realistic estimate of what it is worth, and the evidence to gather while the outage is still running.

Bought through an IT provider? Ask who gets the credit

Many small firms buy Microsoft 365 through a reseller, often their IT provider, rather than from Microsoft. Up to and including the September 2024 edition, Microsoft’s SLA said: “If you purchased a Service from a reseller, you will receive a service credit directly from your reseller and the reseller will receive a Service Credit directly from us” (September 2024 SLA). That sentence is gone from the October 2024 edition onwards (October 2024 SLA), and the current SLA does not replace it.

So the SLA no longer says that, when Microsoft credits your reseller, you get a credit from them. Whether it does now depends on your contract with them. Ask before they file, and get the answer in writing.

Microsoft promises 99.9% uptime, and pays credits below it

Microsoft’s Service Level Agreement covers Exchange Online, Teams, SharePoint Online, OneDrive for work or school and Microsoft 365 Apps. Each promises 99.9% uptime per calendar month, and pays credits on a sliding scale when it misses (Microsoft SLA, October 2026):

Monthly uptime Service credit
Below 99.9% 25%
Below 99% 50%
Below 95% 100%

Uptime is counted in user-minutes: the minutes in the month multiplied by your users, less the minutes each user was down. In a 30-day month like November, with everyone affected, that means:

  • more than 43.2 minutes (43 minutes 12 seconds) of downtime takes you below 99.9% (25% credit)
  • more than 7 hours 12 minutes takes you below 99% (50%)
  • more than 36 hours takes you below 95% (100%)

Two details decide whether your downtime counts. First, each service has its own definition. For Exchange Online, downtime is “any period of time when users are unable to send or receive email with Outlook Web Access”, so a period when desktop Outlook failed but Outlook on the web worked may not count. Second, slowness is not downtime: the SLA excludes “performance degradation or latency issues without actual service unavailability”, except for services that have a performance-based service level.

Exchange Online has two that matter for delayed mail. Its email delivery time level takes the fastest 95% of your messages over the month and pays 25% if they average more than 1 minute, 50% over 4 minutes and 100% over 10 minutes. Because that measure ignores the slowest 5% of a month’s mail, a delay lasting about a working day may not move it at all; a longer one might. Its email ingress and egress availability level covers times Microsoft “is not able to accept or send email messages due to a problem within the M365 boundary”, and counts messages “delayed more than (10) minutes” during the problem against Microsoft, with the same 25%, 50% and 100% tiers below 99.9%, 99% and 95%.

You can claim under only one service level per service for the same incident, so pick the one that fits what happened. Mail that Microsoft accepted and then held in its own queues counts under email delivery time, which measures from “when a mail enters the Microsoft 365 boundary to when the mail is delivered”. The ingress and egress level fits mail that Microsoft turned away, so senders had to keep retrying. If you cannot tell which happened, ask Microsoft or your reseller to check your message trace and claim under whichever pays most.

When this outage could cross each threshold

Microsoft dates the start of the Exchange Online incident to 4.17pm on Thursday 12 November (Downdetector, citing Microsoft). For a business in which every user could not send or receive on Outlook on the web from that moment, in a month with no other downtime, the clock runs like this:

Threshold crossed Uptime falls below Time (UK) Credit tier
43.2 minutes down 99.9% Thu 12 Nov, just after 5pm 25%
7 hours 12 minutes down 99% Thu 12 Nov, 11.29pm 50%
36 hours down 95% Sat 14 Nov, 4.17am, if still down 100%

By midday on Friday, Microsoft’s status page still listed the outage as “Service degradation” (Microsoft), about 19 hours 43 minutes after the start time. Two caveats keep this from being a promise. Microsoft is restoring service region by region, so many users’ real downtime will be shorter than the clock. And it matters whether Microsoft classes the event as an incident or an advisory: Partner Center notes that “advisory incidents aren’t typically eligible for SLA credits” (Microsoft Learn). Check the label against your tenant in Service health.

What that is worth in pounds

Microsoft 365 service credit tiers, 30-day month, all users affected DOWNTIME IN THE MONTH CEILING ON THE CREDIT, 10 USERS PAYING £108 A MONTH Up to 43.2 min 43.2 min to 7.2 h 7.2 h to 36 h Over 36 h 0% 25% 50% 100% £0 up to £27 up to £54 up to £108
Credit tiers from Microsoft's Online Services SLA (October 2026), worked for a 30-day month in which every user is affected. The £ figures are upper limits for a firm paying £108 a month: Microsoft applies the credit only to the fee for the service that failed.

Take a 10-person firm paying £108 a month for Microsoft 365, excluding VAT. If all 10 staff could not use email on the web for more than 7 hours 12 minutes in November, the firm is in the 50% tier. If their real downtime runs past 36 hours, it reaches 100%.

The catch is what the percentage applies to. The SLA says credits “apply only to fees paid for the particular Service” that missed its target, and Microsoft’s own guidance for resellers is plainer still: if a customer “has an Office 365 suite but only experienced a SharePoint outage, the SLA credit is approved only for SharePoint and not the customer’s entire plan” (Microsoft Learn). Microsoft does not publish how it splits a Business Standard fee between email, Teams and the rest. So £54 is the most this firm could get at the 50% tier, not what it will get.

For a realistic figure, use the price of email on its own as a stand-in for the email share of the fee. Microsoft lists Exchange Online (Plan 1) at £3.10 per user per month, paid yearly, excluding VAT (Microsoft). On that basis the email share of this firm’s bill is about £31 a month, so a 50% credit would be worth up to about £15.50, and a 100% credit up to about £31. That is our estimate, not Microsoft’s method: Microsoft does not say how it values one service inside a suite. It does show that the claim is worth filing mainly as a record.

If only five of the ten staff were affected, the shortfall halves: 8 hours of downtime for five people leaves uptime at 99.44%, which is only the 25% tier.

How to claim before 31 December

Credits are not paid automatically. The SLA says Microsoft’s outage messages are “not a confirmation of missed Service Levels or Service Credits eligibility”.

Do one thing today, while the outage is still running: open a support ticket. Partner Center’s checklist for credit claims asks for “the support ticket number and details of customer contact regarding resolving service impact” and “descriptions of your attempts to resolve the incident at the time of occurrence” (Microsoft Learn). A ticket raised now, and a note of what you tried, are evidence you cannot create later. If admin centre pages will not load, phone Microsoft support instead. If you buy through a reseller, ask them to raise it.

What you do next depends on who you pay.

If you pay Microsoft directly, your Microsoft 365 administrator files the claim with Microsoft’s customer support. In the admin centre, select Help & support, describe the problem, then select the Contact Support (headset) icon and choose phone or email (Microsoft Learn). Microsoft notes that if you “bought all your subscriptions through a partner”, you contact the partner instead. The SLA says the claim must include (Microsoft SLA):

  1. a detailed description of the incident
  2. the time and duration of the downtime
  3. the affected resource names, such as the services and mailboxes hit
  4. the number and location of affected users
  5. a description of the errors they saw

Also quote Microsoft’s incident IDs: for this outage, EX1550543 for Exchange Online and MO1550821 for the wider Microsoft 365 incident (Microsoft 365 Status, update). Check them against Service health in your admin centre.

“Failure to provide the required information will result in claims being rejected.” Microsoft says it typically decides within 45 days, and an approved credit is set against your fees.

If you pay a reseller (a Microsoft partner, often your IT provider), you claim through them (Microsoft Learn):

  • Microsoft accepts credit requests only from Cloud Solution Provider direct-bill partners and indirect providers (distributors), not from indirect resellers. If your IT firm buys through a distributor, the claim goes via that distributor.
  • They need your tenant ID, the outage ID and an email from your own business domain asking for the credit.
  • Microsoft gives partners one month from the end of the billing month to file, so your reseller needs your request well before that.
  • Ask whether any credit will be passed on to you (see above).

Send them something like this today:

Please submit an SLA credit claim to Microsoft on our behalf for the Microsoft 365 outage that began on 12 November 2026 (incident IDs EX1550543 and MO1550821; please confirm them in Service health). Our tenant ID is [ID]. [Number] users at [location] could not send or receive email, including on Outlook on the web, from [time] on 12 November to [time] on [date]. Errors seen: [errors]. Support ticket raised during the outage: [number]. What we tried: [steps]. Please confirm the claim reference and whether any credit will be passed to us.

Either way, Microsoft must receive the claim and all the required information by 31 December 2026, so if you buy through a reseller, get your request to them well before then. The SLA says Microsoft must receive claims “by the end of the Applicable Period following the month in which the Incident occurred”, and gives the example that an incident on 15 February must be claimed by 31 March.

What you cannot claim

The SLA is explicit that service credits are “your sole and exclusive remedy” and “will not be awarded to compensate for any other forms of loss, including but not limited to lost revenue, operational costs, or any indirect losses”. The business contract underneath, the Microsoft Customer Agreement, goes further:

  • it excludes “loss of revenue, profits, or anticipated savings” and “interruption of business”
  • it caps Microsoft’s liability for each subscription product at the fees you paid for that product in the 12 months before the incident
  • for UK customers, the contracting company is Microsoft Ireland Operations Limited, the agreement is governed by Irish law, and claims against Microsoft in Europe go to the Irish courts

For a small firm, a court claim for lost profits is not realistic. If you bought through a UK reseller, its own contract and liability terms apply between you and them, so read those too.

Personal plans are different. Microsoft 365 Personal and Family and Outlook.com have no uptime guarantee: Microsoft’s UK consumer terms say they “are not offered with a guaranteed level of quality of service”. The same terms say consumers keep their legal right to have the service provided “using reasonable care and skill” (Microsoft Services Agreement). A sole trader who uses a personal plan mainly for business is unlikely to count as a consumer, because the law defines a consumer as someone acting wholly or mainly outside their business (Consumer Rights Act 2015, section 2).

Check your insurance, then keep records

Whether your insurance covers an outage at a supplier such as Microsoft depends on the policy wording. Ring your broker and ask three specific questions: does the policy include business interruption cover that does not need physical damage; does it extend to dependent or contingent business interruption at an IT or cloud supplier; and how long is the waiting period before cover starts? Do not assume either way until you have the answers.

Whatever you claim, the evidence is the same, so start a log now:

  • when each person lost and regained email (UK time)
  • screenshots of Service health and Microsoft’s status page
  • error messages and bounce notices
  • missed orders, bookings and deadlines, and staff hours lost

Microsoft also posts a preliminary post-incident review to Service health in your admin centre for a broad incident like this within 48 hours of it being fixed, and a final one within five business days (Microsoft Learn). Save both: the start and end times in them support your claim.

For the live position, see our Microsoft 365 outage live status page. For what to do while email is down, see the first hour and the first day.

Frequently asked questions

Can I get compensation from Microsoft for the outage?
If you pay for a Microsoft 365 business plan, you can claim a service credit: 25%, 50% or 100% off the fee for the affected service for that month, depending on how far uptime fell below 99.9%. It comes off a future bill, not as cash, and it is the only remedy Microsoft's terms give you for downtime.
What is the deadline to claim for the November 2026 Microsoft outage?
Microsoft's SLA says claims for Microsoft 365 must reach it by the end of the month after the incident, so 31 December 2026 for this outage. If you buy through a reseller, ask now: Microsoft gives resellers one month from the end of the billing month to file, and they need your details first.
Are Microsoft 365 service credits automatic?
No. Your administrator, or your reseller if you buy through one, has to file a claim with evidence: what happened, when, for how long, how many users were affected and where, and the errors they saw.
Can I claim for lost sales or staff time?
Not under Microsoft's terms. The SLA says service credits are your sole and exclusive remedy and will not compensate for lost revenue, operating costs or indirect losses. Microsoft's business agreement for UK customers also excludes lost profits and is governed by Irish law.
Do Microsoft 365 Personal and Family subscribers get anything?
There is no uptime guarantee on personal plans. Microsoft's UK consumer terms say they are not offered with a guaranteed level of service, but also that consumers keep their legal right to have the service provided with reasonable care and skill.

Sources & further reading

SME Brief uses sources to support factual claims and help readers go deeper.

The Weekly Brief

One email. The week's UK SME signal, no noise.

Our demand data, the tools, the stories that matter, and one thing worth doing this week.

Free. Unsubscribe anytime. We don't share your address.