Getting "ApplicationGatewayFirewallNoRedisCacheRateLimitUnsupported" when I deploy. Which regions actually support this feature?

Question

Getting "ApplicationGatewayFirewallNoRedisCacheRateLimitUnsupported" when I deploy. Which regions actually support this feature?

Kristian K. Riisgaard 20

The organization where I work are attempting to diversify from North and West Europe.

When attempting to deploy to Denmark East as a test, I'm getting the error "ApplicationGatewayFirewallNoRedisCacheRateLimitUnsupported", from which I understand that unlike in the previous regions, there is an unsupported feature, which I assume relates to WAF rules.

Which regions have the support I'm looking for? And what documentation (if any) did I miss, because I spent hours searching for either a list or a command that would allow me to determine whether it is supported.

Mythreya Asnala 0 Reputation points Microsoft External Staff Moderator

2026-07-16T12:35:17.7966667+00:00
Hey Kristian,

The error strongly suggests you’re hitting a region enablement gap for a specific WAF “exception” capability, rather than a general WAF support issue.

What that error usually means

In App Gateway WAF policy deployments, “exceptions” (as in the exception feature) appears to be treated as a Preview/feature-gated capability. In a Microsoft Q&A thread, deployments failed with:

“Region is not enabled for Exception feature”

and the accepted guidance noted that it didn’t look like anything you could “turn on” yourself, and that exceptions and exclusions are different. The key takeaway was: if the region isn’t enabled for that preview feature, deployments fail.

So, for your question (“which regions support this?”): the provided documentation does not include a public list of regions that have this specific App Gateway WAF Exception feature enabled.

Based on the relevant docs provided, we can’t determine a definitive region list. The docs only indicate that:

the feature seems preview / not broadly documented

regions may or may not be enabled

you may need to use a region where the capability is enabled

could you please check the below details

Confirm you’re using “exceptions” not “exclusions”

The Q&A explicitly warns that exceptions and exclusions are totally different.

If your intent was exclusions, the policy/template needs to match that different concept.

Check whether your target region supports the preview capability

There’s no list in the provided materials, but the error is essentially telling you the region isn’t enabled for that feature.

Look for Microsoft announcements

The provided materials don’t specify where the “Exception feature” region rollout is published, but in general the Q&A suggests feature enablement isn’t always discoverable via standard docs.

References

Microsoft Q&A: My app gateway web application firewall policy deployment fails with this message "Region is not enabled for Exception feature". How do I enable the feature? https://learn.microsoft.com/answers/a/1896900?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider

(Context on WAF platform comparison / capabilities) *Web Application Firewall for Azure networks (cross-cloud)
*https://learn.microsoft.com/en-us/azure/networking/design-guide/web-application-firewall?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider&pivots=lift-shift#azure-waf-platform-comparison

Resolve AzureFirewallPremiumUnsupportedRegion (included in the provided docs, but not directly relevant to your App Gateway WAF exception error) https://learn.microsoft.com/troubleshoot/azure/firewall/firewall-known-issues?wt.mc_id=knowledgesearch_inproduct_azure-cxp-community-insider#current-capacity-constraints

Answer accepted by question author

0 additional answers

Your answer

Answer 1

That error is about a RateLimitRule, not WAF exceptions. Application Gateway WAF rate limiting uses a platform-managed counter service, and this message means the required backend is not enabled in Denmark East. It does not mean Application Gateway or WAF_v2 is generally unavailable there.

Microsoft's public rate-limiting guidance lists the prerequisites: Application Gateway WAF_v2, the latest WAF engine with CRS 3.2, and a non-air-gapped cloud. It does not currently provide a per-region matrix for the rate-limit backend. The provider-location output from Azure CLI only shows where the WAF policy resource type exists; it cannot expose enablement of this subfeature, so there is no reliable discovery command for it.

To isolate the issue, deploy the same Denmark East policy after temporarily removing only the RateLimitRule, or change it to a MatchRule. If that succeeds, the regional rate-limit dependency is the blocker. Also keep the WAF policy and Application Gateway in the same region and subscription; a policy left in North Europe cannot be associated with a Denmark East gateway.

For a production choice, open an Azure support request under Application Gateway/WAF and ask Microsoft.Network to confirm current rate-limit enablement for your candidate regions. Until they confirm one, keep this control in North/West Europe or enforce rate limiting at Front Door, API Management, or the application layer for Denmark East.

Kristian K. Riisgaard 20 Reputation points

2026-07-16T14:55:26.2366667+00:00

Thank you for pointing out where the problem was. I'd misunderstood a few things, so no wonder I had a hard time finding anything.

I tried removing all custom rules for Denmark East, and it worked like a charm. I'll go with your suggestion on opening a support request too, so we can do full deployments to Denmark East.

Getting "ApplicationGatewayFirewallNoRedisCacheRateLimitUnsupported" when I deploy. Which regions actually support this feature?

What that error usually means

could you please check the below details

References

0 additional answers

Your answer