Merge pull request #187356 from craigshoemaker/ca/vnet-updates

[Container Apps] VNET updates

Author: PRMerger14

articles/container-apps/get-started.md

@@ -82,6 +82,9 @@ az containerapp create `
 
 ---
 
+> [!NOTE]
+> Make sure the value for the `--image` parameter is in lower case.
+
 By setting `--ingress` to `external`, you make the container app available to public requests.
 
 ## Verify deployment

articles/container-apps/vnet-custom.md

@@ -25,15 +25,30 @@ As you create an Azure Container Apps [environment](environment.md), a virtual n
 
 :::image type="content" source="media/networking/azure-container-apps-virtual-network.png" alt-text="Azure Container Apps environments use an existing VNET, or you can provide your own.":::
 
+## Restrictions
+
+Subnet address ranges can't overlap with the following reserved ranges:
+
+- 169.254.0.0/16
+- 172.30.0.0/16
+- 172.31.0.0/16
+- 192.0.2.0/24
+
+Additionally, subnets must have a size between /21 and /12.
+
 ## Subnet types
 
 As a Container Apps environment is created, you provide resource IDs for two different subnets. Both subnets must be defined in the same container apps.
 
 - **App subnet**: Subnet for user app containers. Subnet that contains IP ranges mapped to applications deployed as containers.
 - **Control plane subnet**: Subnet for [control plane infrastructure](/azure/azure-resource-manager/management/control-plane-and-data-plane) components and user app containers.
 
+::: zone pivot="azure-cli"
+
 If the [platformReservedCidr](#networking-parameters) range is defined, both subnets must not overlap with the IP range defined in `platformReservedCidr`.
 
+::: zone-end
+
 ## Accessibility level
 
 You can deploy your Container Apps environment with an internet-accessible endpoint or with an IP address in your VNET. The accessibility level determines the type of load balancer used with your Container Apps instance.
@@ -46,8 +61,12 @@ Container Apps environments deployed as external resources are available for pub
 
 When set to internal, the environment has no public endpoint. Internal environments are deployed with a virtual IP (VIP) mapped to an internal IP address. The internal endpoint is an Azure internal load balancer (ILB) and IP addresses are issued from the custom VNET's list of private IP addresses.
 
+::: zone pivot="azure-cli"
+
 To create an internal only environment, provide the `--internal-only` parameter to the `az containerapp env create` command.
 
+::: zone-end
+
 ## Example
 
 The following example shows you how to create a Container Apps environment in an existing virtual network.
@@ -234,6 +253,9 @@ az containerapp env create `
 
 ---
 
+> [!NOTE]
+> As you call `az conatinerapp create` to create the container app inside your environment, make sure the value for the `--image` parameter is in lower case.
+
 The following table describes the parameters used in for `containerapp env create`.
 
 | Parameter | Description |
@@ -343,7 +365,9 @@ az network private-dns record-set a add-record `
 
 #### Networking parameters
 
-There are three optional networking parameters you can choose to define when calling `containerapp env create`. You must either provide values for all three of these properties, or none of them. If they aren’t provided, the CLI generates the values for you.
+There are three optional networking parameters you can choose to define when calling `containerapp env create`. Use these options when you have a peered VNET with separate address ranges. Explicitly configuring these ranges ensures the addresses used by the Container Apps environment doesn't conflict with other ranges in the network infrastructure.
+
+You must either provide values for all three of these properties, or none of them. If they aren’t provided, the CLI generates the values for you.
 
 | Parameter | Description |
 |---|---|
@@ -381,17 +405,6 @@ az group delete `
 
 ::: zone-end
 
-## Restrictions
-
-Subnet address ranges can't overlap with the following reserved ranges:
-
-- 169.254.0.0/16
-- 172.30.0.0/16
-- 172.31.0.0/16
-- 192.0.2.0/24
-
-Additionally, subnets must have a size between /21 and /12.
-
 ## Additional resources
 
 - Refer to [What is Azure Private Endpoint](/azure/private-link/private-endpoint-overview) for more details on configuring your private endpoint.

includes/container-apps-create-cli-steps.md

@@ -1,6 +1,6 @@
 ---
 author: craigshoemaker
-ms.service: app-service
+ms.service: container-apps
 ms.topic: include
 ms.date: 01/26/2022
 ms.author: cshoe