Compensation for Microsoft 365 related to the outage on November 12 and 13, 2026, is neither automatic nor calculated based on the full subscription. The customers Those affected must document the impact on their environment and request a credit under the SLA. For purchases made through a CSP reseller, claims regarding November must be received by the supplier by December 31, 2026.
Who is eligible to request compensation for Microsoft 365?
Microsoft 365 compensation may be paid only if the unavailability of a covered service causes its availability to fall below the threshold specified in the applicable SLA. The SLA, or service level agreement, is a contractual commitment that defines a measurable level of availability and the associated credits in the event of non-compliance.
The outage reported on November 12 and 13, 2026, disrupted Exchange Online, Outlook, and other Microsoft 365 services, among others. According to the Associated Press in 2026, Microsoft attributed the problem to servers that failed the automated health checks. The associated identifiers include EX1550543 for Exchange Online and MO1550821 for the broader incident.
However, simply seeing an incident listed in the bord table is not enough. Microsoft clarifies in 2026 that an entry means your tenant—that is, your company’s specific Microsoft environment—may be affected. The actual impact on your users and compliance with the SLA terms remain to be seen.
Incidents classified as “advisory”—that is, as alerts or minor disruptions—are generally not eligible under the Microsoft policy published in 2026. An inability to send emails for several hours is easier to establish than a simple slowdown without measurable data or identified users.
Why must the application be submitted by December 31, 2026?
For Azure hors services purchased through a CSP provider, Microsoft requires that claims be submitted in 2026 within one month of the end of the relevant billing month. A service outage occurring in November 2026 must therefore be reported to the reseller no later than December 31, 2026.
CSP stands for Cloud Solution Provider, the program through which a provider resells and manages Microsoft licenses. The customer submits their application to the provider, who then submits the credit request to Microsoft. Waiting for automatic resolution would waste valuable time, since Microsoft does not issue a credit simply because an outage appears in Service Health.
Companies that purchased their licenses directly from Microsoft must contact the Microsoft 365 Admin Center for assistance, according to a response from Microsoft support published in November 2026. The contract and purchase channel must be verified immediately, as the applicable procedure depends on the billing relationship.
From the agency's perspective, the first step is to locate the invoice and the account from which the licenses are managed. This simple check prevents the agency from sending a request to Microsoft that only the authorized reseller can submit.
What documentation is required to receive an SLA credit?
A Microsoft 365 SLA credit request must identify the tenant and the incident, and then specify the duration of the outage, the affected services, the affected users or sites, and any workarounds attempted. In 2026, Microsoft requires this information to verify the impact at the customer level rather than merely confirming the existence of a general incident.
In the Microsoft 365 admin center, the Health > Service health path displays the incident ID, the affected service, the estimated start time, user impact, status, and updates. Microsoft documentation states that, as of 2026, the history of resolved incidents can be viewed over a 7- or 30-day period. It is therefore best to export or capture the information quickly.
A complete application package includes the following documents:
- Note the exact Microsoft 365 tenant ID and the references EX1550543 or MO1550821 if they appear in your environment;
- List the Service Health messages, including the start times, recovery times, and the named services;
- Identify the affected users, facilities, and functions, without limiting yourself to a broad category such as “the entire company”;
- Please attach the internal tickets, error screenshots, available logs, and Hor reports dated November 2026;
- Describe the steps you took, such as restarting clients, accessing the web, or using a backup communication channel.
The quality of the evidence matters more than its quantity. A table showing that 38 users were unable to send messages between two verifiable hor dates is better than a series of screenshots without a timeline. However, avoid including personal data unnecessarily, in accordance with the principle of data minimization set forth in the RGPD, effective since 2018.
Also keep a copy of Microsoft 365. A continuity plan must remain accessible in the event that the primary tool fails or an administrator account is compromised; this approach aligns with preparedness measures for Cyber threats targeting businesses.
How much compensation can you expect from Microsoft 365?
Microsoft 365 compensation takes the form of a credit calculated per service and based on the duration of eligible downtime. In 2026, an outage limited to SharePoint within an Office 365 suite does not entitle the customer to a credit for the entire suite. The percentage applies to the affected service and the relevant contract period.
For Exchange Online, the SLA tables published in 2026 provide for three tiers. They allow you to estimate the approximate amount of the credit, but not to calculate a final credit amount on your own: Microsoft must still confirm the availability metric, tenant eligibility, and the billed base.
| Availability during the applicable period | Planned service credit | Interpretation |
|---|---|---|
| Less than 99.9 % | 25 % | Have an eligible Exchange Online service |
| Less than 99 % | 50 % | Not a refund for the entire Microsoft 365 suite |
| Less than 95 % | 100 % | Credit capped at the applicable service and period |
The 50 % rate sometimes mentioned in November 2026 does not, therefore, mean that half of all your licenses will be refunded. If only Exchange Online is deemed unavailable, Microsoft does not automatically issue credits for Teams, SharePoint, OneDrive, or Office applications. The current Microsoft Online Services Global SLA is effective as of November 17, 2026.
Honestly, the time spent on the case should be proportionate to the financial stakes. For a few licenses and a short interruption, a simple, well-documented request is sufficient. For a larger fleet, the claim can also be used to quantify the business cost of the downtime: lost hours, delayed orders, or customer service unavailability.
How can I submit the application without holding up the process?
The submission channel depends on how Microsoft 365 licenses are purchased. In 2026, a direct customer submits a claim through support in the Microsoft 365 admin center, while a customer billed by a CSP reseller forwards the details to that provider, who then submits the claim to Microsoft.
The message must include the terms “SLA service credit request” or “SLA credit request,” specify the billing month of November 2026, and list each affected service separately. Specify the times with the time zone, for example, Paris time, as ambiguous time frames can slow down the analysis.
Next, request a confirmation of receipt and a case reference number. If the dealer requests additional information, respond before the deadline rather than waiting until the application is perfect. At this stage, it’s better to submit an admissible application on time than to send a very detailed response after December 31, 2026.
Finally, the outage raises a question of business continuity, which is distinct from reimbursement. Administrative access must be protected, backup channels must be tested, and external dependencies must be documented. For remote teams, the choice of a A VPN Designed for Security and Privacy It can secure certain access points, but it does not restore a cloud service that is unavailable at the provider's end.
Addressing claims and digital continuity early on helps avoid most unpleasant surprises. An outside perspective can help distinguish between the contractual documentation, technical evidence, and measures that will minimize the impact of the next outage.
FAQ on Microsoft 365 Credits
Does a visible outage in Service Health automatically entitle me to a credit?
An outage visible in Microsoft 365 Service Health does not automatically trigger a credit in 2026. Microsoft reviews the impact on the tenant, the affected service, the measured duration, and the terms of the applicable SLA.
Is the SLA credit deposited into the company's bank account?
The Microsoft 365 SLA credit is a service credit, not necessarily a bank refund. How it is handled in practice depends on the contract, the billing channel (direct or CSP), and the eligibility determination.
Can we file a claim if only a few employees were affected?
A company may submit an application even if only some of its users were affected, provided it documents the impact in detail. In 2026, Microsoft will assess the users, sites, duration, and service involved.
Should EX1550543 and MO1550821 be cited in the application?
The identifiers EX1550543 and MO1550821 must be cited if they correspond to the notices posted in your tenant regarding the November 2026 outage. The ID displayed in your own administration center remains the most reliable reference.
Is an "advisory" incident covered by the SLA?
An incident classified as “advisory” is generally not eligible for SLA credits under the Microsoft policy published in 2026. An analysis of the contract and the actual impact is still necessary before dismissing the request.