Skip to content

Commit cb39ac8

Browse files
Update overview-hosting-plans.md
1 parent 80f8d5d commit cb39ac8

File tree

1 file changed

+3
-16
lines changed

1 file changed

+3
-16
lines changed

articles/app-service/overview-hosting-plans.md

Lines changed: 3 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how App Service plans work in Azure App Service, how they're
44
keywords: app service, azure app service, scale, scalable, scalability, app service plan, app service cost
55
ms.assetid: dea3f41e-cf35-481b-a6bc-33d7fc9d01b1
66
ms.topic: article
7-
ms.date: 08/21/2024
7+
ms.date: 02/28/2025
88
ms.author: msangapu
99
author: msangapu-msft
1010
ms.custom: UpdateFrequency3
@@ -105,24 +105,11 @@ If your app is in the same App Service plan with other apps, you may want to imp
105105

106106
## Should I put an app in a new plan or an existing plan?
107107

108-
Since you pay for the computing resources your App Service plan allocates (see [How much does my App Service plan cost?](#cost)), you can potentially save money by putting multiple apps into one App Service plan. You can continue to add apps to an existing plan as long as the plan has enough resources to handle the load. However, keep in mind that apps in the same App Service plan all share the same compute resources. To determine whether the new app has the necessary resources, you need to understand the capacity of the existing App Service plan, and the expected load for the new app. Overloading an App Service plan can potentially cause downtime for your new and existing apps.
108+
Since you pay for the computing resources your App Service plan allocates (see [How much does my App Service plan cost?](#cost)), you can potentially save money by putting multiple apps into one App Service plan. You can continue to add apps to an existing plan as long as the plan has enough resources to handle the load. However, keep in mind that apps in the same App Service plan all share the same compute resources. To determine whether the new app has the necessary resources, you need to understand the capacity of the existing App Service plan, and the expected load for the new app. Overloading an App Service plan can potentially cause downtime for your new and existing apps. You can find more comparisons between plans at [App Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-app-service-limits).
109109

110110
Isolate your app into a new App Service plan when:
111111

112-
- The app is resource-intensive. The number may actually be lower depending on how resource intensive the hosted applications are. However, for general guidance, refer to the table below:
113-
114-
| App Service Plan SKU | Maximum Apps |
115-
|--|--|
116-
| B1, S1, P1v2, I1v1 | 8 |
117-
| B2, S2, P2v2, I2v1 | 16 |
118-
| B3, S3, P3v2, I3v1 | 32 |
119-
| P0v3 | 8 |
120-
| P1v3, I1v2 | 16 |
121-
| P2v3, I2v2, P1mv3 | 32 |
122-
| P3v3, I3v2, P2mv3 | 64 |
123-
| I4v2, I5v2, I6v2 | Maximum density bound by vCPU usage |
124-
| P3mv3, P4mv3, P5mv3 | Maximum density bound by vCPU usage |
125-
112+
- The app is resource-intensive.
126113
- You want to scale the app independently from the other apps in the existing plan.
127114
- The app needs resources in a different geographical region.
128115

0 commit comments

Comments
 (0)