Azure SQL Database SLAMicrosoft Azure · Databases · Microsoft Azure · Databases
Promise vs reality
Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed. How this is measured
All incidents, weighted: 100% · Downtime- Promised
- 99.995%
- Observed, 365d
- n/a
- Major incident time
- n/a
- Credit on first breach
- 10%
Commitments and credits
- General Purpose / Business Critical / Premium / Hyperscale, Zone RedundantDatabases configured for Zone Redundant Deployments99.995%
Monthly uptime below, credit of the bill
- Below 99.995%10%
- Below 99%25%
- Below 95%100%
- Hyperscale / Business Critical / Premium / General Purpose, not zone redundantDatabases not configured for Zone Redundant Deployments99.99%
Monthly uptime below, credit of the bill
- Below 99.99%10%
- Below 99%25%
- Below 95%100%
- Basic / StandardBasic or Standard tier databases99.99%
Monthly uptime below, credit of the bill
- Below 99.99%10%
- Below 99%25%
- Below 95%100%
Terms
- Measured
- Uptime Percentage per 'Applicable Period': for metered pay-as-you-go services, the 30 days prior to and including the first day of the Incident; for other services, the calendar month. A minute is unavailable if all continuous connection attempts to the database fail.
- Credit cap
- Service Credits in any billing month will not exceed the monthly service fees for that Service or Service Resource in the Applicable Period
- Claim window
- Within 60 days of the Incident (Azure)
- How to claim
- Submit the claim to Microsoft customer support with incident description, time and duration of downtime, affected resource names, number/location of affected users and error descriptions
Not covered
- Factors outside Microsoft's reasonable control (natural disaster, war, government action, network failures outside Microsoft data centers)
- Services, hardware or software not provided by Microsoft
- Preview, pre-release, beta or trial versions, or purchases made with subscription credits
- Customer failure to follow required/supported configurations or published guidance
- Exceeding reasonable use or quotas, or throttling of suspected abuse
- Scheduled Downtime (at least 5 days' notice) and customer-initiated restart/stop/failover/scale operations
applicable to Customer's use of the General Purpose, Business Critical, Premium or Hyperscale tiers of the SQL Database Service configured for Zone Redundant Deployments: ... < 99.995% 10% < 99% 25% < 95% 100%
Business Critical with active geo-replication and a Compliant Secondary also carries an RPO commitment of 5 seconds (10% of the secondary's cost if attainment is below 100%) and an RTO commitment of 30 seconds.
Evidence: incidents, last 365 days
Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
Other databases SLAs
ServiceDowntime vs allowed
Amazon DynamoDBAWS99.999% / 99.178%
Azure SQL DatabaseMicrosoft Azure99.995% / n/a
MongoDB Atlas (database clusters)MongoDB99.995% / 99.989%
Lakebase PostgresDatabricks99.99% / n/a
Cloud SQLGoogle Cloud99.99% / 99.927%
Managed DatabasesDigitalOcean99.95% / 100%
Elastic Cloud Hosted (formerly Elasticsearch Service)Elastic99.95% / 99.146%
Promised in the SLAObserved on the vendor's status pagePartial historyShortfall
Summaries of published SLAs; the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.