Need inputs on Vnet peering

Question

Need inputs on Vnet peering

Martinmajestic-3285 105

Hi

I have a couple of questions regarding my Virtual Network Peering setup.

Can I resize my Peered Virtual Network Address space without any impact?
I have an Azure load balancer running on Vnet B, and I want to connect with the load balancer from Vnet A, but it is not working, even though I have peering enabled in both Vnet A and B.

Any help would be much appreciated. Thanks.

Silvia Wibowo 5,866 Reputation points Microsoft Employee Moderator

2025-05-07T04:53:08.45+00:00
Hi @Martinmajestic-3285 ,

Yes. You can update a peered virtual network by modifying, adding, or deleting an address space using the Azure portal. These updates don't incur downtime interruptions. You need to ensure that it doesn't overlap other address spaces. Ref: Update the address space for a peered virtual network

Please elaborate more on your issue: how did you try to connect, using VM or something else? What address you use to connect to Load Balancer: IP address, private DNS name, public DNS name? What's the error message?
Martinmajestic-3285 105 Reputation points

2025-05-07T06:47:34.1133333+00:00

Hello @Sai Prasanna Sinde thanks for your response, as you mentioned "Resources in one virtual network can't communicate with the front-end IP address of a basic load balancer (internal or public) in a globally peered virtual network." Does this limitation also apply to Standard Load Balancers?
Sai Prasanna Sinde 5,635 Reputation points Microsoft External Staff Moderator

2025-05-07T07:05:31.6666667+00:00

Hi @Martinmajestic-3285

No, this limitation does not apply to Standard Load Balancers.

Resources in a peered virtual network (both regional and global peering) can communicate with the front-end IP address of a Standard Load Balancer (internal or public) located in the peered virtual network. Standard Load Balancers are designed to be compatible with VNet peering scenarios, including global peering.

Reference: Azure updates

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on this post.

If you have any further queries, please let us know in the comments below so that we can address them.
Sai Prasanna Sinde 5,635 Reputation points Microsoft External Staff Moderator

2025-05-08T07:56:36.8133333+00:00

Hi @Martinmajestic-3285

Following up to see if the below answer was helpful. If this answers your query, do click **Accept Answer**. And, if you have any further query do let us know in the comments below.

Accepted answer

0 additional answers

Your answer

Silvia Wibowo 5,866 Reputation points Microsoft Employee Moderator

2025-05-07T04:53:08.45+00:00

Hi @Martinmajestic-3285 ,

Yes. You can update a peered virtual network by modifying, adding, or deleting an address space using the Azure portal. These updates don't incur downtime interruptions. You need to ensure that it doesn't overlap other address spaces. Ref: Update the address space for a peered virtual network

Please elaborate more on your issue: how did you try to connect, using VM or something else? What address you use to connect to Load Balancer: IP address, private DNS name, public DNS name? What's the error message?
Martinmajestic-3285 105 Reputation points

2025-05-07T06:47:34.1133333+00:00

Hello @Sai Prasanna Sinde thanks for your response, as you mentioned "Resources in one virtual network can't communicate with the front-end IP address of a basic load balancer (internal or public) in a globally peered virtual network." Does this limitation also apply to Standard Load Balancers?
Sai Prasanna Sinde 5,635 Reputation points Microsoft External Staff Moderator

2025-05-07T07:05:31.6666667+00:00

Hi @Martinmajestic-3285

No, this limitation does not apply to Standard Load Balancers.

Resources in a peered virtual network (both regional and global peering) can communicate with the front-end IP address of a Standard Load Balancer (internal or public) located in the peered virtual network. Standard Load Balancers are designed to be compatible with VNet peering scenarios, including global peering.

Reference: Azure updates

If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on this post.

If you have any further queries, please let us know in the comments below so that we can address them.
Sai Prasanna Sinde 5,635 Reputation points Microsoft External Staff Moderator

2025-05-08T07:56:36.8133333+00:00

Hi @Martinmajestic-3285

Following up to see if the below answer was helpful. If this answers your query, do click **Accept Answer**. And, if you have any further query do let us know in the comments below.

Answer 1

Hi @Martinmajestic-3285

Answering your questions,

You can resize the address space of Azure virtual networks that are peered without incurring any downtime on the currently peered address space. This feature is useful when you need to resize the virtual network's address space after you scale your workloads. After the address space is resized, peers must sync with the new address space changes. Resizing works for both IPv4 and IPv6 address spaces. Please refer the document for more information.
Resources in one virtual network can't communicate with the front-end IP address of a basic load balancer (internal or public) in a globally peered virtual network. Please refer the document for more information.

Kindly let us know if the above helps or you need further assistance on this issue.

Share via

Need inputs on Vnet peering

0 additional answers

Your answer