Starting November 12, many Microsoft 365 users couldn't reach their mailboxes, and features that depend on Exchange Online failed along with them. Microsoft posted the outage to Service health in the Microsoft 365 admin center under incident IDs that include EX1550543 (Exchange Online) and MO1550821 (Microsoft 365). Check which IDs appear in your own tenant, because those are the ones a claim should cite.
The Service Level Agreement for Microsoft Online Services works service by service. For Exchange Online, Microsoft counts downtime as any period when users can't send or receive email with Outlook on the web.
Uptime is measured in user-minutes across the month. An hour of downtime for every user in your tenant counts for far more than an hour for a handful of people. If Exchange Online uptime falls below 99.9%, the SLA sets the credit at 25% of that service's monthly fee. Below 99% it's 50%, and below 95% it's 100%.
Three limits are worth knowing before you file:
Microsoft decides the outcome after it reviews each claim, so nobody can promise a credit amount ahead of time.
Microsoft's Partner Center guidance says credit requests for CSP subscriptions come from CSP providers, through a Partner Center support ticket. Microsoft also wants proof that you asked for the credit: an email from an address on your company's domain. It won't accept a request from a personal email account.
Microsoft needs specific details to consider a claim. Email our support team at support@cloudservus.com, from your company email address, with:
If you can, add the incident IDs shown in Service health for your tenant.
Microsoft's CSP guidance says credit requests for services other than Azure must be submitted within one month from the end of the billing month in which the incident occurred. For a November outage, that window closes at the end of December. Send your details by Friday, December 11, so there's time to file and answer any follow-up questions from Microsoft.
Microsoft notes that a Service health post means a tenant might be affected, and that the impact on each tenant can vary. Your help desk tickets and user counts are the strongest evidence you'll have. Save them now, before the details fade.
If you buy through CloudServus, email support@cloudservus.com and we'll handle the claim from there. If you buy through another partner, ask them whether they're filing for you, and send them the same five details. For a broader look at what you're paying for, a Microsoft licensing assessment is a good place to start.
No. A credit request has to be filed. Microsoft's guidance also says a Service health incident means a tenant might be affected. Whether it qualifies is decided claim by claim.
No. Microsoft accepts credit requests for CSP subscriptions from CSP providers through Partner Center. Your request goes to your partner.
For services other than Azure, one month from the end of the billing month in which the outage happened. For a November outage, plan on the end of December 2026.
For Exchange Online, 25% of that service's monthly fee below 99.9% uptime, 50% below 99%, and 100% below 95%. Uptime is measured in user-minutes, so the result depends on how many of your users were affected and for how long. Microsoft makes the final decision.
No. Microsoft credits the affected service, not the full suite price.
Sources: Microsoft, Service Level Agreement for Microsoft Online Services (October 2026 edition); Microsoft Partner Center, How and when to request a credit from Microsoft (updated June 16, 2026).