Microsoft 365 Outage: What Your SLA Credit Is Worth and How to File a Claim

Microsoft 365 Outage: What Your SLA Credit Is Worth and How to File a Claim

Need Help Figuring Out the Licensing You Need? Save Up to 20% by Chatting with our Experts!

Get Expert Licensing Help

The Microsoft 365 incident that began on November 12, 2026, has customers asking whether they will get a refund, but the answer is a service credit, not a refund. If Microsoft approves your claim, the credit reduces a future TrustedTech invoice for the affected services only, and TrustedTech files the claim with Microsoft on your behalf. Below is what a credit covers, how much downtime it takes to earn one, and what we need from you to file.


Key Takeaways

  • A Microsoft 365 SLA credit is a reduction on a future TrustedTech invoice, not a cash refund.
  • Credits apply only to the services that were affected, such as Exchange Online or Teams, not to your whole Microsoft 365 subscription.
  • Microsoft’s credit tiers for Exchange Online and Teams are 25% below 99.9% monthly uptime, 50% below 99%, and 100% below 95%, and 99.9% uptime allows roughly 43 minutes of average downtime per user in a 30-day month.
  • TrustedTech files your claim with Microsoft after Microsoft publishes the Post-Incident Review for the November 12, 2026 incident, and your request must come from the domain of your affected tenant.
  • TrustedTech needs your details by December 11, 2026, so we can meet Microsoft’s filing deadline.
  • Microsoft, not TrustedTech, decides eligibility, so neither an amount nor a decision date is guaranteed.

Microsoft, not your partner, decides whether your tenant’s impact qualifies. This post covers what a credit is, why it’s usually modest, and how a claim moves through a Cloud Solution Provider (CSP) like TrustedTech.


Is a Microsoft 365 SLA credit a refund?

A Microsoft 365 SLA credit lowers a future bill. It doesn’t refund a past one.

Microsoft’s Service Level Agreement (SLA) defines a service credit as a percentage of the monthly fees for the affected service, applied after Microsoft approves your claim. A service credit is the contractual remedy for missed uptime. A service credit is not compensation for lost productivity, overtime, or missed deadlines. The SLA states that service credits are your sole and exclusive remedy for performance or availability issues and that they aren’t awarded to compensate for lost revenue, operational costs, or other indirect losses (Microsoft Online Services SLA).

For customers who buy through TrustedTech, an approved credit is applied to a future TrustedTech invoice. Nothing is paid out.


Do SLA credits cover your whole Microsoft 365 subscription?

Credits apply to the affected services, not your whole subscription. If Exchange Online and Teams were down and SharePoint ran normally, the credit is calculated on the fees for Exchange Online and Teams. Your total Microsoft 365 bill isn’t the base. Microsoft’s Partner Center guidance states the same rule: a customer on an Office 365 suite who experienced only a SharePoint outage receives a credit for SharePoint alone, and credits are prorated based on the affected service and the duration of the outage (Microsoft Learn, Partner Center).

For Exchange Online and Teams, Microsoft’s published tiers work like this (from the November 17, 2026 Microsoft Online Services SLA, which matches the example table on Microsoft Learn):

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

Some services, such as Teams Calling Plans, Teams Phone, and Audio Conferencing, add 5% and 10% credits when uptime falls below 99.9% and 99%, respectively, so the SLA for each service you use applies.


How much downtime does it take to earn a credit?

The threshold is higher than most people expect. Microsoft measures uptime in user minutes for each service across the entire calendar month. In a 30-day month, 99.9% allows roughly 43 minutes of average downtime per user. A multi-hour outage that hits only some of your users may not average out to enough to cross the line. Dropping below 99% takes about seven hours per user. Downtime also has a narrow definition. For Exchange Online, it is any period when users are unable to send or receive email with Outlook on the web; for Teams, it is any period when users are unable to conduct instant messaging conversations or initiate online meetings. The SLA excludes performance degradation or latency without actual service unavailability (Microsoft Online Services SLA).

