update and new properties for VNA and VNET#29243
Merged
VeryEarly merged 20 commits intoJul 21, 2026
Merged
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
…to arjun/vnra-vnet-ps-changes-2025-07-01
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
Hi @arjun-d-patel, the ChangeLog file path is src/Network/Network/ChangeLog.md. Please add a line right below |
Contributor
|
Hi @arjun-d-patel, please resolve the conflict of file src/Network/Network/ChangeLog.md. |
…to arjun/vnra-vnet-ps-changes-2025-07-01 # Conflicts: # src/Network/Network/ChangeLog.md
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
Hi @arjun-d-patel, please fix CI errors. |
…kingChange exceptions for BandwidthInGbps type change
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
Hi @arjun-d-patel, Please don't manually update files under src/Network/Network.Management.Sdk/Generated. |
… parameter to string type
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
Hi @arjun-d-patel, please don't manually update files under src/Network/Network.Management.Sdk/Generated. Or CI will fail. |
…changes-2025-07-01 # Conflicts: # src/Network/Network/ChangeLog.md # tools/StaticAnalysis/Exceptions/Az.Network/BreakingChangeIssues.csv
Co-authored-by: JunKai-v <v-juphang@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…changes-2025-07-01 # Conflicts: # src/Network/Network/ChangeLog.md
…to arjun/vnra-vnet-ps-changes-2025-07-01 # Conflicts: # src/Network/Network.Management.Sdk/Generated/Models/VirtualNetwork.cs # src/Network/Network.Management.Sdk/Generated/Models/VirtualNetworkAppliance.cs # src/Network/Network.Management.Sdk/Generated/Models/VirtualNetworkApplianceIpVersionType.cs # src/Network/Network.Management.Sdk/Generated/Models/VirtualNetworkPropertiesFormat.cs # src/Network/Network.Management.Sdk/Generated/ResourceNavigationLinksOperations.cs # src/Network/Network.Management.Sdk/Generated/ServiceAssociationLinksOperations.cs # src/Network/Network.Management.Sdk/Generated/SubnetsOperations.cs # src/Network/Network.Management.Sdk/Generated/VirtualNetworkAppliancesOperations.cs # src/Network/Network.Management.Sdk/Generated/VirtualNetworkPeeringsOperations.cs # src/Network/Network.Management.Sdk/Generated/VirtualNetworksOperations.cs # src/Network/Network.Management.Sdk/README.md # src/Network/Network/ChangeLog.md # src/Network/Network/VirtualNetworkAppliance/NewVirtualNetworkApplianceCommand.cs # src/Network/Network/help/New-AzVirtualNetwork.md # src/Network/Network/help/New-AzVirtualNetworkAppliance.md
Contributor
Author
Hi @YanaXu, yes, the auto generated files are reverted now. Can you review again? |
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
VeryEarly
requested changes
Jul 19, 2026
VeryEarly
left a comment
VeryEarly
left a comment
Collaborator
There was a problem hiding this comment.
breaking changes suppressed are not false positive. Please resolve them instead of suppresion
…to arjun/vnra-vnet-ps-changes-2025-07-01 # Conflicts: # src/Network/Network/ChangeLog.md
…07-01' into arjun/vnra-vnet-ps-changes-2025-07-01
…to string Revert PSVirtualNetworkAppliance.BandwidthInGbps from double? back to string, remove the 4 suppressed breaking-change entries from BreakingChangeIssues.csv, and update VNA scenario test assertions to string "50". Addresses reviewer feedback to resolve the breaking change instead of suppressing it.
Contributor
Author
I changed it back to string |
The VNA breaking-change suppressions were already removed; the only remaining diff was an added trailing newline. Restore the file to match the base branch so it is no longer part of the PR.
…ert) The -Bandwidth parameter type (string) and its numeric validation are unchanged from the shipped release, so the entry described a non-change. Genuine new features (PrivateIPAddressVersion, SummarizedGatewayPrefix) remain documented.
…list Use quoted string bandwidth values in examples (matches string parameter) and remove the enumerated valid values from the -Bandwidth description.
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
VeryEarly
approved these changes
Jul 21, 2026
VeryEarly
merged commit Jul 21, 2026
9fcad1b
into
Azure:release-network-2025-07-01
10 of 12 checks passed
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
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.