Skip to content

Commit cc3509c

Browse files
add managed resources section
1 parent 366987c commit cc3509c

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/container-apps/vnet-custom.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: container-apps
77
ms.topic: how-to
8-
ms.date: 1/28/2021
8+
ms.date: 2/3/2022
99
ms.author: cshoe
1010
zone_pivot_groups: azure-cli-or-portal
1111
---
@@ -67,6 +67,10 @@ To create an internal only environment, provide the `--internal-only` parameter
6767

6868
::: zone-end
6969

70+
## Managed resources
71+
72+
When you deploy an internal or an external environment into your own network, a new resource group prefixed with `MC_` is created in the Azure subscription where your environment is hosted. This resource group contains infrastructure components managed by the Azure Container Apps platform, and shouldn't be modified. The resource group contains Public IP addresses used specifically for outbound connectivity from your environment as well as a load balancer. As the load balancer is created in your subscription, there are additional costs associated with deploying the service to a custom virtual network.
73+
7074
## Example
7175

7276
The following example shows you how to create a Container Apps environment in an existing virtual network.

0 commit comments

Comments
 (0)