Skip to content

Commit 9e1b80c

Browse files
Merge pull request #127154 from davmhelm/davmhelm-patch-defaultoutbound-1
Update default-outbound-access.md
2 parents f90ee8f + 59e2fb5 commit 9e1b80c

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/virtual-network/ip-services/default-outbound-access.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,15 @@ az network vnet subnet update --resource-group rgname --name subnetname --vnet-n
160160

161161
* To activate or update virtual machine operating systems, such as Windows, an explicit outbound connectivity method is required.
162162

163-
* In configurations using a User Defined Route (UDR) with a default route (0.0.0.0/0) that sends traffic to an upstream firewall/network virtual appliance, any traffic that bypasses this route (for example, to Service Tagged destinations) breaks in a Private subnet.
163+
* In configurations using User Defined Routes (UDRs), any configured routes with [next hop type `Internet`](../virtual-networks-udr-overview.md#next-hop-types-across-azure-tools) will break in a Private subnet.
164+
165+
* A common example is the use of a UDR to steer traffic to an upstream network virtual appliance/firewall, with exceptions for certain Azure Service Tags to bypass inspection.
166+
167+
* A default route for the destination 0.0.0.0/0, with a next hop type of Virtual Appliance applies in the general case.
168+
169+
* One or more routes are configured to [Service Tag destinations](../virtual-networks-udr-overview.md#service-tags-for-user-defined-routes) with next hop type `Internet`, to bypass the NVA/firewall. Unless an [explicit outbound connectivity method](#add-an-explicit-outbound-connectivity-method) is also configured for the source of the connection to these destinations, attempts to connection to these destinations will fail, because default outbound access isn't available.
170+
171+
* This limitation doesn't apply to the use of Service Endpoints, which use a different next hop type `VirtualNetworkServiceEndpoint`. See [Virtual Network service endpoints](../virtual-network-service-endpoints-overview.md).
164172

165173
* Private Subnets aren't applicable to delegated or managed subnets used for hosting PaaS services. In these scenarios, outbound connectivity is managed by the individual service.
166174

0 commit comments

Comments
 (0)