Powershell changes for IpVersionType property for Private Endpoint Creation #29004
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds a new IpVersionType parameter to the New-AzPrivateEndpoint cmdlet, enabling users to specify the IP version type (IPv4, IPv6, or DualStack) for private IPs of a private endpoint.
Key Changes
- Added IpVersionType parameter with ValidateSet attribute accepting "IPv4", "IPv6", and "DualStack" values
- Updated PowerShell cmdlet model and help documentation
- Added changelog entry documenting the new functionality
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/Network/Network/PrivateEndpoint/NewAzurePrivateEndpointCommand.cs | Adds the new IpVersionType parameter with validation and assigns it to the private endpoint model when provided |
| src/Network/Network/Models/PSPrivateEndpoint.cs | Adds IpVersionType property to the private endpoint model class for mapping to Azure SDK |
| src/Network/Network/help/New-AzPrivateEndpoint.md | Documents the new -IpVersionType parameter with description, type, and allowed values |
| src/Network/Network/ChangeLog.md | Adds user-facing release note describing the new parameter functionality |
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
bzpiyush
changed the title
SatyamurtiDoddini
approved these changes
Dec 22, 2025
wyunchi-ms
approved these changes
Dec 23, 2025
wyunchi-ms
merged commit 747be9c
into
Azure:release-network-2025-05-01
12 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.