Running Azure Functions on App Service plan instances, paying App Service rates. Instance counts change manually or through autoscale, not in response to incoming events, and enabling Always On stops non-HTTP triggers going idle.
Also called App Service plan.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Dedicated plan in context, with comparison tables and the common traps.
Terms in this definition
- Authorisation levels
Key requirements for HTTP triggers in Azure Functions: Anonymous needs no key, Function accepts a function or host key, and Admin requires the master key.
- App Service plan
Billing unit providing the compute, defined by region, OS, pricing tier and instance size and count, on which one or more apps run. Separate plans are needed for Linux and Windows apps.
- App Service
Managed PaaS hosting for web apps and Web App for Containers, run in a sandbox without OS access. Deployment slots and autoscale start at the Standard tier.
- Autoscale
Azure Monitor capability that adds or removes instances on a schedule or once a metric rule has been true for its full duration. The maximum instance count merely sets a ceiling and never triggers scaling itself.
Related terms
- Azure Functions
Serverless compute for event-driven code, started by triggers such as HTTP, timer, Blob or Event Grid and hosted on a Consumption, Premium or Dedicated plan.
- Init container
Runs and finishes before the main containers launch, typically to fetch models or data. Container Apps does not let these use managed identity in Consumption-only environments or on the Dedicated plan.