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.
Also called Premium V2.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains P1V2 in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- 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.
- Dedicated
Running Azure Functions on an App Service plan, which removes the execution time limit and offers VNet integration on Basic and higher tiers.
- Azure Functions Premium plan
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.
- 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.
Related terms
- Automatic scaling (App Service)
Rule-free scale-out choice for Premium v2 to v4 App Service plans that adds prewarmed instances according to HTTP traffic. Scaling on a CPU threshold is not possible with it.
- Zone-redundant plan
A Premium v2 or later App Service plan distributing a minimum of two instances (formerly three) over availability zones.