Skip to content

Commit 1904586

Browse files
authored
Merge pull request #286414 from MicrosoftDocs/main
9/9/2024 PM Publish
2 parents cc08252 + b19054f commit 1904586

File tree

121 files changed

+439
-340
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

121 files changed

+439
-340
lines changed

articles/app-service/app-service-plan-manage.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Manage App Service plan
2+
title: Manage an App Service plan
33
description: Learn how to perform different tasks to manage an App Service plan, such as create, move, scale, and delete.
44
keywords: app service, azure app service, scale, app service plan, change, create, manage, management
55
ms.assetid: 4859d0d5-3e3c-40cc-96eb-f318b2c51a3d
6-
ms.topic: article
6+
ms.topic: how-to
77
ms.author: msangapu
88
author: msangapu-msft
9-
ms.date: 07/31/2023
9+
ms.date: 08/26/2024
1010
ms.custom: "UpdateFrequency3"
1111

1212
---
@@ -23,40 +23,40 @@ An [Azure App Service plan](overview-hosting-plans.md) provides the resources th
2323
2424
You can create an empty App Service plan, or you can create a plan as part of app creation.
2525

26-
1. To start creating an App Service Plan, browse to [https://ms.portal.azure.com/#create/Microsoft.AppServicePlanCreate](https://ms.portal.azure.com/#create/Microsoft.AppServicePlanCreate).
26+
1. To start creating an App Service plan, go to [Create App Service Plan](https://ms.portal.azure.com/#create/Microsoft.AppServicePlanCreate) on the Azure portal.
2727

28-
:::image type="content" source="./media/azure-web-sites-web-hosting-plans-in-depth-overview/create-appserviceplan.png" alt-text="Create an App Service Plan in the Azure portal.":::
28+
:::image type="content" source="./media/azure-web-sites-web-hosting-plans-in-depth-overview/create-appserviceplan.png" alt-text="Create an App Service plan in the Azure portal.":::
2929

3030
2. Configure the **Project Details** section before configuring the App Service plan.
3131

32-
3. In the **App Service Plan details** section, name the App Service Plan, then select the **Operating System** and **Region**. Region determines where your App Service plan is created.
32+
3. In the **App Service Plan details** section, name the App Service plan, and then select the **Operating System** and **Region**. The region specifies where your App Service plan is created.
3333

3434
4. When creating a plan, you can select the pricing tier of the new plan. In **Pricing Tier**, select a **Pricing plan** or select **Explore pricing plans** to view additional details.
3535

36-
5. In the **Zone redundancy** section, select whether the App Service Plan zone redundancy should be enabled or disabled.
36+
5. In the **Zone redundancy** section, select whether the App Service plan zone redundancy should be enabled or disabled.
3737

38-
6. Select **Review + create** to create the App Service Plan.
38+
6. Select **Review + create** to create the App Service plan.
3939

4040
> [!IMPORTANT]
41-
> When creating an new App Service Plan in an existing Resource Group, certain conditions with existing apps can trigger these errors:
41+
> When you create an new App Service plan in an existing resource group, certain conditions with existing apps can trigger these errors:
4242
> - `The pricing tier is not allowed in this resource group`
4343
> - `<SKU_NAME> workers are not available in resource group <RESOURCE_GROUP_NAME>`
4444
>
45-
> This can happen due to incompatibilities with pricing tiers, regions, operating systems, Availability Zones, existing Function apps, or existing web apps. If this error occurs, create your App Service Plan in a **new** Resource Group.
45+
> This can happen due to incompatibilities with pricing tiers, regions, operating systems, availability zones, existing function apps, or existing web apps. If one of these errors occurs, create your App Service plan in a **new** resource group.
4646
>
4747
4848

4949
<a name="move"></a>
5050

5151
## Move an app to another App Service plan
5252

53-
You can move an app to another App Service plan, as long as the source plan and the target plan are in the _same resource group, geographical region, and of the same OS type_. Any change in type such as Windows to Linux or any type that is different from the originating type is not supported.
53+
You can move an app to another App Service plan, as long as the source plan and the target plan are in the _same resource group and geographical region and of the same OS type_. Any change in type, such as Windows to Linux or any type that's different from the originating type, isn't supported.
5454

5555

5656
> [!NOTE]
57-
> Azure deploys each new App Service plan into a deployment unit, internally called a webspace. Each region can have many webspaces, but your app can only move between plans that are created in the same webspace. An App Service Environment can have multiple webspaces, but your app can only move between plans that are created in the same webspace.
57+
> Azure deploys each new App Service plan into a deployment unit, internally called a *webspace*. Each region can have many webspaces, but your app can only move between plans that are created in the same webspace. An App Service Environment can have multiple webspaces, but your app can only move between plans that are created in the same webspace.
5858
>
59-
> You can’t specify the webspace you want when creating a plan, but it’s possible to ensure that a plan is created in the same webspace as an existing plan. In brief, all plans created with the same resource group, region combination and operating system are deployed into the same webspace. For example, if you created a plan in resource group A and region B, then any plan you subsequently create in resource group A and region B is deployed into the same webspace. Note that plans can’t move webspaces after they’re created, so you can’t move a plan into “the same webspace” as another plan by moving it to another resource group.
59+
> You can’t specify the webspace you want when creating a plan, but it’s possible to ensure that a plan is created in the same webspace as an existing plan. In brief, all plans created with the same resource group, region combination, and operating system are deployed into the same webspace. For example, if you created a plan in resource group A and region B, then any plan you subsequently create in resource group A and region B is deployed into the same webspace. Note that plans can’t move webspaces after they’re created, so you can’t move a plan into “the same webspace” as another plan by moving it to another resource group.
6060
>
6161
6262
1. In the [Azure portal](https://portal.azure.com), search for and select **App services** and select the app that you want to move.
@@ -70,7 +70,7 @@ You can move an app to another App Service plan, as long as the source plan and
7070
4. If you create a plan, you can select the pricing tier of the new plan. In **Pricing Tier**, select the existing tier to change it.
7171

7272
> [!IMPORTANT]
73-
> If you're moving an app from a higher-tiered plan to a lower-tiered plan, such as from **D1** to **F1**, the app may lose certain capabilities in the target plan. For example, if your app uses TLS/SSL certificates, you might see this error message:
73+
> If you're moving an app from a higher-tiered plan to a lower-tiered plan, such as from **D1** to **F1**, the app might lose certain capabilities in the target plan. For example, if your app uses TLS/SSL certificates, you might see this error message:
7474
>
7575
> `Cannot update the site with hostname '<app_name>' because its current TLS/SSL configuration 'SNI based SSL enabled' is not allowed in the target compute mode. Allowed TLS/SSL configuration is 'Disabled'.`
7676
>
@@ -79,12 +79,12 @@ You can move an app to another App Service plan, as long as the source plan and
7979

8080
## Move an app to a different region
8181

82-
The region in which your app runs is the region of the App Service plan it's in. However, you cannot change an App Service plan's region. If you want to run your app in a different region, one alternative is app cloning. Cloning makes a copy of your app in a new or existing App Service plan in any region.
82+
The region in which your app runs is the region of the App Service plan it's in. However, you can't change an App Service plan's region. If you want to run your app in a different region, one alternative is app cloning. Cloning makes a copy of your app in a new or existing App Service plan in any region.
8383

8484
You can find **Clone App** in the **Development Tools** section of the menu.
8585

8686
> [!IMPORTANT]
87-
> Cloning has some limitations. You can read about them in [Azure App Service App cloning](app-service-web-app-cloning.md).
87+
> Cloning has some limitations. You can read about them in [Azure App Service App cloning](app-service-web-app-cloning.md#current-restrictions).
8888
8989
## Scale an App Service plan
9090

@@ -96,12 +96,12 @@ To scale out an app's instance count, see [Scale instance count manually or auto
9696

9797
## Delete an App Service plan
9898

99-
To avoid unexpected charges, when you delete the last app in an App Service plan, App Service also deletes the plan by default. If you choose to keep the plan instead, you should change the plan to **Free** tier so you're not charged.
99+
To avoid unexpected charges, when you delete the last app in an App Service plan, App Service also deletes the plan by default. If you choose to keep the plan instead, you should change the plan to the **Free** tier so you're not charged.
100100

101101
> [!IMPORTANT]
102102
> App Service plans that have no apps associated with them still incur charges because they continue to reserve the configured VM instances.
103103
104-
## Next steps
104+
## Next step
105105

106106
> [!div class="nextstepaction"]
107107
> [Scale up an app in Azure](manage-scale-up.md)

0 commit comments

Comments
 (0)