Azure Blob Storage (Storage Accounts) SLAMicrosoft Azure · Storage · Microsoft Azure · Storage
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.99%
- Observed, 365d
- n/a
- Major incident time
- n/a
- Credit on first breach
- 10%
Commitments and credits
- Hot / Transaction Optimized, LRS/ZRS/GRS/GZRS (reads and writes), RA-GRS/RA-GZRS writesStorage accounts in the Hot access tier99.9%
Monthly uptime below, credit of the bill
- Below 99.9%10%
- Below 99%25%
- Hot / Transaction Optimized, RA-GRS and RA-GZRS read requestsRead requests to read-access geo-redundant accounts (with retry against the secondary region)99.99%
Monthly uptime below, credit of the bill
- Below 99.99%10%
- Below 99%25%
- Cool / Cold / Archive, write requests (all redundancy types)Storage in the Cool, Cold and Archive access tiers99%
Monthly uptime below, credit of the bill
- Below 99%10%
- Below 98%25%
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. Uptime = 100% minus Average Error Rate (hourly Failed Storage Transactions / Total Storage Transactions).
- Credit cap
- Maximum published credit is 25% for storage; overall 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
Service Credit –RA-GRS and RA-GZRS (read requests) for Hot, and Transaction Optimized Access Tiers Uptime Percentage Service Credit < 99.99% 10% < 99% 25%
Maximum credit for Storage Accounts is 25% (no 100% tier). As printed in the September 2026 edition, Cool/Cold/Archive read requests show '< 99.9% 10%, < 98% 25%' for both RA-GRS/RA-GZRS and LRS/ZRS/GRS/GZRS. Failed transactions are defined by maximum processing times (e.g. 2 seconds per MB for PutBlob/GetBlob).
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 storage SLAs
ServiceDowntime vs allowed
Volumes Block StorageDigitalOcean99.99% / 100%
Azure Blob Storage (Storage Accounts)Microsoft Azure99.99% / n/a
Cloud StorageGoogle Cloud99.95% / 99.927%
Amazon S3 (Standard)AWS99.9% / 99.178%
Cloudflare R2Cloudflare99.9% / 100%
Spaces Object StorageDigitalOcean99.9% / 100%
OCI Object StorageOracle Cloud Infrastructure99.9% / n/a
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.