Hi 56789,
Based on the image, NAT (Network Address Translation) should theoretically work on Connection 3. This is because you’re planning to use private BGP IP addresses at both ends (on-premises and Azure VPN gateway).
If the on-premises VPN router uses regular, non-APIPA address and it collides with the virtual network address space or other on-premises network spaces, ensure the IngressSNAT rule will translate the BGP peer IP to a unique, non-overlapped address and put the post-NAT address in the BGP peer IP address field of the local network gateway.> NAT isn't supported with BGP APIPA addresses.> https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#does-nat-work-with-bgp-connections
The use of private IP addresses for BGP should not be affected by the limitations associated with APIPA (Automatic Private IP Addressing) addresses, which are used in Connections 1 and 2. Be sure the on-premises BGP routers advertise the exact prefixes as defined in the IngressSNAT rules.
Additional MS reference:
- https://learn.microsoft.com/en-us/azure/vpn-gateway/nat-howto
- https://learn.microsoft.com/en-us/azure/vpn-gateway/nat-overview
- https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq
Luis