Load Balancer over Gobal VNet Peering

Question

Hi everyone, last year this update was provided by Microsoft

"Global VNet Peering now supports Standard Load Balancer. Previously, resources in one virtual network could not communicate with the front-end IP address of an internal load balancer over a globally peered connection. The virtual networks needed to be in the same region. With this announcement, this is no longer the case. You can communicate with the internal IP address of a Standard Load Balancer instance across regions from resources deployed in a globally peered virtual network. This support is in all Azure regions, including Azure China and Azure Government regions."

I am running a POC to test this out with no success. Has anyone successfully deployed Standard Load Balancer with back end pool extending over different regions? I contacted Azure Support and they told me its not possible. so is this update false or I am miss understanding it?

My test included 3 VMs with IIS deployed, answering on TCP 443. 2 in Canada Central and 1 in Canada East. A Standard load balancer deployed in Canada East with backend pool included the 2 VMs in Canada Central, but I could not add the one in Canada East as it simply does not give me the option.

Answer 1

@James Zu , Here are some of the constraints for peered virtual networks,
Resources in one virtual network can't communicate with the front-end IP address of a Basic Internal Load Balancer (ILB) in a globally peered virtual network.
Some services that use a Basic load balancer don't work over global virtual network peering. For more information, see What are the constraints related to Global VNet Peering and Load Balancers?.

Ref: https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview

----------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.

Answer 2

I am having the same issue, @suvasara-MSFT , the comment and page you mention basic load balancers, we are talking about standing load balancers. Per the link this should be supported.

Answer 3

@James Zu , @joe pukepail , You should be able to communicate with the internal IP address of a Standard Load Balancer instance across regions from resources deployed in a globally peered virtual network. We are looking into this issue. Please stay tuned!