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/nat-gateway/nat-overview.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ The following steps are an example of how to set up a NAT gateway:
51
51
52
52
* Assign a public IP address or public IP prefix.
53
53
54
-
* Configure virtual network subnet to use a NAT gateway.
54
+
* Configure a virtual network subnet to use a NAT gateway.
55
55
56
56
If necessary, modify Transmission Control Protocol (TCP) idle timeout (optional). Review [timers](/azure/nat-gateway/nat-gateway-resource#idle-timeout-timers) before you change the default.
57
57
@@ -88,13 +88,13 @@ A NAT gateway doesn't affect the network bandwidth of your compute resources. Le
88
88
89
89
* Egress is defined at a per subnet level with NAT gateway. NAT gateway replaces the default Internet destination of a subnet.
90
90
91
-
* Traffic routing configurations aren't required to use NAT gateway.
91
+
* Traffic routing configurations on a subnet route table aren't required to use NAT gateway.
92
92
93
93
* NAT gateway allows flows to be created from the virtual network to the services outside your virtual network. Return traffic from the internet is only allowed in response to an active flow. Services outside your virtual network can’t initiate an inbound connection through NAT gateway.
94
94
95
95
* NAT gateway takes precedence over other outbound connectivity methods, including a load balancer, instance-level public IP addresses, and Azure Firewall.
96
96
97
-
* When NAT gateway is configured to a virtual network where a different outbound connectivity method already exists, NAT gateway takes over all outbound traffic moving forward. There are no drops in traffic flow for existing connections on Azure Load Balancer. All new connections use NAT gateway.
97
+
* When NAT gateway is configured to a virtual network where a different outbound connectivity method already exists, NAT gateway takes over all outbound traffic moving forward. There are no drops in traffic flow for existing connections. All new connections use NAT gateway.
98
98
99
99
* NAT gateway doesn't have the same limitations of SNAT port exhaustion as does [default outbound access](../virtual-network/ip-services/default-outbound-access.md) and [outbound rules of a load balancer](../load-balancer/outbound-rules.md).
100
100
@@ -104,7 +104,6 @@ A NAT gateway doesn't affect the network bandwidth of your compute resources. Le
104
104
105
105
* The subnet has a [system default route](/azure/virtual-network/virtual-networks-udr-overview#default) that routes traffic with destination 0.0.0.0/0 to the internet automatically. Once NAT gateway is configured to the subnet, communication from the virtual machines existing in the subnet to the internet will prioritize using the public IP of the NAT gateway.
106
106
107
-
108
107
* When you create a user defined route (UDR) in your subnet route table for 0.0.0.0/0 traffic, the default internet path for this traffic is overridden. A UDR that sends 0.0.0.0/0 traffic to a virtual appliance or a virtual network gateway (VPN Gateway and ExpressRoute) as the next hop type instead override NAT gateway connectivity to the internet.
109
108
110
109
* Outbound connectivity follows this order of precedence among different routing and outbound connectivity methods:
0 commit comments