Requesting Clarification of WAF v2 SKU Resource Limits

Question

Are all denoted limits hard-capped at 40 as the first footnote describes? For example, with Standard v2, the listener limits are 200 total, 100 active, both with a superscript "1" indicating that they would both be reduced to 40. I'm looking to confirm that this is indeed the case, and that's not something else like 40 active, but some number north of that in total. In the standard SKU, I can theoretically configure 100 listeners and a corresponding https redirect. When using a WAF SKU, taking the footnote and notations at face value, it would seem to do the same would reduce me to 20 listeners if I wanted a corresponding https redirect for each. That seems like a drastic capacity hit.

For reference, the limits are outlined here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#application-gateway-limits

Answer 1

@Adrian Lane Thank you for contacting Azure Support. With Standard V2 the limit is 100 active. With WAF V2 it is 40 active. Active listeners are ones with a backend pool and not just plain redirects. therefore, HTTPS redirect listeners do not count and the limit remains 40 with those redirects. Hope this helps!

Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.