Remove ShouldProcess Parameter from Azure Firewall related Resources

[bewatersmsft]

Description

Multiple customers have complained of applying test changes to production workloads due to the What-If parameter being passed which comes from ShouldProcess. After reviewing the code, it is apparent there is no support for ShouldProcess and should be removed.

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull Request Overview

This PR disables incomplete SupportsShouldProcess functionality (which enables WhatIf/Confirm parameters) for four Network module cmdlets: Set-AzIpGroup, Set-AzFirewall, Set-AzFirewallPolicy, and Set-AzFirewallPolicyRuleCollectionGroup. The changes address issue #27667 by setting the SupportsShouldProcess attribute to false until proper implementation can be completed.

Key changes:

• Disabled SupportsShouldProcess attribute in four cmdlet classes
• Added TODO comments with issue reference to track future implementation
• Updated ChangeLog.md to document the removal

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/Network/Network/IpGroup/SetIpGroupCommand.cs	Disabled SupportsShouldProcess for Set-AzIpGroup cmdlet
src/Network/Network/AzureFirewall/SetAzureFirewallCommand.cs	Disabled SupportsShouldProcess for Set-AzFirewall cmdlet
src/Network/Network/AzureFirewallPolicy/SetAzureFirewallPolicyCommand.cs	Disabled SupportsShouldProcess for Set-AzFirewallPolicy cmdlet
src/Network/Network/AzureFirewallPolicy/RuleGroup/SetAzureFirewallPolicyRuleCollectionGroupCmdlet.cs	Disabled SupportsShouldProcess for Set-AzFirewallPolicyRuleCollectionGroup cmdlet
src/Network/Network/ChangeLog.md	Documented removal of SupportsShouldProcess from the four cmdlets

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[github-actions]

To the author of the pull request,
This PR was labeled "Contains Breaking Change" because breaking changes have been detected by the static analysis pipeline.

• According to our policy, breaking changes can only take place during major release and they must be preannounced.
• Please follow our guide on the detailed steps.
• Required: Please fill in the task below to facilitate our contact,you will receive notifications related to breaking changes.

[dolauli]

@bewatersmsft There are breaking changes detected that have not been preannounced. Either target the next breaking change window May 2026, or make sure the PR contains no breaking change.

Check the log of the static analysis pipeline for details.