How can we improve Azure Networking?

Support communicating to the frontend IP address of a globally peered internal load balancer

The VNet peering documentation contains the following constraint:

Resources in one virtual network cannot communicate with the frontend IP address of an Azure internal load balancer in the globally peered virtual network. The load balancer and the resources that communicate with it must be in the same region.

In scenarios that require a resource to access a load balanced application in another region, a 3rd party load balancer is required.

22 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mike Webber shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        +1 we really need this feature, especially when peering vnets from different subscriptions

      • Riccardo commented  ·   ·  Flag as inappropriate

        This limitation is an headache.
        I had to replace my Global VNET peering with VNET2VNET connection (not fair).
        I have 2 AKS in 2 different regions and need to connect from one region to the other by ILB.
        I cannot use a third party LB, the mission is keep it simple.
        Yes please, can you provide an ETA?
        Thanks

      • Ganesh Majeti commented  ·   ·  Flag as inappropriate

        Hello, Thankyou for starting to implement the fix for this issue.. Can you please provide an ETA to the fix?

      Feedback and Knowledge Base