So the realistic best-case scenario for a typical incident is the 25% tier, applied to the monthly fees for the affected services. That’s a real credit, but small next to what an outage costs in staff time. We still think it’s worth filing. Gathering the details is quick, and without a claim there is no credit.


How does a Microsoft 365 SLA claim work through a CSP?

A CSP files the claim with Microsoft for you. Microsoft accepts credit requests only from CSP providers and requires that the customer’s email requesting the credit come from the affected tenant’s domain. This means the process starts with you, and we handle the filing.

  1. You ask TrustedTech to file. Reply to your TrustedTech contact or open a support request.
  2. We wait for the Post-Incident Review. Microsoft publishes the Post-Incident Review (PIR) after closing the incident, and the PIR confirms the official start and end times. We file against Microsoft’s own record so your claim and the incident line up.
  3. You send the details. Collecting them now means we can file as soon as Microsoft publishes the review.
  4. We submit the claim and send you the Microsoft ticket number. We attach Microsoft’s outage incident ID, which appears on the Service health page in the Microsoft 365 admin center (Microsoft Learn).
  5. Microsoft decides. Microsoft says it typically processes claims within 45 days of receiving them (Microsoft Online Services SLA). We keep you updated, and any approved credit is applied to a future TrustedTech invoice.

Here is what we need from you. Send it from your company email address, because Microsoft requires the customer email submitted as evidence to come from your organization’s domain (an email from a personal address isn’t acceptable):

  • Your tenant ID or primary domain (we can look this up if you’re unsure)
  • The Microsoft 365 services your users couldn’t use, such as Outlook/Exchange, Teams, or SharePoint/OneDrive
  • The time windows when users were affected, with start and end times and time zone
  • The number of affected users and their locations
  • What your team did to resolve the issue, plus any support ticket numbers opened with us or Microsoft
  • Screenshots or error messages, if you have them

Please send these by December 11, 2026, to meet Microsoft’s filing deadline. Microsoft’s Partner Center guidance sets the deadline for Microsoft 365 claims at one month from the end of the billing month in which the incident occurred, which, for a November 12, 2026 incident, is December 31, 2026. The SLA gives the same cutoff: Microsoft must receive the claim and all required information by the end of the month after the month in which the incident occurred (Microsoft Online Services SLA).


Frequently Asked Questions

Q. Will we get a refund?

A. No. An approved SLA credit is applied to a future TrustedTech invoice. It reduces what you owe; it isn’t paid back to you.

Q. Does the credit cover our whole Microsoft 365 subscription?

A. No. Credits apply only to the specific services affected, not to your full subscription.

Q. Is a credit guaranteed if we file?

A. No. Microsoft determines eligibility based on the impact on your tenant under its SLA, so we can’t promise an outcome or amount.

Q. Why can’t you file today?

A. Microsoft’s Post-Incident Review confirms the official start and end times. We file after it’s published so the claim matches Microsoft’s record.

Q. Will we get a credit automatically?

A. No. Microsoft’s SLA is claim-based: Microsoft must receive a claim that includes the information it needs to validate it (Microsoft Online Services SLA). For subscriptions bought through TrustedTech, we file that claim for you. We’ll update this page if Microsoft announces a different process.

Q. Outlook was down for hours. Why isn’t the credit bigger?

A. Microsoft measures uptime per service, in user minutes, across the whole calendar month. For Exchange Online, downtime counts only periods when users can’t send or receive email with Outlook on the web. A multi-hour outage affecting part of your organization can leave your monthly uptime above 99.9%, which earns no credit. When uptime falls below a tier, the credit is a percentage of that month’s Exchange Online fees (Microsoft Online Services SLA).

Q. Does a 50% credit mean half our Microsoft 365 invoice?

