Microsoft business customers affected by the recent disruption to Outlook, Teams and other services may be eligible for billing credits under their service-level agreements, but compensation is not automatic and depends on the affected service and applicable contract.
WIRED reported that business subscribers should review their agreements following the November 12 disruption. The potential remedy is a service credit, rather than a guaranteed cash payment for every affected user.
Business subscriptions and personal plans have different terms
A service-level agreement, or SLA, sets out a provider’s service commitments and the remedies available when qualifying performance falls short. WIRED says these protections can apply to small business customers as well as large enterprises.
However, the terms are product-specific. Customers should check the agreement covering their subscription rather than assume that an outage affecting several Microsoft products produces the same entitlement for each one.
Personal subscriptions are different. According to WIRED, the consumer Microsoft Services Agreement allows refunds or credits at Microsoft’s discretion but does not offer the same contractual uptime protections. A Microsoft 365 Family subscription should therefore not be treated as equivalent to a covered business subscription.
Credits may cover only the affected service
Microsoft’s Partner Center guidance says SLA credits depend on which services were affected. Its example explains that a customer with an Office 365 suite who experiences only a SharePoint outage receives an approved credit for SharePoint, not the entire suite.
The guidance also says credits are prorated according to the affected service and outage duration. These instructions cover services sold through the Cloud Solution Provider program; customers buying through other channels should check their own agreement and support route.
What customers need for a claim
For partner-submitted claims, Microsoft requires the customer tenant identifier, outage incident identifier and evidence that the customer experienced the disruption and requested a credit. The incident identifier is available through Service Health in the Microsoft 365 admin center.
Supporting evidence can include the time and duration of downtime, the number and locations of affected users, troubleshooting attempts and relevant support ticket details. Microsoft says advisory incidents are not typically eligible.
Under the Partner Center instructions, non-Azure claims must be submitted within one month after the end of the billing month in which the incident occurred. Azure claims have a two-month window. These are the published partner-channel deadlines, not a blanket statement covering every Microsoft contract.
For organizations affected by the Microsoft disruption, the next step is to document the impact and establish which service commitments apply. Neither an outage report nor a paid subscription alone guarantees an approved credit.
