Skip to content

Commit 41a60d7

Browse files
committed
Update IP use description
1 parent e65c940 commit 41a60d7

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

articles/app-service/environment/networking.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,20 +25,22 @@ The size of the subnet can affect the scaling limits of the App Service plan ins
2525
>
2626
> Sample calculation:
2727
>
28-
> For each App Service plan instance, you need:
29-
> 5 Windows Container apps = 5 IP addresses
30-
> 1 IP address per App Service plan instance
28+
> For each App Service plan instance, you need:
29+
> 5 Windows Container apps = 5 IP addresses
30+
> 1 IP address per App Service plan instance
3131
> 5 + 1 = 6 IP addresses
3232
>
33-
> For 25 instances:
33+
> For 25 instances:
3434
> 6 x 25 = 150 IP addresses per App Service plan
3535
>
3636
> Since you have 2 App Service plans, 2 x 150 = 300 IP addresses.
3737
3838
If you use a smaller subnet, be aware of the following limitations:
3939

40-
- Any particular subnet has five addresses reserved for management purposes. In addition to the management addresses, App Service Environment dynamically scales the supporting infrastructure, and uses between 4 and 27 addresses, depending on the configuration and load. You can use the remaining addresses for instances in the App Service plan. The minimal size of your subnet is a `/27` address space (32 addresses).
41-
40+
- Any particular subnet has five addresses reserved for management purposes. In addition to the management addresses, App Service Environment dynamically scales the supporting infrastructure, and uses between 7 and 27 addresses, depending on the configuration and load. You can use the remaining addresses for instances in the App Service plan. The minimal size of your subnet is a `/27` address space (32 addresses).
41+
- For any App Service plan OS/SKU combination used in your App Service Environment like I1v2 Windows, one standby instance is created for every 20 active instances. The standby instances will also require IP addresses.
42+
- When scaling App Service plans in the App Service Environment up/down, the amount of IP addresses used by the App Service plan is temporarily doubled while the scale operation completes. The new instances need to be fully operational before the existing instances are deprovisioned.
43+
- Platform upgrades need free IP addresses to ensure upgrades can happen without interruptions to outbound traffic. Finally, after scale up, down, or in operations complete, there might be a short period of time before IP addresses are released.
4244
- If you run out of addresses within your subnet, you can be restricted from scaling out your App Service plans in the App Service Environment. Another possibility is that you can experience increased latency during intensive traffic load, if Microsoft isn't able to scale the supporting infrastructure.
4345

4446
## Addresses

0 commit comments

Comments
 (0)