Update WAF rules and support information

[BrandynR-MSFT]

Aligning FAQ documentation with CRS/DRS Ruleset that outlines that CRS 3.0 is no longer supported; DRS2.1 and CRS3.2 are recommended as the latest available versions, with all available features

[prmerger-automator]

@BrandynR-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[prmerger-automator]

@BrandynR-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit afc5147:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/web-application-firewall/ag/application-gateway-waf-faq.yml	⚠️Warning		Details

articles/web-application-firewall/ag/application-gateway-waf-faq.yml

• Line 47, Column 61: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#drs-21' in 'articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md', did you mean '#drs21'?

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[Copilot]

Pull Request Overview

Updates the Web Application Firewall (WAF) FAQ documentation to reflect current support for rule sets. The update removes CRS 3.0 from supported versions and adds DRS 2.1 as a recommended option.

• Removes CRS 3.0 from the list of currently supported rule sets
• Adds DRS 2.1 as a supported rule set option
• Updates deprecation notice to include CRS 3.0 alongside CRS 2.2.9

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[v-dirichards]

@halkazwini

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[halkazwini]

Thank you for your contribution, @BrandynR-MSFT!
Please commit these two small changes.

[v-dirichards]

@BrandynR-MSFT - Can you respond to the requested changes or let us know if you would like us to commit them?

• Update WAF rules and support information #127733 (comment)
• Update WAF rules and support information #127733 (comment)

---

@halkazwini - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[BrandynR-MSFT]

Accepted changes

[learn-build-service-prod]

Learn Build status updates of commit 5182617:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/web-application-firewall/ag/application-gateway-waf-faq.yml	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[learn-build-service-prod]

Learn Build status updates of commit 953ad99:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/web-application-firewall/ag/application-gateway-waf-faq.yml	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[halkazwini]

#sign-off