Azure App Service SLA Credits & Refunds

App Service downtime that's billed against your Azure subscription is usually creditable, but the SLA fine print determines how much. This guide walks through the App Service availability commitment Microsoft publishes, the exclusions that quietly disqualify many claims, and what FinOps teams do to systematically recover credits across an Azure tenant.

What this guide covers

• The official Azure App Service uptime commitment and credit tiers
• Which incidents qualify (and which exclusions silently disqualify claims)
• How to file an App Service credit request inside the Azure claim window
• Why manual claim recovery typically leaves money on the table

Frequently asked questions about Azure App Service SLAs

What is the typical SLA uptime guarantee for Azure App Service?

Azure guarantees 99.95% uptime for App Service when running on Basic, Standard, Premium, or Isolated tiers (Free and Shared tiers carry no SLA). If Azure fails to meet this commitment during a billing cycle, you are eligible to receive a portion of your App Service spend back as a service credit — typically 10% at under 99.95% and 25% at under 99%.

How do I claim Azure App Service SLA credits after an outage?

Submit a billing support request through the Azure portal: Help + Support → New support request → Issue type: Billing → Problem type: Service credit request. Within two months of the billing period in question, provide the affected Subscription ID and Resource ID, the start and end timestamps of the impacted period, your evidence (Azure Monitor logs, Resource Health alerts, or independent monitoring), and your calculated Monthly Uptime Percentage for App Service. Microsoft validates against its internal incident records before issuing the credit to your billing account.

What exclusions apply to the Azure App Service SLA?

Notably, App Service running on the Free or Shared (F1/D1) tiers carries no SLA at all, and application-level errors caused by your own code or deployment slots are not covered.

Why is it difficult to get refunds for App Service outages manually?

Compute outages rarely show up cleanly. An App Service workload might be partially degraded — some instances fail, others stay healthy — and the SLA only counts the portion of capacity that was actually unavailable. To prove a claim you need per-instance (or per-task) error-rate data, not just an aggregate dashboard. Most teams discover this only when their first credit request comes back denied for "insufficient evidence."

Related Azure SLA guides

Other Azure services creditable through the same portal-based billing request process:

• Azure Virtual Machines SLA credits — Compute
• Azure Azure Functions SLA credits — Compute
• Azure AKS SLA credits — Compute
• Azure Blob Storage SLA credits — Storage

Recover Azure credits without a portal grind

Azure billing support requests for App Service aren't difficult to file — they're tedious. Each one takes the same kind of subscription-ID, resource-ID, timestamp, and uptime-calculation packaging, repeated for every incident across every subscription you own.

Next Signal detects App Service SLA breaches across your Azure tenants, packages the credit request in the format Microsoft expects, and submits it. See how it works or start a free trial.