Azure Functions 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.95%
- Observed, 365d
- n/a
- Major incident time
- n/a
- Credit on first breach
- 10%
Commitments and credits
- Consumption planFunction Apps on the Consumption plan99.95%
Monthly uptime below, credit of the bill
- Below 99.95%10%
- Below 99%25%
- Below 95%100%
- Flex Consumption, Premium or Dedicated App Service planFunction Apps on Flex Consumption, Premium or Dedicated App Service plans99.95%
Monthly uptime below, credit of the bill
- Below 99.95%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. Consumption plan: share of triggered executions that ran; Flex Consumption/Premium/Dedicated: minutes the Function App could be triggered.
- 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 Function App on the Consumption plan. Uptime Percentage Service Credit < 99.95% 10% < 99% 25% < 95% 100%
An execution counts as unavailable if the Function App history log captured no output five minutes after the trigger fired.
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 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 FunctionsMicrosoft Azure99.95% / 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.