You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/networking.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,20 +25,22 @@ The size of the subnet can affect the scaling limits of the App Service plan ins
25
25
>
26
26
> Sample calculation:
27
27
>
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
31
31
> 5 + 1 = 6 IP addresses
32
32
>
33
-
> For 25 instances:
33
+
> For 25 instances:
34
34
> 6 x 25 = 150 IP addresses per App Service plan
35
35
>
36
36
> Since you have 2 App Service plans, 2 x 150 = 300 IP addresses.
37
37
38
38
If you use a smaller subnet, be aware of the following limitations:
39
39
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.
42
44
- 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.
0 commit comments