Skip to content

Commit ec3a926

Browse files
Update waf-front-door-drs.md
1 parent ab4db20 commit ec3a926

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/web-application-firewall/afds/waf-front-door-drs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,10 @@ The version of the DRS that you use also determines which content types are supp
7070

7171
### Upgrading or changing ruleset version
7272

73-
When a ruleset version is changed in a WAF Policy, all the previous customizations from the existing managed rulesets such as rule state, rule actions and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules and policy settings will remain unaffected during the new ruleset assignment. You will need to redefine rule overrides and validate changes before deploying in a production environment.
73+
If you are upgrading, or assigning a new ruleset version, and would like to preserve existing rule overrides and exclusions, it is recommended to use PowerShell, CLI, REST API, or a templates to make ruleset version changes. A new version of a ruleset can have newer rules, additional rule groups, and may have updates to existing signatures to enforce better security and reduce false positives. It is recommended to validate changes in a test environment, fine tune if necessary, and then deploy in a production environment.
74+
75+
> [!NOTE]
76+
> If you are using the Azure portal to assign a new managed ruleset to a WAF policy, all the previous customizations from the existing managed ruleset such as rule state, rule actions, and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules, or policy settings will remain unaffected during the new ruleset assignment. You will need to redefine rule overrides and validate changes before deploying in a production environment.
7477
7578
### DRS 2.1
7679

0 commit comments

Comments
 (0)