Uptimeby GlyphAzure Virtual Machines SLA
Microsoft Azure · Compute · promises up to 99.99% · SLA of Sep 1, 2026 · checked 13d ago
Incidents, last 365 days
Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
Commitments and credits
Availability Zones
Two or more VMs deployed across two or more Availability Zones in the same region
Credit: below 99.99%: 10% · below 99%: 25% · below 95%: 100%
Availability Set / Dedicated Host Group
Two or more VMs in the same Availability Set or same Dedicated Host Group (not Availability Sets using Azure shared disks)
Credit: below 99.95%: 10% · below 99%: 25% · below 95%: 100%
Single-Instance VM, Premium SSD / Premium SSD v2 / Ultra Disk
Single VM with Premium SSD for all OS disks and Premium SSD, Premium SSD v2 or Ultra Disk for all data disks
Credit: below 99.9%: 10% · below 99%: 25% · below 95%: 100%
Single-Instance VM, Standard SSD Managed Disk
Single VM whose lowest disk type is Standard SSD
Credit: below 99.5%: 10% · below 95%: 25% · below 90%: 100%
Single-Instance VM, Standard HDD Managed Disk
Single VM whose lowest disk type is Standard HDD
Credit: below 95%: 10% · below 92%: 25% · below 90%: 100%
SLA changes
Azure Virtual Machines
The SLA page text changed (6 sentences added, 2 removed); not yet reviewed.
2 weeks agoPage
Azure Virtual Machines
Availability Zones tier added: VMs across two or more zones get 99.99% (10/25/100% credits). Not present in the March 2018 edition.
8 years agoSource
Azure Virtual Machines
100% 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%'.
9 years agoSource
Azure Virtual Machines
Single-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%).
9 years agoSource
More in compute
AWS LambdaAWS promises 99.95% uptime, with a 10% credit when it misses; its status page showed 3 d of major outage in the last year.
Observed 99.178% over 365 days
Amazon EC2AWS promises 99.99% uptime, with a 10% credit when it misses; its status page showed 3 d of major outage in the last year.
Observed 99.178% over 365 days
Cloudflare promises 99.99% uptime, with a 10% credit when it misses; its status page showed 7.6 h of major outage in the 71 days on file.
Observed 99.552% over 365 days
Confluent promises 99.99% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
Confluent promises 99.9% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
DigitalOcean promises 99.95% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
DigitalOcean promises 99.99% uptime, with a 100% credit when it misses; its status page showed no major outage in the last year.
Observed 100% over 365 days
Google Cloud promises 99.99% uptime, with a 10% credit when it misses; its status page showed 3.7 h of major outage in the 252 days on file.
Observed 99.939% over 365 days
Cloudflare WorkersCloudflare promises 99.99% uptime, with a 10% credit when it misses; its status page showed 7.6 h of major outage in the 71 days on file.99.99%First credit10%Observed 365d99.552%All incidents 99.951%
Confluent Cloud for Apache FlinkConfluent promises 99.99% uptime, with a 5% credit when it misses; its status page showed no major outage in the last year.99.99%First credit5%Observed 365d100%All incidents 97.635%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean promises 99.95% uptime, with a 10% credit when it misses; its status page showed no major outage in the last year.99.95%First credit10%Observed 365d100%All incidents 99.989%
Compute EngineGoogle Cloud promises 99.99% uptime, with a 10% credit when it misses; its status page showed 3.7 h of major outage in the 252 days on file.99.99%First credit10%Observed 365d99.939%All incidents 99.467%
Terms, exclusions and sources
- 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
- Status history
- Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
- Weighted uptime
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).