Skip to main content
Premium v3 is the current generation of App Service Premium plans. Its sizes have the same number of cores as the Premium v2 size one step up and more memory, at a lower list price. nOps finds Premium v2 plans (P1v2, P2v2, P3v2) that run steadily on pay-as-you-go and estimates the saving from scaling them to P0v3, P1v3 or P2v3.

Why it matters

It is usually a scale-up in place with more memory for less money, and many older plans are still on Premium v2.

How nOps finds it

nOps reads the last 30 days of App Service billing. A plan is flagged when it was billed on at least 25 of those days and in the last 2 days, and is mostly pay-as-you-go rather than covered by reservations. Its 7-day pay-as-you-go cost, scaled to a month, is multiplied by the difference between the Premium v2 and Premium v3 list prices for the same region and operating system (P1v2 to P0v3, P2v2 to P1v3, P3v2 to P2v3). The target must be at least 3% cheaper, the service must not be mostly paid with credits, and the saving must be at least $5 a month.

Before you start

Permission to scale the App Service plan, and a quiet period: apps restart when the plan changes tier.

How to implement

  1. In the Azure portal, open the App Service plan and go to Scale up (App Service plan).
  2. Choose the Premium v3 size shown in the recommendation and apply. Or use az appservice plan update --resource-group RESOURCE_GROUP --name PLAN_NAME --sku P1V3.
  3. If Premium v3 is not offered for the plan, create a new Premium v3 plan in a new resource group and move the apps to it.
  4. Update sku_name in Terraform (or the SKU in Bicep or ARM templates) so a later deployment does not change it back.

Risks and considerations

  • Apps restart when the plan changes tier. Use deployment slots or a quiet period.
  • Reservations bought for Premium v2 do not cover Premium v3.
  • To roll back, scale the plan back to its Premium v2 size.

FAQs

No. Each target size has the same number of cores as the current one and more memory.