Functions hosting plan that keeps instances pre-warmed to avoid cold starts and supports VNet integration; executions default to 30 minutes, a limit you can raise in host.json.
Also called Elastic Premium.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Functions Premium plan in context, with comparison tables and the common traps.
Terms in this definition
- Cold
Online access tier for blobs that costs less to store than Cool but more to read, while data stays instantly available.
- Regional VNet integration
From the Basic tier up, App Service can send outbound traffic into a VNet by way of a subnet delegated to
Microsoft.Web/serverFarms. Reaching the app privately from inside, though, calls for a private endpoint.
Related terms
- EP1
EP1, EP2 and EP3 are the Elastic Premium sizes for Azure Functions, offering 1 core with 3.5 GB, 2 cores with 7 GB and 4 cores with 14 GB respectively. Names beginning with P, P1V2 for instance, denote Dedicated plans that lack elastic scaling.
- P1V2
An App Service Premium V2 size. For Azure Functions, sizes beginning with P are Dedicated plans without elastic scaling, in contrast to the Elastic Premium EP1, EP2 and EP3 sizes.
- Runtime Scale Monitoring
Function apps on the Azure Functions Premium plan that use SQL triggers need this runtime setting turned on, so they can scale out as pending changes build up.