![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 46%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,775 questions
Hello @prasantc ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand that you were able to downsize your Vnets from /20 to /21 which were peered to other Vnets and the subnet was not using all the IP scope but doing the same in production with same range of IPs and subnets in a Vnet errored out as it had a remote hub peering on a VWAN. You would like to if there is a resize limitation and what is the best approach to downsize Vnet with remote hub peering.
As per Vnet peering documentation,
You can resize the address space of Azure virtual networks that are peered without incurring any downtime on the currently peered address space. Once the address space is resized, peers must sync with the new address space changes. Resizing works for both IPv4 and IPv6 address spaces.
However, this feature doesn't support scenarios where the virtual network to be updated is peered with:
- A classic virtual network
- A managed virtual network such as the Azure VWAN hub
If your Vnet has a remote hub peering on a VWAN, then downsizing/re-sizing the Vnet in such a case is not supported.
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.