✓
Credit-backed
Publishes an SLA backed by tiered service credits: 99.9% uptime, credits up to 100%.
Source: official SLA ↗ · checked Jun 2026 · View as JSON
99.9%
Uptime
100%
Max credit
60d
Claim window
Credit
Remedy
Standard
Min plan
Reference calculation
Estimate service credit
See what the published credit tier would imply for one affected service and billing period. This is an estimate, not a claim decision.
Use the uptime percentage calculated under the vendor's SLA, not an independent monitoring result. Affected spend means the monthly fees for the affected service.
The estimate uses the published terms below and does not adjudicate measurement rules, exclusions, plan eligibility, or whether a claim is still timely.
How to claim
Submission
Microsoft Support · support.microsoft.com/en-us/
Deadline
60 days of incident
Review timeline
Typically within 45 days of receipt of the claim
Credit applied
Applied to next invoice
Required evidence: Detailed description of the Incident, Time and duration of downtime, Affected resource names, Number and location(s) of affected users, Description of errors that occurred during the incident
Common exclusions
Scheduled maintenance
Force majeure events
Customer misconfigurations
Online Services or service tiers provided free of charge
Previews
Support tiers complementary, not the SLA
Standard
SLA-eligible
Included · Business hours
Enterprise
SLA-eligible
Custom · 24/7
Per-service SLAs · 3
Most platforms commit to SLAs per service, not one blanket number.Service
Category
Uptime
SLA
Power BI Embedded
Embedded analytics for applications
Analytics
Uptime 99.9%
SLA covered
Power BI Report Server
On-premises report server (no cloud SLA)
Analytics
Uptime 99.9%
SLA covered
Power BI Service
Cloud-based BI service
Analytics
Uptime 99.9%
SLA covered
Notes — Microsoft is a Other SaaS provider. See the official SLA at https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services.
Found an error?
Suggest a correction ↗