Skip to content

Commit 4f38890

Browse files
authored
Merge pull request #159724 from MicrosoftDocs/master
Update for Build //2021 430444
2 parents 2ab484c + 94e4fde commit 4f38890

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/application-gateway/configuration-infrastructure.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,10 @@ Consider a subnet that has 27 application gateway instances and an IP address fo
3030

3131
Application Gateway (Standard or WAF) SKU can support up to 32 instances (32 instance IP addresses + 1 private front-end IP + 5 Azure reserved) – so a minimum subnet size of /26 is recommended
3232

33-
Application Gateway (Standard_v2 or WAF_v2 SKU) can support up to 125 instances (125 instance IP addresses + 1 private front-end IP + 5 Azure reserved) – so a minimum subnet size of /24 is recommended
33+
Application Gateway (Standard_v2 or WAF_v2 SKU) can support up to 125 instances (125 instance IP addresses + 1 private front-end IP + 5 Azure reserved) – so a minimum subnet size of /24 is required.
34+
35+
> [!IMPORTANT]
36+
> Starting mid-late May 2021, a minimum subnet size of /24 (256 IPs) per Application Gateway v2 SKU (Standard_v2 or WAF_v2) will be required for new deployments. Existing deployments will not be affected by this requirement but are encouraged to move to a subnet with at least 256 IPs per v2 gateway. This requirement will ensure the subnet has sufficient IP addresses for the gateway to undergo maintenance updates without impact on available capacity.
3437
3538
## Network security groups
3639

0 commit comments

Comments
 (0)