Application Gateway v2 limits

[konopkap]

Hello,

I'd like to ask about AppGW limits. Currently we're using AppGW in WAFv2 tier. According to the docs there should be a limit to 40 backend pools.

Back-end address pools | 100¹ 1 In case of WAF-enabled SKUs, you must limit the number of resources to 40.

In our AppGW we have ~60 backend pools. Shouldn't it be limited to 40 (as we use WAF-enabled SKU tier)? If not then how the limit table should be read?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 36f49a06-90b1-cbe1-3853-2c38277b79f8
• Version Independent ID: 02ff6f6c-3ef6-b48f-060d-b290419e0aba
• Content: Azure subscription limits and quotas - Azure Resource Manager
• Content Source: articles/azure-resource-manager/management/azure-subscription-service-limits.md
• Service: azure-resource-manager
• Sub-service: management
• GitHub Login: @tfitzmac
• Microsoft Alias: tomfitz

[SwathiDhanwada-MSFT]

@konopkap Thanks for your comment. We will review the issue and get back to you shortly.

[SwathiDhanwada-MSFT]

@konopkap Please note that the guideline is recommendation based on best practices. All instances of AppGW are configured in active-active setup and must share the same configuration. This means that WAF engine has to be loaded on each instance for each listener. An instance of Application Gateway can host up to 40 websites and protect these web applications at the same time with web application firewall. To know more, kindly refer this document.

As you are using more than 40 websites , I would recommend to monitors all threat alerts and check if web application firewall auditing all the incoming requests.

As there are no further documentation changes, we will close the issue for now. If there are further questions , please revert and we will be glad to assist you.