How to use public IP address NAT for VPN traffic

EddieB 0 Reputation points
2024-08-28T14:59:11.6866667+00:00

We already have multiple VPN connections up and running in our Azure Virtual Network connecting to our on-prem locations.

Now we have an external 3rd party that we need to connect to via VPN as well.

For this new connection, they require that the the traffic going over the VPN is NATed via a PUBLIC IP address. They cannot accept private or shared IP subnet spaces. So this will be in addition to the public gateway IP address... If we can use the same address for the VPN gateway and NATing that would be fine, but not a requirement.

I am able to establish the IKEv2 S2S VPN connection without any problems, but on the other end, AFTER data goes through the VPN runnel, they are seeing the traffic coming from our internal subnets.

I have tried adding a public IP address to the VM on our end that needs to connect to them, but I am not sure how to route traffic, using the public IP address, through the VPN gateway, or if that is even an option.

I was also wondering if there is a setting within the Virtual Network Gateway to enforce this behavior, to force it to NAT the VPN traffic via a public IP address.

Thanks

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,508 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.