How to re-size Azure virtual networks that are peered—now in preview | Azure Blog and Updates

As prospects undertake and scale their purposes in Azure, they continually must develop or resize their networks within the cloud. Digital networks in Azure have had a long-standing constraint the place any deal with area change is barely allowed if the digital community doesn’t have any peerings. As we speak, we’re saying that this limitation has been lifted, and prospects can freely resize their digital networks with out incurring any downtime. With this function, current peerings on the digital community don’t should be deleted previous to including or deleting an deal with prefix on the digital community.

Particulars on including or eradicating deal with area on peered digital networks

You’ll be able to replace (add or take away) deal with area on a digital community that’s peered with one other digital community in the identical area or throughout areas. Deal with area replace on digital networks additionally works if the digital community has peered with one other digital community throughout subscriptions. Be aware: Digital networks which have peerings throughout AD-tenants are at present not supported. This function introduces two new properties on the virtualNetworkPeerings object of the digital community:This function introduces two new properties on the virtualNetworkPeerings object of the digital community:

• remoteVirtualNetworkAddressSpace: Incorporates essentially the most present deal with area of the peered digital community. This deal with might or is probably not the identical because the peered deal with contained within the remoteAddressSpace property.
• peeringSyncLevel: Signifies if the deal with contained within the remoteVirtualNetworkAddressSpace property is identical because the deal with that’s truly peered with the digital community.

When deal with area on a digital community (1) is up to date, the corresponding peering hyperlinks on the distant digital networks in direction of this digital community (1) should be synced with the brand new deal with area. The standing of the peering hyperlinks between the 2 digital networks signifies which facet of the peering hyperlink must be synced with the brand new deal with area.

• LocalNotInSync: While you replace the deal with area on the primary digital community (1), the peering standing of the hyperlink from the second digital community (2) to the primary digital community (1) is LocalNotInSync. At this stage, whereas the peering is lively throughout the previous deal with area of the digital community, the brand new deal with area has not peered with the distant digital community.
• RemoteNotInSync: While you replace deal with area on the primary digital community (1), the peering standing of the hyperlink from the primary digital community to the second digital community (2) is RemoteNotInSync. A sync operation on the peering hyperlink from the digital community (2) to the digital community (1) will synchronize the deal with area throughout the peering.
• Be aware: Deal with modifications on digital networks in ARM which have peerings to ASM digital networks is enabled, nevertheless the ASM digital community is not going to be up to date with the brand new deal with area of the ARM digital community. 

The function is at present in preview and supported throughout all manufacturing Azure areas.

Get began in the present day

Updating the deal with area on a digital community that’s peered could be achieved in two simple steps. It’s supported by means of REST APIs in addition to Portal and PowerShell shoppers.

1. Add a brand new deal with on a digital community that has lively peering connections with different digital networks.
2. Carry out a “sync” on the peering hyperlink from every of the peered distant digital networks to this digital community (1) on which the deal with change is made. This motion is required for every distant peered VNet to study of the newly added deal with prefix.

To do that on the Azure portal, go to the peerings tab on the digital community the place the deal with replace has been made. Choose all of the peerings which have peering standing as “Distant sync required”, after which click on the Sync button. It will be sure that all of the distant peered digital networks study the up to date deal with area of this digital community (1).

The sync may also be carried out individually on the peering hyperlink from every distant peered digital community by going to the peerings tab on the distant digital networks.

To do that in PowerShell, use the commandlet: Sync-AzVirtualNetworkPeering on every peering hyperlink from the distant digital community to the digital community (1) on which the deal with change is made.

Whereas the function is in preview, prospects must register their subscriptions with the next function flag: Microsoft.Community/AllowUpdateAddressSpaceInPeeredVnets to make use of this functionality. This flag can be deprecated when the function is usually out there.

Try the video to efficiently add a brand new deal with prefix on an Azure Digital Community that’s peered to a different digital community, utilizing the Azure portal.

What’s subsequent?

We could have a number of enhancements to the consumer expertise rolling out within the subsequent few weeks. These will embody a single-click (bulk) possibility on the Azure portal to “sync” a number of friends when an deal with area change is made in addition to improved warning and error messages. Moreover, help for digital networks which are peered throughout Azure Lively Listing tenants will even be step by step rolled out within the subsequent few weeks.

Basic availability for this function is focused within the subsequent month. We’re at all times listening and making fixed enhancements, so please preserve the suggestions coming.