Configure PremiumV2 tier for Azure App Service
The new PremiumV2 pricing tier provides Dv2-series VMs with faster processors, SSD storage, and double memory-to-core ratio compared to Standard tier. In this article, you learn how to create an app in PremiumV2 tier or scale up an app to PremiumV2 tier.
To scale-up a web app to PremiumV2, you need to have a Web App in Azure App Service that runs in a pricing tier lower than PremiumV2.
The PremiumV2 tier is currently available for App Service on Windows only. Linux containers are not yet supported.
PremiumV2 is already available in most Azure regions and growing. To see if it is available in your region, run the following Azure CLI command in the Azure Cloud Shell:
az appservice list-locations --sku P1V2
If you receive an error during app creation or App Service plan creation, then PremiumV2 is most likely not available for your region of choice.
Create an app in PremiumV2 tier
The pricing tier of an App Service app is defined in the App Service plan that it runs on. You can create an App Service plan by itself or as part of Web App creation.
When configuring the App Service plan in the Azure portal, select Pricing tier.
Choose one of the PremiumV2 options and click Select.
If you do not see P1V2, P2V2, and P3V2 as options, either PremiumV2 is not available in your region of choice, or you are configuring a Linux App Service plan, which does not support PremiumV2.
Scale up an existing app to PremiumV2 tier
Before scaling an existing app to PremiumV2 tier, make sure that PremiumV2 is available in your region. For information, see PremiumV2 availability. If it is not available in your region, see Scale up from an unsupported region.
Depending on your hosting environment, scaling up may require extra steps.
In the Azure portal, open your App Service app page.
In the left navigation of your App Service app page, select Scale up (App Service plan).
Select one of the PremiumV2 sizes, then click Select.
If your operation finishes successfully, your app's overview page shows that it is now in a PremiumV2 tier.
If you get an error
Some App Service plans cannot scale up to the PremiumV2 tier. If your scale-up operation gives you an error, you need a new App Service plan for your app.
Create a Windows App Service plan in the same region and resource group as your existing App Service app. Follow the steps at Create an app in PremiumV2 tier to set it to PremiumV2 tier. If desired, use the same scale-out configuration as your existing App Service plan (number of instances, autoscale, and so on).
Open your App Service app page again. In the left navigation of your App Service, select Change App Service plan.
Select the App Service plan you just created.
Once the change operation completes, your app is running in PremiumV2 tier.
Scale up from an unsupported region
If your app runs in a region where PremiumV2 is not yet available, you can move your app to a different region to take advantage of PremiumV2. You have two options:
- Create an app in new PremiumV2 plan, then redeploy your application code. Follow the steps at Create an app in PremiumV2 tier to set it to PremiumV2 tier. If desired, use the same scale-out configuration as your existing App Service plan (number of instances, autoscale, and so on).
If your app already runs in an existing Premium tier, then you can clone your app with all app settings, connection strings, and deployment configuration.
In the Clone app page, you can create a new App Service plan in the region you want, and specify the settings that you want to clone.
Automate with scripts
The following command creates an App Service plan in P1V2. You can run it in the Cloud Shell. The options for
--sku are P1V2, P2V2, and P3V2.
az appservice plan create \ --resource-group <resource_group_name> \ --name <app_service_plan_name> \ --sku P1V2
The following command creates an App Service plan in P1V2. The options for
-WorkerSize are Small, Medium, and Large.
New-AzureRmAppServicePlan -ResourceGroupName <resource_group_name> ` -Name <app_service_plan_name> ` -Location <region_name> ` -Tier "PremiumV2" ` -WorkerSize "Small"