Skip to content

Commit 38dc50b

Browse files
Typo
Typo
1 parent 9abd4df commit 38dc50b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/configuration-infrastructure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ For example, here's how to calculate the available addressing for a subnet with
4343
Subnet Size /24 = 255 IP addresses - 5 reserved from the platform = 250 available addresses.
4444
250 - Gateway 1 (10) - 1 private frontend IP configuration = 239
4545
239 - Gateway 2 (2) = 237
46-
237 - Gateway 3 (15) - 1 private frontend IP configuration = 223
46+
237 - Gateway 3 (15) - 1 private frontend IP configuration = 221
4747

4848
> [!IMPORTANT]
4949
> Although a /24 subnet is not required per Application Gateway v2 SKU deployment, it is highly recommended. This is to ensure that Application Gateway v2 has sufficient space for autoscaling expansion and maintenance upgrades. You should ensure that the Application Gateway v2 subnet has sufficient address space to accommodate the number of instances required to serve your maximum expected traffic. If you specify the maximum instance count, then the subnet should have capacity for at least that many addresses. For capacity planning around instance count, see [instance count details](understanding-pricing.md#instance-count).

0 commit comments

Comments
 (0)