Skip to content

Commit ad0a0e5

Browse files
authored
Merge pull request #249677 from craigshoemaker/patch-18
[Container Apps] Networking: Add named anchors
2 parents 56d45f6 + 3e8bf63 commit ad0a0e5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/networking.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ In addition, Container Apps on the workload profiles environment reserve the fol
148148
## Routes
149149

150150
User Defined Routes (UDR) and controlled egress through NAT Gateway are supported in the workload profiles environment, which is in preview. In the Consumption only environment, these features aren't supported.
151-
151+
<a name="udr"></a>
152152
### User defined routes (UDR) - preview
153153

154154
> [!NOTE]
@@ -191,7 +191,7 @@ Network rules allow or deny traffic based on the network and transport layer. Th
191191

192192
> [!Note]
193193
> For Azure resources you are using with Azure Firewall not listed in this article, please refer to the [service tags documentation](../virtual-network/service-tags-overview.md#available-service-tags).
194-
194+
<a name="nat"></a>
195195
### NAT gateway integration - preview
196196

197197
You can use NAT Gateway to simplify outbound connectivity for your outbound internet traffic in your virtual network on the workload profiles environment. NAT Gateway is used to provide a static public IP address, so when you configure NAT Gateway on your Container Apps subnet, all outbound traffic from your container app is routed through the NAT Gateway's static public IP address.

0 commit comments

Comments
 (0)