Update Microsoft.Security/privateLinks to stable version

[amih90]

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 Microsoft.Security/privateLinks provider to use a stable API version instead of a preview version. The change promotes the service from preview status (2025-09-01-preview) to stable (2026-01-01) within the Private Link Common Cmdlets framework.

Key Changes:

• Updated Microsoft.Security/privateLinks API version from preview to stable
• Added changelog entry documenting the onboarding

Reviewed changes

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

File	Description
src/Network/Network/PrivateLinkService/PrivateLinkServiceProvider/ProviderConfiguration.cs	Updated API version from "2025-09-01-preview" to "2026-01-01" for Microsoft.Security/privateLinks configuration
src/Network/Network/ChangeLog.md	Added entry under "Upcoming Release" documenting the onboarding of Microsoft.Security/privateLinks to Private Link cmdlets

[Copilot]

The changelog entry does not explain what changed from the user's perspective. According to the custom guidelines for ChangeLog.md files, entries should be written for Azure PowerShell users and explain what changed and how it affects their usage. Consider revising to something like: "Updated Microsoft.Security/privateLinks to stable API version 2026-01-01 for Private Link cmdlets" to clarify that this is an API version update that affects stability/support.

[isra-fel]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).