Skip to content

Commit a9a71c9

Browse files
committed
minir update to no Nat Note
1 parent 236c4a2 commit a9a71c9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-vmware/enable-public-ip-nsx-edge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ A Sourced Network Translation Service (SNAT) with Port Address Translation (PAT)
6565
To enable SNAT for your specified address ranges, you must configure a gateway firewall rule and SNAT for the specific address ranges you desire. If you do not want SNAT enabled for specific address ranges, you must also create a No-NAT rule for the address ranges you wish to exclude. For this functionality to work as expected, make the No-NAT rule a higher priority than the SNAT rule.
6666

6767
>[!Note]
68-
> To enable SNAT for your specified address ranges, you must [configure a gateway firewall rule](#gateway-firewall-used-to-filter-traffic-to-vms-at-t1-gateways) and SNAT for the specific address ranges you desire. If you don't want SNAT enabled for specific address ranges, you must also create a [No-NAT rule for the address ranges](#no-nat-rule-for-specific-address-ranges) for the address ranges you wish to exclude. For this functionality to work as expected, make the No-NAT rule a higher priority than the SNAT rule.
68+
> To enable SNAT for your specified address ranges, you must [configure a gateway firewall rule](#gateway-firewall-used-to-filter-traffic-to-vms-at-t1-gateways) and SNAT for the specific address ranges you desire. If you don't want SNAT enabled for specific address ranges, you must also create a [No-NAT rule](#no-nat-rule-for-specific-address-ranges) for the address ranges you wish to exclude. For this functionality to work as expected, make the No-NAT rule a higher priority than the SNAT rule.
6969
7070
**Add rule**
7171
1. From your Azure VMware Solution private cloud, select **vCenter Credentials**

0 commit comments

Comments
 (0)