Properly set base policy id in azure firewall policy via pipe

[bewatersmsft]

Description

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.

[Copilot]

Pull Request Overview

This PR fixes an issue where the base policy ID is incorrectly set when updating an Azure Firewall Policy using pipeline input. The fix extracts base policy information consistently whether the cmdlet receives input via parameter or pipeline.

Key Changes:

• Added a new ExtractBasePolicy() helper method to properly handle base policy ID extraction from both parameter and pipeline input scenarios
• Removed inline base policy handling logic that was causing the issue with piped input

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
SetAzureFirewallPolicyCommand.cs	Added ExtractBasePolicy() method to properly handle base policy ID extraction; replaced inline base policy handling with method call
AzureFirewallPolicyTests.ps1	Added test function to verify base policy is correctly preserved when updating policies via pipeline
AzureFirewallPolicyTests.cs	Added test method wrapper to run the new PowerShell test scenario

[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).