Claiming a Microsoft 365 SLA credit after an outage: who can claim, what it is worth, and the deadline
For a business on Microsoft 365, the outage that started on 12 November 2026 cost close to a full working day of email. The Service Level Agreement gives paying customers a credit on their bill when uptime falls short, but Microsoft does not apply it on its own. Someone has to file a claim, with evidence, before the deadline. Checked against the SLA version dated 17 November 2026.
A paying business customer can claim a credit when a Microsoft 365 service's uptime for the month falls below 99.9%. Below 99.9% earns 25% of that service's fee for the month, below 99% earns 50%, and below 95% earns 100%. The claim must reach Microsoft by the end of the month after the incident, so the 12–13 November 2026 outage has a deadline of 31 December 2026. The credit comes off a future invoice. It is not paid in cash and does not cover lost business.
What happened on 12–13 November 2026
Microsoft's preliminary post-incident report, as quoted by BleepingComputer, puts the start at 11:20 AM ET on 12 November and the end of customer impact at 11:10 AM ET on 13 November: just under 24 hours. Three things combined. A bug that reached the networking gateway servers in a July update, extra traffic after Teams failed over, and server capacity that was already reduced. Unlike Teams, OneDrive and SharePoint, Exchange Online could not fail over to other infrastructure.
The multi-service notice was MO1550821, covering Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR. The Exchange Online incident was EX1550543. Some reports put the outage at more than 30 hours. Tenants were hit at different times, so no single figure is right for everyone. What counts in a claim is how long your own users could not work, not a number from the news.
As of 18 November 2026 Microsoft had not published the final report. Open both incident IDs in your own tenant's Service health page. The IDs and times shown there are what Microsoft will check your claim against.
Who can claim, and what counts as downtime
This SLA is part of Microsoft's commercial agreements. It covers paid business, enterprise, education and government plans. Home plans such as Personal and Family are not under it.
| Situation | Can you claim? |
|---|---|
| Paid business plan, bought direct or through a partner | Yes, if uptime fell below the threshold |
| Services or tiers provided free of charge | No, the SLA excludes them |
| Trials, and preview or beta features | No |
| Bought under Open, Open Value or Open Value Subscription | Yes, but as extra days of service, not money off fees |
| Licenses reserved but not paid for at the time | No |
Most rejected claims fail on the definition of downtime. The SLA defines it separately for each service, and more narrowly than users experience an outage.
- Exchange Online: users cannot send or receive email with Outlook on the web. If desktop Outlook hung but Outlook on the web worked, that time does not count.
- Microsoft Teams: users cannot hold chat conversations or start online meetings.
- SharePoint Online: users cannot read or write any part of a site collection they have permission to.
The SLA also excludes slowness without actual unavailability, network problems on your side or at your internet provider, tenant misconfiguration, and third-party add-ins. In Service health, an Incident means a service or a major function is unavailable. An Advisory means some users have a problem but the service still works, and Microsoft's partner guidance says advisories are not typically eligible.
One more line in the SLA matters: Microsoft's outage communications are not a confirmation that a service level was missed or that a credit is owed. A Service health post is where a claim starts. The proof that your users were affected has to come from you.
Working out uptime in user minutes
User minutes for the month are the minutes in the month times the total number of users. November has 30 days, so each user contributes 43,200 minutes. Downtime is the length of each incident times the number of users it affected, summed over the month. Exchange Online has no scheduled downtime to deduct.
Take a company with 20 users: 864,000 user minutes in November. Suppose Outlook on the web was unusable for 23 hours 50 minutes (1,430 minutes). The credit depends on how many people were affected.
| Users affected | Downtime user minutes | Uptime | Credit |
|---|---|---|---|
| 20 | 28,600 | 96.69% | 50% |
| 12 | 17,160 | 98.01% | 50% |
| 5 | 7,150 | 99.17% | 25% |
If every user was affected for the whole incident, the thresholds in a 30-day month work out as time: more than 43.2 minutes for 25%, more than 7 hours 12 minutes for 50%, and more than 36 hours before you reach 100%. In a 31-day month they are 44.6 minutes, 7 hours 26 minutes and 37 hours 12 minutes.
So for most tenants that lost a full day, this outage sits in the 50% band. Even the reports of more than 30 hours stay short of 36. If the same service had another incident in the same month, add those minutes too: the SLA counts the whole month.
Exchange Online has more than one service level. Besides Outlook on the web, there are levels for email delivery time and for accepting and sending mail. When one incident breaks several levels of the same service, the SLA lets you claim under only one. We would use Outlook on the web availability, because it is the easiest to evidence from your users' side.
What the credit is calculated on, and why it is usually smaller than expected
The credit is a percentage of the fees you actually paid for the affected service in the month of the incident, not the whole plan. Microsoft's partner guidance gives the example of a customer on an Office 365 suite with only a SharePoint outage: the credit is approved for SharePoint only, prorated by the service and the length of the outage.
- Annual prepaid: the fee that counts is the part applied to that month, about a twelfth of the annual price, not the whole payment.
- Cap: credits for a service in a month never exceed that month's fee for that service.
- Form: it comes off a future invoice. There is no cash refund.
- Sole remedy: the SLA makes credits the only remedy for availability problems, and excludes lost revenue, operating costs and indirect losses.
- No self-help: keep paying invoices in full while a claim is open. The SLA does not let you withhold or offset fees yourself.
Many guides skip the suite question. Business Standard or E3 bundles Exchange, SharePoint, Teams and the Office apps into one price, and the SLA does not say how that price is split between services. Taking 50% of the full per-user price gives you a ceiling, not the amount you will receive. Ask Microsoft or your partner to confirm in writing which fee the credit is calculated on.
Bought direct or through a partner: who files
How you bought Microsoft 365 decides who files the claim and whose deadline applies.
| How you bought | Who files | Where | Deadline |
|---|---|---|---|
| Direct from Microsoft | Your organization's admin | A support request in the Microsoft 365 admin center | End of the month after the incident |
| Through a CSP partner | The partner, not you | A ticket in Partner Center | One month from the end of the billing month of the incident |
Microsoft accepts credit requests only from CSP direct and indirect providers, not from indirect resellers. If the company that sold you the licenses is a reseller, your request travels one more step up the chain.
The partner has to attach an email from you asking for the credit, sent from the affected tenant's domain. A personal address is not accepted, and a customer name, tenant ID and ticket number on their own are not enough.
An approved credit appears on the partner's invoice. Microsoft's page does not say how the partner passes it on to you, so that depends on your contract. Ask when you send the request. If you bought through a partner, email them in the first week of December 2026: they need time to collect claims before their own deadline.
Evidence to save before it leaves Service health
Service health in the admin center shows incidents from the past 30 days. The 12 November incident will drop off the screen around mid-December, before the claim deadline. Save both incident pages as PDFs now.
For incidents with broad impact across many organizations, Microsoft posts a preliminary Post-Incident Report (PIR) in Service health within 48 hours of resolution, and a final one within five business days. Smaller incidents get a closure summary instead. Keep both PIR versions.
The SLA says a claim must include everything Microsoft needs to validate it, and an incomplete claim will be rejected. At minimum:
- A description of the incident and the errors users saw, with screenshots.
- Start time, end time and duration of the downtime, with the time zone stated.
- The affected service and incident ID, such as EX1550543.
- The number of affected users and the offices or branches they were in.
- What you did to try to fix it, your helpdesk ticket numbers, and any Microsoft support request numbers.
Also have ready your tenant ID, a 36-character GUID shown in the admin center's organization profile or on the Microsoft Entra admin center overview, the plan name and license count, and your own uptime figure. Your users' side of the timeline comes from helpdesk tickets, staff notices and the team chat.
Filing the claim when you bought direct
- Sign in to the Microsoft 365 admin center with an admin account. Ordinary users cannot open support requests.
- Go to Support and start a new request. Describe it as an SLA service credit claim and choose to contact support. Menu names in the admin center change from time to time.
- Open one request per service per incident. If Exchange Online and SharePoint Online both fell below the threshold, file two.
- Choose email as the contact method so the whole exchange is in writing. Attach your evidence. If the form will not take attachments, reply to Microsoft's first email with them.
- Note the request number. The SLA says Microsoft will use commercially reasonable efforts to process claims, typically within 45 days. That is a target, not a promise.
- If approved, the credit shows on your invoices under Billing. If rejected, ask for the reason in writing and reply in the same request with the missing evidence or a corrected calculation.
Replace the text in angle brackets with your own details. The last request, to confirm the fee the credit is based on, deals with the suite question the SLA leaves open.
Subject: SLA service credit claim - Exchange Online - incident EX1550543
Tenant ID: <36-character tenant GUID>
Organization: <company name>
Subscription: <plan name>, <number> licenses, <monthly / annual prepaid>
Purchased: <direct from Microsoft / through partner name>
We request a service credit under the Service Level Agreement for
Microsoft Online Services for the Exchange Online incident above.
1. Incident: users could not send or receive email in Outlook on the web.
Errors seen: <error text, screenshots attached>
2. Time and duration: from <date time, time zone> to <date time, time zone>,
<minutes> minutes in total for affected users.
3. Affected users: <number> of <total licensed> users, at <office locations>.
User list attached.
4. Steps taken: <what we tried>, helpdesk tickets <numbers>,
Microsoft support request <number, if any>.
5. Uptime for <month>: (<user minutes> - <downtime user minutes>)
/ <user minutes> x 100 = <result>%
6. Attachments: Service health incident page and post-incident report (PDF),
helpdesk tickets, screenshots, user list.
Please confirm in writing the service fee the credit is calculated on
and the invoice it will be applied to.
Contact: <name, role, email at the tenant domain, phone>Booking the credit in the accounts
Do not book a receivable or income when you file. The outcome depends on Microsoft's review and the amount is not yet known. As a general principle, a contingent asset is not recognized until it is virtually certain. Record the credit when it is approved or appears on an invoice, as a reduction of software subscription expense for that period.
On annual prepaid plans there may be no new invoice until renewal or until you add licenses, so the credit can sit for months. Keep a short register with the request number, the approved amount and the invoice it was applied to, so you can confirm it was actually used.
If a local partner issues your tax invoices, ask whether they will issue a credit note or reduce the next invoice, so input tax matches what you actually paid. Agree the treatment with your auditor.
In the month the credit lands, software cost will come in under budget. Note in the variance report that it is a one-off, not a lasting price cut. Budget variance analysis covers how to explain a variance like this.
Is it worth claiming?
In money terms the credit is usually small. A 20-person company that lost email for a day lost 20 person-days of work, and gets back at most half of one month's Exchange fee. We would still file if you kept the evidence. The claim takes little time once the evidence is in hand, and it gives you three things worth more than the credit.
- A record of the incident that Microsoft has reviewed, useful in a supplier review or a renewal conversation with your partner.
- A process that is ready, so next time IT and finance know what to save and where to send it.
- A real cost figure. Lost user minutes times staff cost per hour tells you how much a fallback plan is worth.
What the SLA does not cover is the larger loss: a day of customer email left unanswered, or a month-end close pushed back. Microsoft 365 Copilot was on the list of affected services, so a team that relies on Copilot in Excel during the close needs a manual fallback, and a local copy of the latest monthly management report, not only the one in SharePoint or OneDrive.
What the SLA and Microsoft's pages leave open
- Suite pricing: the SLA does not say how a Business Standard or E3 price is divided between Exchange, SharePoint and Teams.
- Partner pass-through: the partner guidance does not say when or how a partner must pass an approved credit on to the customer.
- Outage length: reports range from just under 24 hours to more than 30, and the final report had not been published when this was checked.
- Which SLA applies: Microsoft updates the SLA almost every month. The version that governs your subscription is the one in force when it started or last renewed, not always the newest.
Questions about Microsoft 365 SLA credits
Do you get a refund when Microsoft 365 goes down?
Not in cash. A paying business customer gets a credit on a future invoice when the service's uptime for the month falls below 99.9%, and only after filing a claim. Microsoft does not apply it automatically.
What is the deadline for the 12–13 November 2026 outage?
If you bought direct, the claim and all required information must reach Microsoft by 31 December 2026. If you bought through a partner, the partner's deadline is one month from the end of the billing month of the incident, so contact them in early December.
Can I claim on Microsoft 365 Family or Personal?
Not under this SLA. The Service Level Agreement for Microsoft Online Services covers paid commercial plans, and excludes free services, trials and preview features.
Desktop Outlook failed but Outlook on the web worked. Is that downtime?
No. For Exchange Online the SLA defines downtime as users being unable to send or receive email with Outlook on the web. A problem limited to desktop or mobile Outlook does not qualify.
How much credit does a Business Standard customer get?
No more than that month's fee for the affected service, and only for the service that went down. The SLA does not say how a suite price is split between services, so a figure based on the full per-user price is a ceiling. Ask Microsoft or your partner to confirm the fee base in writing.
When should the credit be booked?
Not when you file, because the outcome and amount are not yet known. Book it when it is approved or appears on an invoice, as a reduction of software subscription expense for that period.
Sources
Checked on 18 November 2026 against the Service Level Agreement for Microsoft Online Services (WW) dated 17 November 2026 and the Microsoft Learn pages below. The timeline of the 12–13 November outage comes from news reports citing Microsoft's preliminary report. SLA terms can change every month, so check the version that applies to your agreement before filing.
- Microsoft Licensing: Service Level Agreements (SLA) for Online Services
- Microsoft Learn: Request a credit from Microsoft (Partner Center)
- Microsoft Learn: How to check Microsoft 365 service health
- Microsoft Learn: Service health and continuity (post-incident reports)
- BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage (16 Nov 2026)
- Office Watch: Microsoft 365 went down? How to claim your SLA credit (16 Nov 2026)
