Greetings.
Points to Note:
- Azure does not have an out of the box Private Traffic NAT Solution as of today.
- Azure NAT Gateway is used for Internet Bound communications, not for S2S traffic
There are 2 options you can consider,
1.
- You can consider using Dynamic NAT on Azure VPN Gateway
- When Dynamic NAT rules are used, traffic is unidirectional which means communication must be initiated from the site that is represented in the Internal Mapping field of the rule. If traffic is initiated from the External Mapping, the connection will not be established.
- You should use an EgressSNAT Rule
- If you require bidirectional traffic initiation, then use a static NAT rule to define a 1:1 mapping. (But static NAT would have a wider Address range)
- You can also use the Azure Firewall SNAT ***with private IP address ranges *and not DNAT
- Again, this requires that the OnPrem (Destination) whitelist the entire AzureFirewallSubnet range
- As Azure Firewall SNATs the traffic to one of the firewall private IP addresses in AzureFirewallSubnet range
- The AzureFirewallSubnet should be a minimum of /26 - meaning, you should whitelist the 62 IP Addresses that are part of the /26 AzureFirewallSubnet
Hope this is clear.
Kindly let us know if this helps or you need further assistance on this issue.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.