Skip to content

Commit 206a9cc

Browse files
Merge pull request #214771 from JackStromberg/patch-84
Limit change
2 parents dbe52ea + 1fb181d commit 206a9cc

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

includes/application-gateway-limits.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ ms.author: victorh
88
| Resource | Limit | Note |
99
| --- | --- | --- |
1010
| Azure Application Gateway |1,000 per subscription | |
11-
| Front-end IP configurations |2 |1 public and 1 private |
12-
| Front-end ports |100<sup>1</sup> | |
13-
| Back-end address pools |100 | |
14-
| Back-end servers per pool |1,200 | |
11+
| Frontend IP configurations |2 |1 public and 1 private |
12+
| Frontend ports |100<sup>1</sup> | |
13+
| Backend address pools |100 | |
14+
| Backend targets per pool |1,200 | |
1515
| HTTP listeners |200<sup>1</sup> |Limited to 100 active listeners that are routing traffic. Active listeners = total number of listeners - listeners not active.<br>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. See [Frequently asked questions about Application Gateway](../articles/application-gateway/application-gateway-faq.yml#what-is-considered-an-active-listener-versus-inactive-listener) for additional details.|
1616
| HTTP load-balancing rules |400<sup>1</sup> | |
17-
| Back-end HTTP settings |100<sup>1</sup> | |
17+
| Backend HTTP settings |100<sup>1</sup> | |
1818
| Instances per gateway |V1 SKU - 32<br>V2 SKU - 125 | |
1919
| SSL certificates |100<sup>1</sup> |1 per HTTP listener |
2020
| Maximum SSL certificate size |V1 SKU - 10 KB<br>V2 SKU - 16 KB| |

0 commit comments

Comments
 (0)