Skip to content

Commit cc5bada

Browse files
Grammar
Grammar
1 parent a042cb7 commit cc5bada

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/application-gateway/configuration-infrastructure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ Application Gateway (Standard or WAF) SKU can support up to 32 instances (32 ins
3232

3333
Application Gateway (Standard_v2 or WAF_v2 SKU) can support up to 125 instances (125 instance IP addresses + 1 private frontend IP configuration + 5 Azure reserved). A minimum subnet size of /24 is recommended.
3434

35-
To determine the available capacity of a subnet that has existing Application Gateways provisioned, take the size of the subnet and subtract the five reserved IP addresses of the subnet reserved by the platform.  Next, take each gateway and subtract the the max-instance count.  For each gateway that has a private IP, subtract one additional IP address per gateway as well.
35+
To determine the available capacity of a subnet that has existing Application Gateways provisioned, take the size of the subnet and subtract the five reserved IP addresses of the subnet reserved by the platform.  Next, take each gateway and subtract the the max-instance count.  For each gateway that has a private frontend IP configuration, subtract one additional IP address per gateway as well.
3636

37-
For example, here's how to calculate the available addressing for a subnet with three gateways with varying sizes:
37+
For example, here's how to calculate the available addressing for a subnet with three gateways of varying sizes:
3838
- Gateway 1: Maximum of 10 instances; utilizes a private frontend IP configuration
3939
- Gateway 2: Maximum of 2 instances; no private frontend IP configuration
4040
- Gateway 3: Maximum of 15 instances; utilizes a private frontend IP configuration

0 commit comments

Comments
 (0)