A. No. Service credits apply only to fees paid for the particular service, service resource or service tier for which a service level wasn’t met, and they can’t exceed the monthly fees for that service. A 50% credit on Exchange Online is half of that month’s Exchange Online fees, not half of your Microsoft 365 invoice (Microsoft Online Services SLA).

Q. How much will the credit be per user?

A. Microsoft calculates the credit as a percentage of the monthly fees for the affected service, so the amount depends on the service, your subscription, your user count, and the tier your tenant reaches. We can’t give a figure until Microsoft reviews the claim.

Q. Does a service degradation qualify?

A. Only if users were actually unable to use the service as the SLA defines it. The SLA excludes performance degradation or latency issues without actual service unavailability, and states that Microsoft outage communications do not confirm missed service levels or credit eligibility (Microsoft Online Services SLA). The Teams service level, for example, counts only periods when users can’t engage in instant messaging or initiate online meetings.

Q. Where do we find the incident ID and our tenant ID?

A. A Microsoft 365 admin with the Service Support admin or Helpdesk admin role can open Health > Service health in the Microsoft 365 admin center and read the incident ID there (Microsoft Learn). Microsoft status posts quoted in community threads on Microsoft Q&A reference incident IDs EX1550543 and MO1550821, so confirm which applies to your tenant. Your tenant ID (GUID) is in the Tenant ID box on the Overview page of the Microsoft Entra admin center (Microsoft Learn). Microsoft Learn says Service health shows history for the past 30 days, so record the details soon. We can also look up your tenant ID for you.

Q. Was this an incident or an advisory?

A. Service health labels each event as one or the other. Microsoft defines an incident as a critical issue in which the service or a major function of it is unavailable, and an advisory as a problem that affects some users while the service is still available (Microsoft Learn). Microsoft’s Partner Center guidance says advisory incidents aren’t typically eligible for SLA credits, so check how service health classifies the event for your tenant.

Q. Should we contact Microsoft support ourselves?

A. Not for subscriptions you bought through TrustedTech. Microsoft’s guidance is that if you bought all your subscriptions through a partner, you contact your partner for support (Microsoft Learn), and Microsoft accepts credit requests only from CSP providers (Partner Center). Reply to your TrustedTech contact or open a support request, and we’ll file the claim.

Q. We already opened a support ticket. Is that enough?

A. No. Microsoft’s Partner Center guidance states that a customer name, tenant identifier, partner ticket number, and ticket creation date and timestamp aren’t sufficient for a claim to be processed. A claim also requires your tenant GUID, the outage incident ID, proof that you encountered the outage and requested the credit, and confirmation of whether the affected subscriptions were purchased through CSP (Partner Center). Your ticket number still belongs in the details you send us.

Q. What if we don’t have screenshots?

A. Send what you have. The SLA requires a detailed description of the incident, the time and duration of the downtime, the affected resource names, the number and locations of affected users, and a description of the errors, and states that claims without the required information are rejected (Microsoft Online Services SLA). Partner Center’s evidence list includes your attempts to resolve the incident, the customer’s request email, and the support ticket details, but it doesn’t include screenshots (Partner Center). Tell us which details are missing, and don’t recreate or backdate records.


The takeaway

Treat an SLA credit as a modest offset, not a recovery, and gather your details now so the claim is ready when Microsoft closes the incident. If your users were affected and you’d like us to file, talk to your TrustedTech account team, and we’ll take it from there.


References

Sources checked November 19, 2026. Microsoft pages can change, so confirm current terms before you file.

Thomas Rosquin, Sr Writer

Thomas Rosquin, Sr Writer

Thomas Rosquin is a content strategist and technology writer at TrustedTech, a top 1% global Microsoft Cloud Solution Provider. With 20 years of experience in research, editorial, and content strategy, he focuses on Microsoft technologies, workplace AI, and IT governance, translating complex licensing and adoption decisions into clear guidance for technology leaders. His work draws on original research, industry analysis, and close collaboration with TrustedTech's Microsoft-certified solutions team.

LinkedIn | Case Studies