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: articles/virtual-network/nat-gateway/troubleshoot-nat.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ This article provides guidance on how to configure your NAT gateway to ensure ou
38
38
Check the following configurations to ensure that NAT gateway can be used to direct traffic outbound:
39
39
1. At least one public IP address or one public IP prefix is attached to NAT gateway. At least one public IP address must be associated with the NAT gateway for it to provide outbound connectivity.
40
40
2. At least one subnet is attached to a NAT gateway. You can attach multiple subnets to a NAT gateway for going outbound, but those subnets must exist within the same virtual network. NAT gateway cannot span beyond a single virtual network.
41
-
3. No [NSG rules](../network-security-groups-overview.md#outbound) or [UDRs](#udr-supersedes-nat-gateway-for-going-outbound) are blocking NAT gateway from directing traffic outbound to the internet.
41
+
3. No [NSG rules](../network-security-groups-overview.md#outbound) or [UDRs](#virtual-appliance-and-virtual-network-gateway-udrs-supersede-nat-gateway-for-going-outbound) are blocking NAT gateway from directing traffic outbound to the internet.
0 commit comments