Add DisablePeeringRoute parameter to New-AzRouteTable#29252
Merged
VeryEarly merged 5 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). |
Contributor
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
NoriZC
reviewed
Mar 11, 2026
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
sonalsingh-msft
force-pushed
the
sonalsingh/dprPSChanges
branch
from
April 20, 2026 18:37
88fd5f7 to
13909f3
Compare
Contributor
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
sonalsingh-msft
force-pushed
the
sonalsingh/dprPSChanges
branch
from
July 14, 2026 20:37
13909f3 to
ec33496
Compare
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
VeryEarly
reviewed
Jul 19, 2026
added 5 commits
July 20, 2026 09:28
…r forward compatibility
…egion The DisablePeeringRoute feature is currently only enabled in the Central US EUAP canary region, so the test now targets that region. Also drops the list-vs-get assertion for DisablePeeringRoute because the route tables list endpoint does not project that property (only the single-resource GET returns it).
The New-AzRouteTable help documents -DisablePeeringRoute as accepting pipeline input by property name, and all other value-carrying parameters on this cmdlet (ResourceGroupName, Name, Location, Tag, Route) set ValueFromPipelineByPropertyName. Add it here for consistency and to keep the help in sync with the parameter definition.
Addresses review feedback: the entry was under the shipped Version 7.27.0 section; moved it to the top of Upcoming Release.
sonalsingh-msft
force-pushed
the
sonalsingh/dprPSChanges
branch
from
July 20, 2026 16:29
83fd32a to
548a296
Compare
Collaborator
|
/azp run |
Contributor
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
VeryEarly
approved these changes
Jul 21, 2026
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
This PR adds support for the
DisablePeeringRoutefeature on Route Tables.Changes:
DisablePeeringRouteproperty to RouteTable SDK modelDisablePeeringRoute.cswithNoneandAllconstantsDisablePeeringRouteproperty toPSRouteTablePowerShell model-DisablePeeringRouteparameter toNew-AzRouteTablecmdlet withValidateSet("None", "All")New-AzRouteTableRelated:
Checklist