Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,659 questions
Virtual Network Gateway BGP
Handian Sudianto
5,731
Reputation points
My vnet address space is 172.16.0.0/24 with below detail
Then i create Virtual Network gateway and my BGP Peer IP address 172.16.0.62.
When we creating the Local Network gateway should we assign BGP peer IP Address for my onprem devices under subnet 172.16.0.0/26? I try use 172.16.0.11
But i get below error while assigning the Local Network gateway to Virtual Network gateway
The local network gateway /subscriptions/xxxxx/resourceGroups/rg-networkservices-common/providers/Microsoft.Network/localNetworkGateways/lgw1 cannot have overlapping address space from virtual network gateway subnet /subscriptions/xxx/resourceGroups/rg-networkservices-common/providers/Microsoft.Network/virtualNetworkGateways/1. Click here for details
What BGP Peer IP Address should i use for my onprem devices?
{count} votes
-
![](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(204.8, 81%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Sai Prasanna Sinde 4,170 Reputation points Microsoft Vendor2025-02-28T03:59:27.1733333+00:00 Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
BGP Peer IP addresses are used for establishing BGP (Border Gateway Protocol) peering between your Azure Virtual Network Gateway and your on-premises router.
They must be unique and routable; they should not overlap with your VNet address space or the GatewaySubnet.
Since your VNet is 172.16.0.0/24, you cannot use any IP address within that range for your on-premises BGP Peer IP. You mentioned trying 172.16.0.11, which is also within your VNet and will cause the same error. You need to select a private IP address from a different range that is routable from your on-premises network.
On your on-premises network, create a small subnet specifically for BGP peering. for example, you could use 192.168.100.0/30. This range provides 4 IP addresses, with 2 usable for the BGP peers and assign one of these IPs to your on-premises router's BGP interface.
In your Azure Local Network Gateway (Lgw), specify the on-premises BGP Peer IP address from the subnet you created and configure the address space of the Local Network Gateway to represent the networks you want to advertise from on-premises to Azure. This should not include the BGP peering subnet.
Make sure the BGP Peer IP address of the Virtual Network Gateway is correctly configured (172.16.0.62 in your case) and make sure the ASNs match on both sides.
Reference: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-bgp-overview
Please let us know in the comments below or give this an upvote if the information above is helpful or if you need further assistance with this issue.
-
Handian Sudianto 5,731 Reputation points
2025-02-28T07:56:45.3366667+00:00 So it's okay if Azure BGP peer is 172.16.0.62 then in my on prem use 192.168.100.100 for example?
-
Sai Prasanna Sinde 4,170 Reputation points Microsoft Vendor
2025-02-28T10:15:21.78+00:00 Yes, that is correct.
Azure BGP Peer: 172.16.0.62 (within your Azure VNet but specifically for the VPN Gateway)
On premises BGP Peer: 192.168.100.100 (or any other IP from a different, non-overlapping subnet)
Just make sure that the 192.168.100.100 IP address is routable from your on-premises network.
Kindly let us know if the above helps or you need further assistance on this issue.
Sign in to comment
Sign in to answer