Skip to content

Commit 6e8ee4b

Browse files
Merge pull request #249705 from msangapu-msft/premium
premium
2 parents 251eb7f + c16e090 commit 6e8ee4b

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/app-service/app-service-configure-premium-tier.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to better performance for your web, mobile, and API app i
44
keywords: app service, azure app service, scale, scalable, app service plan, app service cost
55
ms.assetid: ff00902b-9858-4bee-ab95-d3406018c688
66
ms.topic: article
7-
ms.date: 05/08/2023
7+
ms.date: 08/29/2023
88
ms.author: msangapu
99
author: msangapu-msft
1010
ms.custom: seodec18, devx-track-azurecli, devx-track-azurepowershell
@@ -13,19 +13,19 @@ ms.custom: seodec18, devx-track-azurecli, devx-track-azurepowershell
1313

1414
# Configure Premium V3 tier for Azure App Service
1515

16-
The new Premium V3 pricing tier gives you faster processors, SSD storage, and quadruple the memory-to-core ratio of the existing pricing tiers (double the Premium V2 tier). With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
16+
The new Premium V3 pricing tier gives you faster processors, SSD storage, memory-optimized options, and quadruple the memory-to-core ratio of the existing pricing tiers (double the Premium V2 tier). With the performance advantage, you could save money by running your apps on fewer instances. In this article, you learn how to create an app in Premium V3 tier or scale up an app to Premium V3 tier.
1717

1818
## Prerequisites
1919

20-
To scale-up an app to Premium V3, you need to have an Azure App Service app that runs in a pricing tier lower than Premium V3, and the app must be running in an App Service deployment that supports Premium V3.
20+
To scale-up an app to Premium V3, you need to have an Azure App Service app that runs in a pricing tier lower than Premium V3, and the app must be running in an App Service deployment that supports Premium V3. Additionally the App Service deployment must support the desired SKU within Premium V3.
2121

2222
<a name="availability"></a>
2323

2424
## Premium V3 availability
2525

2626
The Premium V3 tier is available for both native and custom containers, including both Windows containers and Linux containers.
2727

28-
Premium V3 is available in some Azure regions and availability in additional regions is being added continually. To see if it's available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md):
28+
Premium V3 as well as specific Premium V3 SKUs are available in some Azure regions and availability in additional regions is being added continually. To see if a specific PremiumV3 offering is available in your region, run the following Azure CLI command in the [Azure Cloud Shell](../cloud-shell/overview.md) (substitute _P1v3_ with the desired SKU):
2929

3030
```azurecli-interactive
3131
az appservice list-locations --sku P1V3
@@ -44,11 +44,12 @@ To see all the Premium V3 options, select **Explore pricing plans**, then select
4444
:::image type="content" source="media/app-service-configure-premium-tier/explore-pricing-plans.png" alt-text="Screenshot showing the Explore pricing plans page with a Premium V3 plan selected.":::
4545

4646
> [!IMPORTANT]
47-
> If you don't see a Premium V3 plan as an option, or if the options are greyed out, then Premium V3 likely isn't available in the underlying App Service deployment that contains the App Service plan. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
47+
> If you don't see **P0V3**, **P1V3**, **P2V3**, **P3V3**, **P1mV3**, **P2mV3**, **P3mV3**, **P4mV3**, and **P5mV3** as options, or if some options are greyed out, then either **Premium V3** or an individual SKU within **Premium V3** isn't available in the underlying App Service deployment that contains the App Service plan. See [Scale up from an unsupported resource group and region combination](#unsupported) for more details.
48+
>
4849
4950
## Scale up an existing app to Premium V3 tier
5051

51-
Before scaling an existing app to Premium V3 tier, make sure that Premium V3 is available. For information, see [Premium V3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
52+
Before scaling an existing app to Premium V3 tier, make sure that both Premium V3 as well as the specific SKU within Premium V3 are available. For information, see [PremiumV3 availability](#availability). If it's not available, see [Scale up from an unsupported resource group and region combination](#unsupported).
5253

5354
Depending on your hosting environment, scaling up may require extra steps.
5455

@@ -74,10 +75,9 @@ Some App Service plans can't scale up to the Premium V3 tier, or to a newer SKU
7475

7576
## Scale up from an unsupported resource group and region combination
7677

77-
If your app runs in an App Service deployment where Premium V3 isn't available, or if your app runs in a region that currently does not support Premium V3, you need to re-deploy your app to take advantage of Premium V3. You have two options:
78+
If your app runs in an App Service deployment where Premium V3 isn't available, or if your app runs in a region that currently does not support Premium V3, you need to re-deploy your app to take advantage of Premium V3. Alternatively newer Premium V3 SKUs may not be available, in which case you also need to re-deploy your app to take advantage of newer SKUs within Premium V3. You have two options:
7879

79-
- Create an app in a new resource group and with a new App Service plan. When creating the App Service plan, select a Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the App Service plan down to a lower tier to save costs, you can always scale back up to Premium V3 because the deployment unit supports it.
80-
- 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 into a new resource group on a new app service plan that uses Premium V3.
80+
- Create an app in a new resource group and with a new App Service plan. When creating the App Service plan, select the desired Premium V3 tier. This step ensures that the App Service plan is deployed into a deployment unit that supports Premium V3 as well as the specific SKU within Premium V3. Then, redeploy your application code into the newly created app. Even if you scale the new App Service plan down to a lower tier to save costs, you can always scale back up to Premium V3 and the desired SKU within Premium V3 because the deployment unit supports it.
8181

8282
![Screenshot showing how to clone your app.](media/app-service-configure-premium-tier/clone-app.png)
8383

0 commit comments

Comments
 (0)