Skip to content

Latest commit

 

History

History
59 lines (56 loc) · 4.36 KB

application-gateway-limits.md

File metadata and controls

59 lines (56 loc) · 4.36 KB
author ms.service ms.topic ms.date ms.author
greg-lindsay
azure-application-gateway
include
06/19/2024
greglin
Resource Limit Note
Azure Application Gateway 1,000 per region per subscription
Frontend IP configurations 4 IPv4 - 1 public and 1 private.
IPv6 - 1 public and 1 private.
Frontend ports 1001
Backend address pools 100
Backend targets per pool 1,200
HTTP listeners 2001 Limited to 100 active listeners that are routing traffic. Active listeners = total number of listeners - listeners not active.
If a default configuration inside a routing rule is set to route traffic (for example, it has a listener, a backend pool, and HTTP settings) then that also counts as a listener. For more information, see Frequently asked questions about Application Gateway.
HTTP load-balancing rules 4001
Backend HTTP settings 1001
Instances per gateway V1 SKU - 32
V2 SKU - 125
SSL certificates 1001 1 per HTTP listener
Maximum SSL certificate size V1 SKU - 10 KB
V2 SKU - 16 KB
Maximum trusted client CA certificate size 25 KB 25 KB is the maximum aggregated size of root and intermediate certificates contained in an uploaded pem or cer file.
Maximum trusted client CA certificates 200 100 per SSL Profile
Authentication certificates 100
Trusted root certificates 100
Request timeout minimum 1 second
Request timeout maximum to private backend 24 hours
Request timeout maximum to external backend 4 minutes
Number of sites 1001 1 per HTTP listener
URL maps per listener 1
Host names per listener 5
Maximum path-based rules per URL map 100
Redirect configurations 1001
Number of rewrite rule sets 400
Number of Header or URL configuration per rewrite rule set 40
Number of conditions per rewrite rule set 40
Concurrent WebSocket connections Medium gateways 20k2
Large gateways 50k2
Maximum URL length 32 KB
Maximum header size 32 KB
Maximum header field size for HTTP/2 8 KB
Maximum header size for HTTP/2 16 KB
Maximum requests per HTTP/2 connection 1000 The total number of requests that can share the same frontend HTTP/2 connection
Maximum file upload size (Standard SKU) V1 - 2 GB
V2 - 4 GB
This maximum size limit is shared with the request body
Maximum file upload size (WAF SKU) V1 Medium - 100 MB
V1 Large - 500 MB
V2 - 750 MB
V2 (with CRS 3.2 or DRS) - 4 GB3
1 MB - Minimum Value
100 MB - Default value
V2 with CRS 3.2 or DRS - can be turned On/Off
Maximum request size limit Standard SKU (without files) V1 - 2 GB
V2 - 4 GB
Maximum request size limit WAF SKU (without files) V1 or V2 (with CRS 3.1 and older) - 128 KB
V2 (with CRS 3.2 or DRS) - 2 MB3
8 KB - Minimum Value
128 KB - Default value
V2 with CRS 3.2 or DRS - can be turned On/Off
Maximum request inspection limit WAF SKU V1 or V2 (with CRS 3.1 and older) - 128 KB
V2 (with CRS 3.2 or DRS) - 2 MB3
8 KB - Minimum Value
128 KB - Default value
V2 with CRS 3.2 or DRS - can be turned On/Off
Maximum Private Link Configurations 2 1 for public IP, 1 for private IP
Maximum Private Link IP Configurations 8
Maximum WAF custom rules per WAF policy 100
Maximum WAF match conditions per custom rule 10 This limit is not enforced by the WAF. Adding more than 10 match conditions can lead to performance degredation
WAF IP address ranges per match condition 540
600 - with CRS 3.2 or DRS
Maximum WAF exclusions per Application Gateway 40
200 - with CRS 3.2 or DRS
WAF string match values per match condition 10

1 The number of resources listed in the table applies to standard Application Gateway SKUs and WAF-enabled SKUs running CRS 3.2 or DRS. For WAF-enabled SKUs running CRS 3.1 or lower, the supported number is 40. For more information, see WAF engine.

2 Limit is per Application Gateway instance not per Application Gateway resource.

3 Must define the value via WAF Policy for Application Gateway.