1.3.0

What's new

• Support Microsoft Default Rule Set 2.0 source policies using verified native defaults, membership, descriptions, and paranoia levels. Generated DRS targets remain 2.1/2.2; DRS 1.2 is not supported.
• Preserve compatible source managed-rule behavior automatically and report unsupported carryover without remapping rule IDs. Custom-rule merging remains unchanged.
• Compare header/cookie exclusions case-insensitively and query/body argument selectors case-sensitively, preserving original selector spelling.
• Show source, master, and selected custom-rule priorities separately. Detect collisions against the selected merge, including future source selections.
• Resolve priority conflicts with one comparison warning, a clear resolution panel, an available-priority suggestion, explicit Enter confirmation, and actionable invalid-input/cancellation handling.
• Announce startup phases and show compatibility-check progress.
• Remove unused review/report scaffolding and align documentation. Only Templates/mastertemplate.json is tracked; local template/test JSON is ignored.

Command-line interface

Use SourcePolicy and MasterPolicy for either JSON files or live Azure policy resource IDs. Obsolete selection options and old source/master parameter names and aliases have been removed; update existing commands to use the canonical names.

Validation

All four maintained PowerShell regression suites pass. Actual-policy generation was verified with 28 custom rules, unique priorities, exactly two prompts, and one warning per conflicting row. Input JSON remains unchanged, and the script does not deploy or modify Azure resources.

Pull request

• #4

1.2.0

Highlights

• Added automatic WAF migration with -Auto: choose source for review decisions while retaining target-only custom rules.
• Support -Auto -ReportOnly previews; prevent combining automatic mode with manual source/target selections.
• Preserve interactive resolution of custom-rule priority conflicts.
• Added a Terraform-based DRS 2.2 master template.
• Simplified script help, README, and maintained test scaffolding.

Validation

All four maintained PowerShell regression suites passed. The customer report-only scenario resolved 120 decisions with no pending choices and did not create an output file.

Full changes: 1.1.0...1.2.0

1.1.0

Capabilities

• Azure Front Door WAF request exceptions (Preview): URI, IP/CIDR and header predicates; complete DRS, Bot Manager and HTTP DDoS scopes; independent KeepSource/KeepTarget choices; compatibility and quota validation.
• Live Azure resource IDs or JSON snapshots for source and master policies, with explicit context/subscription checks and input/output protection.
• Effective, version-aware policy comparisons with labeled tags, consistent absence markers and compatibility warnings beside their rows.
• A self-contained migration script with embedded catalogs and no companion-file requirements.

Requirements and usage

Download the attached New-WafMigrationTemplate.ps1 or the source archive, and follow README for parameters and deployment guidance. PowerShell 7 and Az.Accounts are required. Live policy inputs require an authenticated Az context.

Request exceptions require DRS 2.1 or 2.2. Verify aggregate exception quotas across associated policies through Azure deployment validation. The script generates ARM templates; it does not deploy policies or change Front Door associations.

1.0.0

Initial release of the WAF migration tooling.