Azure Functions SLA

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

An execution counts as unavailable if the Function App history log captured no output five minutes after the trigger fired.

All Microsoft Azure SLAsHow this is measuredSuggest a correction