Release network 2025 03 01

[kamboj-prjwl]

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 updates the Azure Network module's NetworkSecurityPerimeter.Autorest component, specifically targeting the 2025-03-01 API version release. The changes consist primarily of regenerated test recording files and test environment configuration updates.

Key Changes:

• API version update from 2025-01-01 to 2025-03-01 across all test recordings
• Test environment configuration refresh with new randomized resource names (from tklmb prefix to tgtdq prefix)
• Addition of a breaking change exception for the New-AzApplicationGatewayFirewallPolicyManagedRuleOverride cmdlet

Reviewed Changes

Copilot reviewed 73 out of 272 changed files in this pull request and generated no comments.

File	Description
tools/StaticAnalysis/Exceptions/Az.Network/BreakingChangeIssues.csv	Adds exception for 'Sensitivity' parameter validation set change in firewall policy cmdlet
src/Network/NetworkSecurityPerimeter.Autorest/test/localEnv.json	Updates test environment variables with new random string prefix and resource names
src/Network/NetworkSecurityPerimeter.Autorest/test/env.json	Updates test environment variables (identical changes to localEnv.json)
src/Network/NetworkSecurityPerimeter.Autorest/test/*.Recording.json (multiple files)	Regenerated test recordings with updated API version (2025-03-01), new resource names, timestamps, and correlation IDs

Files not reviewed (1)

• src/Network/Network/Properties/Resources.Designer.cs: Language not supported

[notyashhh]

Is this pr "DO NOT SQUASH"? @kamboj-prjwl

cc: @VeryEarly

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[kamboj-prjwl]

Is this pr "DO NOT SQUASH"? @kamboj-prjwl

cc: @VeryEarly

We can apply DO NOT SQAUSH as done for previous releases also. Ref: #28692, #28558

[github-actions]

‼️ Do NOT use squash to merge this pull request. All the commits must be merged to the target branch.
‼️ Enable "Allow merge commits" in the pull request settings. Select "Merge Commits" to merge the PR. Then go back to settings and disable the option.

[notyashhh]

@kamboj-prjwl / @baoqihuang0326 please resolve the conflicts

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

waiting