EX1550543 SLA credit: how to claim your Microsoft 365 service credit for the Nov 12 Exchange Online outage

Most admins assume an EX1550543 SLA credit will show up on its own because Microsoft posted the incident. It won't. Microsoft only credits what a tenant claims, per affected service, with its own evidence, inside a deadline set by your billing month.
This is the sequence we run with a tenant after an outage like Nov 12: confirm the impact from your own Service Health record, do the math per service, and file through the channel that actually bills you.
Confirm your tenant was hit: EX1550543 and MO1550821 in Service Health
Microsoft logged the Exchange Online side as EX1550543 ("Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods") and pointed impact to other Microsoft 365 services at MO1550821. The public mirrors and news reports don't agree on start times, so don't build your claim on them. Use the times in your own tenant.
Go to the Microsoft 365 admin center > Health > Service health > Issue history. Open each incident ID that appears, and save the issue type (incident or advisory), affected services, start and end times, user impact text, and the post-incident report when it's available. Partner Center notes that advisory incidents aren't typically eligible, so the issue type matters.
What breaks it:
- Export it this week. Issue history only shows items resolved in the last 7 or 30 days, and your claim needs the record after the dashboard drops it.
- Collect your own impact evidence: help desk tickets, monitoring alerts, user reports with times and locations, and what you tried during the incident.
- Don't add incident IDs you can't see in your tenant. If an ID from Reddit isn't in your Issue history, leave it out of the claim.
Do the math per service: user-minutes, not one percentage for the suite
Admin threads this week argue 25% versus 50%. Neither is the answer for your tenant. Microsoft's Q&A moderator put it plainly: credits vary by service and by measured availability, so one percentage can't be applied to the whole suite. Partner Center gives the same rule with an example: an Office 365 customer with only a SharePoint outage gets SLA credit for SharePoint, not the whole plan.
For Exchange Online, the Online Services SLA defines downtime as any period when users can't send or receive email with Outlook on the web, measured in user-minutes: each incident's length in minutes multiplied by the number of users it hit. Monthly uptime is (user-minutes − downtime) ÷ user-minutes × 100, and the service credit tiers are:
- Below 99.9%: 25%
- Below 99%: 50%
- Below 95%: 100%
The credit is a percentage of what you paid for that service in the calendar month, not of your whole Microsoft invoice. Check the Exchange Online section of the current SLA edition before you file, because Microsoft revises it.
What breaks it:
- Count affected users, not licensed users. If only one region or one connection method failed for you, the downtime figure drops.
- Work out Exchange Online separately from anything you're claiming under MO1550821. Each service has its own SLA terms.
- Write the math into the claim. A reviewer can check a number. They can't do much with "we were down all day."
File it: admin center if you buy direct, Partner Center if you buy through a CSP
Bought direct. An admin opens the Microsoft 365 admin center, selects Help & support, describes the request (SLA credit for EX1550543), then selects Contact Support and attaches the evidence. Microsoft's support page says you need at least one subscription bought through Microsoft to use this route.
Bought through a CSP. Partner Center accepts credit requests only from CSP direct and indirect providers, not indirect resellers, and the partner files it as a support ticket. They need your tenant GUID, the outage incident ID, whether the subscriptions were bought through CSP, and proof that you were affected and asked for the credit. That includes an email requesting the credit sent from your tenant's domain. Personal addresses are rejected.
What breaks it:
- Know the deadline rule. For non-Azure services, CSP requests are due within one month from the end of the billing month the incident occurred in. Your billing month sets the date.
- Send your CSP a complete pack: tenant GUID, incident IDs, times, affected user count and locations, troubleshooting notes, and your support ticket number.
- Ask for the partner's ticket number so you can follow up when the claim is being reviewed.
What "good" looks like: the five-step claim baseline
If you do nothing else this month, these five steps get a credit request from "we should" to filed:
- Save the EX1550543 and MO1550821 records from Issue history, including issue type and the post-incident report.
- Count affected users and minutes from your own tickets and monitoring, per service.
- Run the Exchange Online uptime math against the current SLA tiers and write the result down.
- File through your billing channel: Help & support if you buy direct, your CSP's Partner Center ticket if you don't.
- Check the next invoice. Partner Center says approved credits show up on the next invoice and reconciliation data.
A service credit only comes back if someone tracks downtime in user-minutes, files the claim before the deadline, and checks the next invoice; our Cloud Cost Optimization work puts that on a monthly checklist alongside license right-sizing, so credits and overspend don't depend on someone remembering after an outage.
The uncomfortable question
Was the outage bad enough for a credit? That's the wrong question. Can you prove, in user-minutes, how bad it was for your tenant, before the Issue history entry ages out? Open Health > Service health > Issue history today, find EX1550543, and compare its times with your own help desk tickets. If the numbers don't line up, fix that before you file.
Frequently asked questions
Is the EX1550543 SLA credit applied automatically?
No. A Microsoft Q&A moderator confirmed that SLA credits aren't issued just because Service Health shows an outage. You submit a request and Microsoft evaluates it against the SLA.
What is the deadline for a Microsoft 365 SLA credit request through a CSP?
Partner Center guidance says credit requests for non-Azure services must be submitted within one month from the end of the billing month in which the incident occurred. Azure claims get two months.
Who can file an SLA credit claim in Partner Center?
Only CSP direct and indirect providers. Indirect resellers can't, so if you buy through a reseller, the provider behind them files the ticket.
Cloud Cost Optimization tracks outage credits, license right-sizing and the next invoice every month, so nothing depends on someone remembering after an incident.
See Cloud Cost Optimization →Get the next Insights post by email.
Keep reading
MC1476200: Copilot usage based billing turns on by default December 1. Set the spending policy before your tenant does it for you
MC1476200 turns on Copilot usage-based billing by default for new Copilot Business seats from Dec 1 (CSP), with a 4,000-credit policy. How to cap it.
Read the article →AADSTS7000215 followed by a successful sign-in: how to check Entra service principal sign-ins for stolen app secrets
AADSTS7000215 on a service principal sign-in, then a success from an IP you don't own, means someone holds your app secret. Where to look, what to block.
Read the article →MC1506733: Entra lets every user create agent blueprints on Nov 4. Turn it off before your app-registration lock gives you false comfort
MC1506733 lets default Entra users create agent blueprints from Nov 4. The toggle, what it doesn't block, and the monthly check to keep it set on purpose.
Read the article →

