Azure Virtual Machines SLAMicrosoft Azure · Compute · Microsoft Azure · Compute
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
- Availability ZonesTwo or more VMs deployed across two or more Availability Zones in the same region99.99%
Monthly uptime below, credit of the bill
- Below 99.99%10%
- Below 99%25%
- Below 95%100%
- Availability Set / Dedicated Host GroupTwo or more VMs in the same Availability Set or same Dedicated Host Group (not Availability Sets using Azure shared disks)99.95%
Monthly uptime below, credit of the bill
- Below 99.95%10%
- Below 99%25%
- Below 95%100%
- Single-Instance VM, Premium SSD / Premium SSD v2 / Ultra DiskSingle VM with Premium SSD for all OS disks and Premium SSD, Premium SSD v2 or Ultra Disk for all data disks99.9%
Monthly uptime below, credit of the bill
- Below 99.9%10%
- Below 99%25%
- Below 95%100%
- Single-Instance VM, Standard SSD Managed DiskSingle VM whose lowest disk type is Standard SSD99.5%
Monthly uptime below, credit of the bill
- Below 99.5%10%
- Below 95%25%
- Below 90%100%
- Single-Instance VM, Standard HDD Managed DiskSingle VM whose lowest disk type is Standard HDD95%
Monthly uptime below, credit of the bill
- Below 95%10%
- Below 92%25%
- Below 90%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. VM downtime = minutes with no Virtual Machine Connectivity.
- 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
The following Service Levels and Service Credits are applicable to Customer’s use of Virtual Machines deployed across two or more Availability Zones in the same region: ... < 99.99% 10% < 99% 25% < 95% 100%
For a single VM with mixed disk types, the lowest disk-type SLA applies. VMs sharing the same Shared Disk are treated like single-instance VMs. Azure SLAs are published only inside the consolidated Microsoft Online Services SLA document (monthly editions; the September 2026 edition was current on 2026-09-23).
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.
SLA changes
- May1Azure Virtual MachinesAvailability Zones tier added: VMs across two or more zones get 99.99% (10/25/100% credits). Not present in the March 2018 edition.Source
- Mar15Azure Virtual Machines100% credit tier added below 95% for Availability Set and single-instance VMs. January 2017 edition: Availability Set < 99.95% 10%, < 99% 25% (no 100% tier); March 15, 2017 edition adds '< 95% 100%'.Source
- Jan1Azure Virtual MachinesSingle-instance VM SLA of 99.9% (premium storage for all disks) first appears. December 2016 edition covered only VMs in an Availability Set (99.95%, credits 10% / 25%).Source
Other compute SLAs
ServiceDowntime vs allowed
Amazon EC2AWS99.99% / 99.178%
Cloudflare WorkersCloudflare99.99% / 100%
Confluent Cloud for Apache FlinkConfluent99.99% / 99.628%
Droplets (CPU)DigitalOcean99.99% / 100%
Compute EngineGoogle Cloud99.99% / 99.927%
Azure Virtual MachinesMicrosoft Azure99.99% / n/a
AWS LambdaAWS99.95% / 99.178%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean99.95% / 100%
Confluent Cloud ksqlDBConfluent99.9% / 99.628%
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.