Share via

WebApplicationFirewallPolicy validation failed. Subscriptions without DeveloperPreview flag enabled cannot use Microsoft_DefaultRuleSet_2.2

Justin M. Szwed 20 Reputation points
2025-12-04T03:47:01.5833333+00:00

Attempting to create or update WAF premium policy with DRS 2.2 and I get the error in title. I cannot find what feature to register either in the portal or in powershell/CLI - Nothing references DefaultRuleSet.

Azure Web Application Firewall
0 comments
Answer accepted by question author
  1. Hamzeh Al-Okeeli 75 Reputation points Microsoft Employee
    2025-12-11T07:39:04.2766667+00:00

    This is an internal issue. DRS 2.2 is intended to be generally available, but the platform is still enforcing a DeveloperPreview flag requirement. Since no public feature flag exists, CLI registration fails with "FeatureNotFound".

    Product team is actively working on a fix, which is expected to be rolled out around mid-January 2026 (possibly earlier).

    In the meantime, please continue using DRS 2.1.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ravi Varma Mudduluru 3,775 Reputation points Microsoft External Staff Moderator
    2025-12-04T04:16:39.8066667+00:00

    Hello @ Justin M. Szwed,

    Welcome to Microsoft Q&A Platform.

    Although Default Rule Set (DRS) 2.2 is intended to be generally available, the platform is still enforcing a Developer Preview feature flag (DeveloperPreviewFlag) for Microsoft_DefaultRuleSet_2.2. Since there is no publicly exposed feature flag to register (via Portal, PowerShell, or Azure CLI), any attempt to create or update a WAF Premium policy using DRS 2.2 fails with the following error:

    “Subscriptions without DeveloperPreviewFlag enabled cannot use Microsoft_DefaultRuleSet_2.2.”

    I also tested this behavior in my own environment and encountered the same error, which confirms that this is not a configuration issue on your side, but a platform-side bug/limitation.

    Current Status

    The product team is actively working on a fix

    • The fix is expected to be rolled out around mid-January 2026 (possibly earlier)

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.