Skip to content

Commit 3144efa

Browse files
Merge pull request #221542 from aimee-littleton/patch-119
clarify when outbound takes place
2 parents 67f2438 + 71d7a22 commit 3144efa

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/virtual-network/nat-gateway/nat-gateway-resource.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,9 @@ Private Link uses the private IP addresses of your virtual machines or other com
5050

5151
### Connect to the internet with NAT gateway
5252

53-
NAT gateway is recommended for all production workloads where you need to connect to a public endpoint over the internet. When NAT gateway is configured to subnets, all previous outbound configurations, such as Load balancer or instance-level public IPs (IL PIPs) are superseded by NAT gateway. Outbound initiated and return traffic go through NAT gateway. There's no down time on outbound connectivity after adding NAT gateway to a subnet with existing outbound configurations.
53+
NAT gateway is recommended for all production workloads where you need to connect to a public endpoint over the internet. Outbound connectivity takes place right away upon deployment of a NAT gateway with a subnet and at least one public IP address. No additional routing configurations are required to start connecting outbound with NAT gateway. NAT gateway becomes the default route to the internet after association to a subnet.
54+
55+
In the presence of other outbound configurations within a virtual network, such as Load balancer or instance-level public IPs (IL PIPs), NAT gateway takes precedence for outbound connectivity. All new outbound initiated and return traffic starts using NAT gateway. There's no down time on outbound connectivity after adding NAT gateway to a subnet with existing outbound configurations.
5456

5557
### Coexistence of outbound and inbound connectivity
5658

0 commit comments

Comments
 (0)