I want a SLA credit for EX1550543 / MO1550821

A Microsoft 365 administrator should document the tenant’s impact now and submit an SLA credit request through Microsoft 365 billing support for incidents EX1550543 and MO1550821; a public incident listing does not automatically establish credit eligibility.

1. Preserve tenant-specific evidence

1. In the Microsoft 365 admin center, open Health > Service health.
2. Open EX1550543 and MO1550821 under active issues—or later under Issue history—and save their updates and final incident reports. The details include the estimated start time, affected services, status, user impact, and Microsoft’s updates. ^1^
3. Record:
   • Actual start and end times for your organization, including time zone.
   • Affected Microsoft 365 and Copilot subscriptions.
   • Number and locations of affected users.
   • Exact symptoms, such as mailbox connection failures or Copilot unavailability.
   • Screenshots, errors, logs, and any support correspondence.
   • The tenant ID and both incident IDs.

Credits are assessed for the affected service and outage duration, not automatically for the entire Microsoft 365 plan. An advisory is not typically eligible, and an incident appearing in Service Health only indicates that the tenant might have been affected; Microsoft evaluates actual customer impact and the final incident record. ^2^

2. Submit through the correct billing channel

Subscription purchased directly from Microsoft

An administrator should:

1. Open the Microsoft 365 admin center.
2. Select Help & support at the lower-right.
3. Enter: SLA service credit request for EX1550543 and MO1550821.
4. If the suggested results do not resolve it, select Contact Support.
5. Choose phone or email, provide the contact details, and submit the request. ^3^
6. Include the collected evidence and request separate assessment of:
   • Exchange Online impact under EX1550543.
   • Microsoft 365/Copilot impact associated with MO1550821.

Use wording such as:

Requesting an SLA service credit for tenant impact from EX1550543 and MO1550821 on November 12, 2026. Impact began at approximately 12:00 noon EDT and affected [number] users in [locations]. Affected subscriptions/services: [list]. Impact ended at [time, or “ongoing”]. Attached are errors, timestamps, Service Health updates, and user-impact evidence.

If every subscription was purchased through a partner, Microsoft directs customers to contact that partner rather than opening a direct Microsoft support request. ^3^

Subscription purchased through a CSP partner

Send the claim and evidence to the CSP provider that bills the organization. Only CSP direct and indirect providers can submit this Microsoft credit request; indirect resellers cannot submit it themselves. The provider submits a Partner Center support ticket containing the tenant GUID, incident IDs, proof of impact, affected subscriptions, and confirmation that the subscriptions were purchased through CSP. ^2^

For non-Azure services, the documented CSP claim deadline is within one month after the end of the billing month in which the incident occurred. If approved, the credit appears on a subsequent invoice and reconciliation data. ^2^

Eligibility limitation

The final credit cannot be determined while the incident duration and tenant impact are still being finalized. Microsoft will compare the documented outage against the applicable service SLA, exclusions, and availability threshold. SLA credits generally apply as a percentage of the fee for the affected service; they do not compensate for lost revenue or other business damages. ^4^

Do not post the tenant ID, invoice details, user information, or logs containing personal data in this public Q&A thread; provide them only in the private Microsoft or CSP support case.

References

1. How to check Microsoft 365 service health
2. How and when to request a credit from Microsoft
3. Get support for Microsoft 365 for business
4. How to read a service-level agreement (SLA)