Network OOB Release

[azure-powershell-bot]

Description

Network OOB Release

Checklist

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

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at 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. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• 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 Az.Network module and related tooling for the 7.17.0 release, adds new features to the changelog and release notes, and bumps pipeline NodeTool versions.

• Bumped Az.Network version to 7.17.0 across manifests and assembly info
• Added Version 7.17.0 entry in ChangeLog and expanded release notes in Az.Network.psd1
• Updated Publish-RMModules parameter sets and AutoRest NodeTool versionSpec in pipelines

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tools/ModulePublisher.psm1	Added CmdletBinding, new ParameterSet for ApiKey logic
tools/Docs/az-ps-latest-2.csv	Updated Az.Network docs package version to 7.17.0
tools/AzPreview/AzPreview.psd1	Bumped Az.Network RequiredVersion to 7.17.0
tools/Az/Az.psd1	Bumped Az.Network RequiredVersion to 7.17.0
src/Network/Network/Properties/AssemblyInfo.cs	Upgraded AssemblyVersion and AssemblyFileVersion
src/Network/Network/ChangeLog.md	Added “## Version 7.17.0” under Upcoming Release
src/Network/Network/Az.Network.psd1	Updated ModuleVersion, generated date, and release notes
NuGet.Config	Unintended trailing blank lines
.azure-pipelines/windows-powershell.yml	Upgraded NodeTool versionSpec
.azure-pipelines/powershell-core.yml	Upgraded NodeTool versionSpec
.azure-pipelines/azure-powershell-ci.yml	Upgraded NodeTool versionSpec

Comments suppressed due to low confidence (2)

src/Network/Network/Az.Network.psd1:64

• Commenting out the default ScriptsToProcess and TypesToProcess arrays may disable module initialization steps unexpectedly. Revert these to empty arrays or remove the lines if intentional, and add a comment explaining why they are disabled.

# ScriptsToProcess = @()

NuGet.Config:32

• Two trailing blank lines were added at the end of the file. These are unnecessary and can be removed to keep the file clean.

+

[Copilot]

The ApiKey parameter is assigned a new ParameterSet 'ByName' without corresponding sets defined on RepoName or Path, which may lead to ambiguous binding. Consider adding ParameterSetName attributes to related parameters (e.g. RepoName, Path) to fully define both 'ByName' and 'ByLocation' sets.

[Copilot]

[nitpick] The NodeTool versionSpec is duplicated across multiple pipeline files. Consider extracting it into a variable or template to simplify updates and ensure consistency.

Suggested change

	versionSpec: '18.20.8'
	versionSpec: ${{ variables.NodeToolVersion }}