Skip to content

Commit 741b75c

Browse files
authored
Merge pull request #121323 from azarboon/patch-2
Update manage-scale-up.md
2 parents f24a49c + 7582051 commit 741b75c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/app-service/manage-scale-up.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This article shows you how to scale your app in Azure App Service. There are two
1515
like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more. You scale up by changing the pricing tier of the
1616
App Service plan that your app belongs to.
1717
* [Scale out](https://en.wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling): Increase the number of VM instances that run your app.
18-
You can scale out to as many as 30 instances, depending on your pricing tier. [App Service Environments](environment/intro.md)
18+
Basic, Standard and Premium service plans scale out to as many as 3, 10 and 30 instances respectively. [App Service Environments](environment/intro.md)
1919
in **Isolated** tier further increases your scale-out count to 100 instances. For more information about scaling out, see
2020
[Scale instance count manually or automatically](../azure-monitor/autoscale/autoscale-get-started.md). There, you find out how
2121
to use autoscaling, which is to scale instance count automatically based on predefined rules and schedules.

0 commit comments

Comments
 (0)