[ACA] [335389] Combine vnet-custom and vnet-custom-internal.

Author: v-jaswel

articles/container-apps/vnet-custom-internal.md

@@ -1,6 +1,6 @@
 ---
 title: Integrate a virtual network with an internal Azure Container Apps environment
-description: Learn how to integrate a VNET to an internal Azure Container Apps environment.
+description: Learn how to integrate a virtual network with an internal Azure Container Apps environment.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
@@ -13,36 +13,36 @@ zone_pivot_groups: azure-cli-or-portal
 
 # Provide a virtual network to an internal Azure Container Apps environment
 
-The following example shows you how to create a Container Apps environment in an existing virtual network.
+The following example shows you how to create a Container Apps environment in an existing virtual network (VNet).
 
 ::: zone pivot="azure-portal"
 
 <!-- Create -->
 [!INCLUDE [container-apps-create-portal-steps.md](../../includes/container-apps-create-portal-steps.md)]
 
 > [!NOTE]
-> You can use an existing virtual network, but a dedicated subnet with a CIDR range of `/23` or larger is required for use with Container Apps when using the Consumption only environment. When using the workload profiles environment, a `/27` or larger is required. To learn more about subnet sizing, see the [networking environment overview](./networking.md#subnet).
+> An existing VNet must have a dedicated subnet with a CIDR range of `/23` or larger when using the Consumption only environemnt. It must have a CIDR range of `/27` or larger when using the workload profiles environment. To learn more about subnet sizing, see the [networking architecture overview](./networking.md#subnet).
 
-7. Select the **Networking** tab to create a VNET.
-8. Select **Yes** next to *Use your own virtual network*.
-9. Next to the *Virtual network* box, select the **Create new** link and enter the following value.
+1. Select the **Networking** tab to create a VNet.
+1. Select **Yes** next to *Use your own virtual network*.
+1. Next to the *Virtual network* box, select the **Create new** link and enter the following value.
 
     | Setting | Value |
     |--|--|
     | Name | Enter **my-custom-vnet**. |
 
-10. Select the **OK** button.
-11. Next to the *Infrastructure subnet* box, select the **Create new** link and enter the following values:
+1. Select the **OK** button.
+1. Next to the *Infrastructure subnet* box, select the **Create new** link and enter the following values:
 
     | Setting | Value |
     |---|---|
     | Subnet Name | Enter **infrastructure-subnet**. |
     | Virtual Network Address Block | Keep the default values. |
     | Subnet Address Block | Keep the default values. |
 
-12. Select the **OK** button.
-13. Under *Virtual IP*, select **Internal**.
-14. Select **Create**.
+1. Select the **OK** button.
+1. Under *Virtual IP*, select **Internal**.
+1. Select **Create**.
 
 <!-- Deploy -->
 [!INCLUDE [container-apps-create-portal-deploy.md](../../includes/container-apps-create-portal-deploy.md)]
@@ -83,7 +83,7 @@ Register-AzResourceProvider -ProviderNamespace Microsoft.ContainerService
 
 ---
 
-Declare a variable to hold the VNET name.
+Declare a variable to hold the VNet name.
 
 # [Bash](#tab/bash)
 
@@ -99,10 +99,7 @@ $VnetName = 'my-custom-vnet'
 
 ---
 
-Now create an instance of the virtual network to associate with the Container Apps environment. The virtual network must have two subnets available for the container app instance.
-
-> [!NOTE]
-> Network subnet address prefix requires a minimum CIDR range of `/23` for use with Container Apps when using the Consumption only environment. When using the Workload Profiles environment, a `/27` or larger is required. To learn more about subnet sizing, see the [networking environment overview](./networking.md#subnet).
+Now create a virtual network to associate with the Container Apps environment. The virtual network must have two subnets available for the container app instance.
 
 # [Bash](#tab/bash)
 
@@ -145,7 +142,7 @@ $vnet = New-AzVirtualNetwork @VnetArgs
 
 ---
 
-When using the Workload profiles environment, you need to update the VNET to delegate the subnet to `Microsoft.App/environments`. This delegation is not applicable to the Consumption-only environment.
+When using the Workload profiles environment, you need to update the VNet to delegate the subnet to `Microsoft.App/environments`. This delegation is not needed for the Consumption-only environment.
 
 # [Bash](#tab/bash)
 
@@ -167,7 +164,7 @@ $vnet | Set-AzVirtualNetwork
 
 ---
 
-With the VNET established, you can now query for the infrastructure subnet ID.
+With the virtual network created, you can now query for the infrastructure subnet ID.
 
 # [Bash](#tab/bash)
 
@@ -178,12 +175,12 @@ INFRASTRUCTURE_SUBNET=`az network vnet subnet show --resource-group ${RESOURCE_G
 # [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
-$InfrastructureSubnet = (Get-AzVirtualNetworkSubnetConfig -Name $SubnetArgs.Name -VirtualNetwork $vnet).Id
+$InfrastructureSubnet=(Get-AzVirtualNetworkSubnetConfig -Name $SubnetArgs.Name -VirtualNetwork $vnet).Id
 ```
 
 ---
 
-Finally, create the Container Apps environment with the VNET and subnet.
+Finally, create the Container Apps environment using the custom VNet.
 
 # [Bash](#tab/bash)
 
@@ -196,23 +193,21 @@ az containerapp env create \
   --internal-only
 ```
 
-The following table describes the parameters used in for `containerapp env create`.
+The following table describes the parameters used with `containerapp env create`.
 
 | Parameter | Description |
 |---|---|
 | `name` | Name of the Container Apps environment. |
 | `resource-group` | Name of the resource group. |
-| `logs-workspace-id` | (Optional) The ID of an existing the Log Analytics workspace.  If omitted, a workspace is created for you. |
+| `logs-workspace-id` | (Optional) The ID of an existing Log Analytics workspace.  If omitted, a workspace is created for you. |
 | `logs-workspace-key` | The Log Analytics client secret. Required if using an existing workspace. |
-| `location` | The Azure location where the environment is to deploy.  |
+| `location` | The Azure location where the environment is to deploy. |
 | `infrastructure-subnet-resource-id` | Resource ID of a subnet for infrastructure components and user application containers. |
-| `internal-only` | (Optional) The environment doesn't use a public static IP, only internal IP addresses available in the custom VNET. (Requires an infrastructure subnet resource ID.) |
-
-With your environment created using your custom virtual network, you can deploy container apps into the environment using the `az containerapp create` command.
+| `internal-only` | (Optional) The environment doesn't use a public static IP, only internal IP addresses available in the custom VNet. (Requires an infrastructure subnet resource ID.) |
 
 # [Azure PowerShell](#tab/azure-powershell)
 
-A Log Analytics workspace is required for the Container Apps environment.  The following commands create a Log Analytics workspace and save the workspace ID and primary shared key to environment variables.
+A Log Analytics workspace is required for the Container Apps environment. The following commands create a Log Analytics workspace and save the workspace ID and primary shared key to environment variables.
 
 ```azurepowershell-interactive
 $WorkspaceArgs = @{
@@ -234,7 +229,7 @@ $EnvArgs = @{
     EnvName = $ContainerAppsEnvironment
     ResourceGroupName = $ResourceGroupName
     Location = $Location
-    AppLogConfigurationDestination = 'log-analytics'
+    AppLogConfigurationDestination = "log-analytics"
     LogAnalyticConfigurationCustomerId = $WorkspaceId
     LogAnalyticConfigurationSharedKey = $WorkspaceSharedKey
     VnetConfigurationInfrastructureSubnetId = $InfrastructureSubnet
@@ -249,13 +244,11 @@ The following table describes the parameters used in for `New-AzContainerAppMana
 |---|---|
 | `EnvName` | Name of the Container Apps environment. |
 | `ResourceGroupName` | Name of the resource group. |
-| `LogAnalyticConfigurationCustomerId` | The ID of an existing the Log Analytics workspace. |
+| `LogAnalyticConfigurationCustomerId` | The ID of an existing Log Analytics workspace. |
 | `LogAnalyticConfigurationSharedKey` | The Log Analytics client secret.|
-| `Location` | The Azure location where the environment is to deploy.  |
+| `Location` | The Azure location where the environment is to deploy. |
 | `VnetConfigurationInfrastructureSubnetId` | Resource ID of a subnet for infrastructure components and user application containers. |
-| `VnetConfigurationInternal` | (Optional) The environment doesn't use a public static IP, only internal IP addresses available in the custom VNET. (Requires an infrastructure subnet resource ID.) |
-
-With your environment created using your custom virtual network, you can deploy container apps into the environment.
+| `VnetConfigurationInternal` | (Optional) The environment doesn't use a public static IP, only internal IP addresses available in the custom VNet. (Requires an infrastructure subnet resource ID.) |
 
 ---
 
@@ -350,7 +343,7 @@ New-AzPrivateDnsRecordSet @DnsRecordArgs
 
 #### Networking parameters
 
-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 don't conflict with other ranges in the network infrastructure.
+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 don'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 values are generated for you.
 
@@ -362,9 +355,9 @@ You must either provide values for all three of these properties, or none of the
 | `platform-reserved-dns-ip` | An IP address from the `platform-reserved-cidr` range that is used for the internal DNS server. The address can't be the first address in the range, or the network address. For example, if `platform-reserved-cidr` is set to `10.2.0.0/16`, then `platform-reserved-dns-ip` can't be `10.2.0.0` (the network address), or `10.2.0.1` (infrastructure reserves use of this IP). In this case, the first usable IP for the DNS would be `10.2.0.2`. |
 | `docker-bridge-cidr` | The address range assigned to the Docker bridge network. This range must have a size between `/28` and `/12`. |
 
-- The `platform-reserved-cidr` and `docker-bridge-cidr` address ranges can't conflict with each other, or with the ranges of either provided subnet. Further, make sure these ranges don't conflict with any other address range in the VNET.
+- The `platform-reserved-cidr` and `docker-bridge-cidr` address ranges can't conflict with each other, or with the ranges of either provided subnet. Further, make sure these ranges don't conflict with any other address range in the VNet.
 
-- If these properties aren’t provided, the CLI autogenerates the range values based on the address range of the VNET to avoid range conflicts.
+- If these properties aren’t provided, the CLI autogenerates the range values based on the address range of the VNet to avoid range conflicts.
 
 # [Azure PowerShell](#tab/azure-powershell)
 
@@ -374,17 +367,17 @@ You must either provide values for all three of these properties, or none of the
 | `VnetConfigurationPlatformReservedDnsIP` | An IP address from the `VnetConfigurationPlatformReservedCidr` range that is used for the internal DNS server. The address can't be the first address in the range, or the network address. For example, if `VnetConfigurationPlatformReservedCidr` is set to `10.2.0.0/16`, then `VnetConfigurationPlatformReservedDnsIP` can't be `10.2.0.0` (the network address), or `10.2.0.1` (infrastructure reserves use of this IP). In this case, the first usable IP for the DNS would be `10.2.0.2`. |
 | `VnetConfigurationDockerBridgeCidr` | The address range assigned to the Docker bridge network. This range must have a size between `/28` and `/12`. |
 
-- The `VnetConfigurationPlatformReservedCidr` and `VnetConfigurationDockerBridgeCidr` address ranges can't conflict with each other, or with the ranges of either provided subnet. Further, make sure these ranges don't conflict with any other address range in the VNET.
+- The `VnetConfigurationPlatformReservedCidr` and `VnetConfigurationDockerBridgeCidr` address ranges can't conflict with each other, or with the ranges of either provided subnet. Further, make sure these ranges don't conflict with any other address range in the VNet.
 
-- If these properties aren’t provided, the range values are autogenerated based on the address range of the VNET to avoid range conflicts.
+- If these properties aren’t provided, the range values are autogenerated based on the address range of the VNet to avoid range conflicts.
 
 ---
 
 ::: zone-end
 
 ## Clean up resources
 
-If you're not going to continue to use this application, you can delete the Azure Container Apps instance and all the associated services by removing the **my-container-apps** resource group.  Deleting this resource group removes the resource group automatically created by the Container Apps service containing the custom network components.
+If you're not going to continue to use this application, you can delete the **my-container-apps** resource group. This deletes the Azure Container Apps instance and all associated services. It also deletes the resource group that the Container Apps service automatically created and which contains the custom network components.
 
 ::: zone pivot="azure-cli"
 
@@ -409,7 +402,7 @@ Remove-AzResourceGroup -Name $ResourceGroupName -Force
 
 ## Additional resources
 
-- To use VNET-scope ingress, you must set up [DNS](./networking.md#dns).
+- To use VNet-scope ingress, you must set up [DNS](./networking.md#dns).
 
 ## Next steps