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/container-apps/networking.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ There are two architectures in Container Apps: the Consumption only architecture
27
27
28
28
| Architecture Type | Description |
29
29
|-----------|-------------|
30
-
| Workload profiles architecture (preview) | Supports user defined routes (UDR) and egress through NAT Gateway when using a custom VNet. The minimum required subnet size is /27. |
30
+
| Workload profiles architecture (preview) | Supports user defined routes (UDR) and egress through NAT Gateway when using a custom virtual network. The minimum required subnet size is /27. |
31
31
| Consumption only architecture | Doesn't support user defined routes (UDR) and egress through NAT Gateway. The minimum required subnet size is /23. |
32
32
33
33
## Accessibility Levels
@@ -53,7 +53,7 @@ As you create a custom VNet, keep in mind the following situations:
53
53
- You can restrict inbound requests to the environment exclusively to the VNet by deploying the environment as [internal](vnet-custom-internal.md).
54
54
55
55
> [!NOTE]
56
-
> When you provide your own VNet, additional [managed resources](networking.md#managed-resources) are created which incur billing.
56
+
> When you provide your own virtual network, additional [managed resources](networking.md#managed-resources) are created, which incur billing.
57
57
58
58
As you begin to design the network around your container app, refer to [Plan virtual networks](../virtual-network/virtual-network-vnet-plan-design-arm.md) for important concerns surrounding running virtual networks on Azure.
0 commit comments