Skip to content

Commit ea9d6cb

Browse files
Merge pull request #302377 from msangapu-msft/patch-5
Update overview-hosting-plans.md
2 parents 7ff6956 + b6a1b36 commit ea9d6cb

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,7 @@ In other tiers, an app runs and scales as follows:
7575
- If multiple apps are in the same App Service plan, they all share the same VM instances.
7676
- If you have multiple deployment slots for an app, all deployment slots also run on the same VM instances.
7777
- If you enable diagnostic logs, perform backups, or run [WebJobs](webjobs-create.md), they also use CPU cycles and memory on these VM instances.
78-
79-
In this way, the App Service plan is the scale unit of the App Service apps. If the plan is configured to run five VM instances, then all apps in the plan run on all five instances. If the plan is configured for autoscaling, then all apps in the plan are scaled out together, based on the autoscale settings.
78+
- All apps in an App Service plan scale together, because they share the same underlying compute resources (VM instances). Scaling the plan — whether manually or through autoscale rules — affects all apps in the plan.
8079

8180
For more information on scaling out an app, see [Get started with autoscale in Azure](/azure/azure-monitor/autoscale/autoscale-get-started).
8281

0 commit comments

Comments
 (0)