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.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains App Service plan in context, with comparison tables and the common traps.
Terms in this definition
- region
A provider-defined grouping in VCF Automation of Supervisors that all share one NSX Local Manager; tenants consume its compute, storage and memory via quotas set per region.
- Archive
Offline access tier for blobs, cheapest to store yet dearest to access. Reading a blob means rehydrating it first, which can take as long as 15 hours.
- COUNT
A DAX function returning how many non-blank numbers, dates or text values a column contains. Boolean columns need COUNTA instead, and for counting the rows of a table COUNTROWS is the better choice.
- LAMP
Short for Linux, Apache, MySQL and PHP (Perl and Python also fill the P): a widely used open-source stack for web applications whose database is frequently Azure Database for MySQL.
Related terms
- Azure Functions Dedicated plan
Running Functions on an App Service plan. Executions have no time limit, and from the Basic tier upwards apps can integrate with a VNet.
- Dedicated
Running Azure Functions on an App Service plan, which removes the execution time limit and offers VNet integration on Basic and higher tiers.
- Dedicated plan
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.
- Scale Up
Picking a bigger or smaller instance size, or another pricing tier, for an App Service plan by hand.
- Zone-redundant plan
A Premium v2 or later App Service plan distributing a minimum of two instances (formerly three) over availability zones.