You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: includes/vpn-gateway-faq-nat-include.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,3 +74,7 @@ Yes, this is typically used when the connections are for the same on-premises ne
74
74
### Do I need both Ingress and Egress rules on a NAT connection?
75
75
76
76
You need both Ingress and Egress rules on the same connection when the on-premise network address space overlaps with the VNet address space. If the VNet address space is unique among all connected networks, you don't need the EgressSNAT rule on those connections. You can use the Ingress rules to avoid address overlap among the on-premises networks.
77
+
78
+
### What do I choose as "IP configuration ID" ?
79
+
80
+
"IP configuration ID" is simply the name of the IP configuration object you want the NAT rule to use. With this setting, you are simply choosing which gateway public IP address applies to the NAT rule. If you haven't specified any custom name at gateway creation time, the gateway's primary IP address is assigned to the "default" IPconfiguration and the secondary IP is assigned to the "activeActive" IPconfiguration.
0 commit comments