Azure Functions SLA
Microsoft Azure · Compute · promises up to 99.95% · SLA of Sep 1, 2026 · checked 25h 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
TierUptimeCredit of the monthly bill
- Consumption planFunction Apps on the Consumption plan99.95%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%below 99.95%: 10% · below 99%: 25% · below 95%: 100%
More in compute
ServicePromisedFirst creditObserved 365dDowntime
AWS LambdaAWS · Compute · Standard99.95%First credit10%Observed 365d99.178%All incidents 99.852%
Cloudflare WorkersCloudflare · Compute · Enterprise99.99%First credit10%Observed 365d100%All incidents 99.984%
Confluent Cloud for Apache FlinkConfluent · Compute · Flink (per region)99.99%First credit5%Observed 365d99.628%All incidents 97.169%
DigitalOcean Kubernetes (DOKS) HA control planeDigitalOcean · Compute · HA control plane99.95%First credit10%Observed 365d100%All incidents 99.992%
Compute EngineGoogle Cloud · Compute · Instances in Multiple Zones (Premium Tier)99.99%First credit10%Observed 365d99.927%All incidents 99.488%
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. 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
- Status history
- Azure publishes post-incident reviews as web pages only, with no machine-readable history, so observed uptime is not computed.
- Weighted uptime
- All incidents, weighted: 100% · Downtime
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.
Sources: each vendor's own SLA page (re-read monthly) and status page feed (read every Friday). A summary, not the contract: the contract you sign governs. Logos via logo.dev; trademarks belong to their owners.