Last updated: November 15, 2026
To claim a Microsoft 365 SLA credit, your admin must file a claim with Microsoft support (or with your CSP partner, if you buy through one) by the end of the calendar month after the month of the outage. Include your tenant ID, the incident ID from the Service Health dashboard, the affected service, the number of users affected and how long they were affected. If the service fell below 99.9% monthly uptime, Microsoft credits 25% of that service’s monthly fees, rising to 50% below 99% and 100% below 95%. Credits come off future bills; they are never cash refunds.
This guide was written after the Microsoft 365 outage that began on November 12, 2026, when Exchange Online servers failed health checks and Outlook, Teams and Copilot went down for businesses worldwide for well over a day. Microsoft tracked it under incident IDs EX1550543 (Exchange Online) and MO1550821 (Microsoft 365). For an incident in November 2026, a direct claim must reach Microsoft by December 31, 2026.
Microsoft 365 is covered by the Service Level Agreement for Microsoft Online Services, a document Microsoft updates regularly and publishes on its licensing site. The August 2026 edition still promises 99.9% monthly uptime for the core workloads: Exchange Online, Microsoft Teams chat and meetings, SharePoint Online, OneDrive and the Microsoft 365 Apps services. Teams Phone, Calling Plans and Audio Conferencing carry a higher 99.99% target with an extra 10% credit tier.
| Monthly uptime for the service | Service credit |
|---|---|
| Below 99.9% | 25% of that service’s monthly fees |
| Below 99% | 50% |
| Below 95% | 100% |
99.9% sounds strict, but it allows about 43 minutes of downtime in a 30-day month. 99% allows about 7 hours 18 minutes, and 95% allows about 36 hours. Uptime is measured in user minutes, so an outage that hit only some of your users counts for less than one that hit everyone.
Microsoft calculates monthly uptime as (user minutes minus downtime) divided by user minutes. User minutes are the total minutes in the month multiplied by the number of licensed users of that service. Downtime is the minutes during which affected users could not use the service as the SLA defines it.
Here is a simple example. A company has 100 Exchange Online users in a 30-day month, which is 4,320,000 user minutes. If all 100 users lost email for 20 hours, that is 120,000 minutes of downtime, so monthly uptime is about 97.2%. That is below 99% but above 95%, so the credit would be 50% of the month’s Exchange Online fees. If only half the users were affected, uptime would be about 98.6%, still below 99%.
Two things reduce what you can claim. First, the credit applies only to the fees for the service that missed its target. If you pay for a Microsoft 365 suite, the credit is based on the share of the bundle that covers the affected service, not your whole bill. Second, the SLA excludes some causes, including problems outside Microsoft’s reasonable control, your own network or ISP failures, and features in preview.
Note when each service stopped working for your users, how many users were affected and what they could not do. Screenshots of error messages and the Service Health dashboard help. Open a support ticket with Microsoft during the outage if you can, because a ticket number makes the later claim stronger.
In the Microsoft 365 admin center, go to Health, then Service health, and open the incident history. Copy the incident ID (for example EX1550543) and the start and end times Microsoft recorded. Microsoft usually publishes a post-incident report within a few days.
Your tenant ID is on the Microsoft Entra admin center overview page. From your invoice, work out what you pay per month for the affected service or the plan that includes it.
If you buy directly from Microsoft, open a billing support request in the admin center and say you are requesting an SLA service credit. If you buy through a Cloud Solution Provider (CSP) partner, file with the partner instead: Microsoft’s partner rules require partners to submit outage claims within one month of the end of the billing month and to supply the tenant ID, the outage ID and evidence that the customer requested the credit, usually an email from your company domain.
Microsoft says it uses commercially reasonable efforts to process claims within 45 days. Approved credits are applied to future invoices for that service. Keep paying your invoices in the meantime; withholding payment does not speed anything up.
SLA credits are Microsoft’s only contractual remedy for missed uptime, and they are capped at the fees you paid for the affected service that month. They do not cover lost sales, overtime, missed deadlines or the cost of workarounds. For a typical small business, a 25% or 50% credit on one month of email fees is worth tens or hundreds of dollars, not the cost of a lost day.
That is why the real protection is resilience, not compensation. An email continuity service keeps mail flowing when Exchange Online is down, a Microsoft 365 backup keeps a copy of your data outside Microsoft, and a written plan for what to do when Microsoft 365 is down cuts the chaos. If you need help with any of it, see our list of Microsoft 365 consultants.
No. Credits are not automatic. A Service Health post or a public statement from Microsoft is not a claim. Your admin, or your CSP partner, has to file a claim with the required details before the deadline.
For a direct claim, Microsoft must receive it by the end of the calendar month after the month the incident occurred. For the November 2026 outage, that means by December 31, 2026. CSP partners work to a deadline of one month after the end of the billing month, so tell your partner early.
It depends on how long your users were affected and how many of them. If every user lost Exchange Online for more than about 7 hours 18 minutes in a 30-day month, uptime falls below 99%, which means a 50% credit on Exchange Online fees for that month. Below 95%, about 36 hours, the credit is 100%.
No. Microsoft applies approved service credits to future fees for the affected service. They are not paid out as cash and cannot exceed that month’s fees for the service.
For larger tenants, usually yes, because the credit can be significant and claims create a record of Microsoft’s reliability for future negotiations. For very small businesses, the credit may be small, but filing takes less than an hour if you have the incident ID ready.
Related reading: Best Microsoft Teams Alternatives, Best Outlook Alternatives For Business Email, Best Uptime Monitoring Tools.
Microsoft 365 SLA credits are real money, but only if someone files a claim on time with the right details. Get the incident ID, count affected users and minutes, and file before the end of the following month, or ask your CSP partner to do it straight away. Then spend more time on resilience than on the claim, because no credit will pay for a lost day of business.