vnet ga updates

Author: dlepow

articles/container-instances/container-instances-region-availability.md

@@ -2,7 +2,7 @@
 title: Resource availability by region
 description: Availability of compute and memory resources for the Azure Container Instances service in different Azure regions.
 ms.topic: article
-ms.date: 02/19/2020
+ms.date: 04/27/2020
 ms.author: danlep
 
 ---

articles/container-instances/container-instances-virtual-network-concepts.md

@@ -2,19 +2,16 @@
 title: Scenarios to use a virtual network
 description: Scenarios, resources, and limitations to deploy container groups to an Azure virtual network.
 ms.topic: article
-ms.date: 04/20/2020
+ms.date: 04/27/2020
 ms.author: danlep
 
 ---
 
 # Virtual network scenarios and resources
 
-[Azure Virtual Network](../virtual-network/virtual-networks-overview.md) provides secure, private networking for your Azure and on-premises resources. By deploying container groups into an Azure virtual network, your containers can communicate securely with other resources in the virtual network. This article provides background about virtual network scenarios, limitations, and resources.
+[Azure Virtual Network](../virtual-network/virtual-networks-overview.md) provides secure, private networking for your Azure and on-premises resources. By deploying container groups into an Azure virtual network, your containers can communicate securely with other resources in the virtual network. 
 
-For deployment information, see:
-
-* [Deploy container instances into an Azure virtual network](container-instances-vnet.md).
-* [Regions and resource availability](container-instances-region-availability.md#availability---virtual-network-deployment) for container group deployments to a virtual network
+This article provides background about virtual network scenarios, limitations, and resources. For deployment examples using the Azure CLI, see [Deploy container instances into an Azure virtual network](container-instances-vnet.md).
 
 ## Scenarios
 
@@ -23,8 +20,10 @@ Container groups deployed into an Azure virtual network enable scenarios like:
 * Direct communication between container groups in the same subnet
 * Send [task-based](container-instances-restart-policy.md) workload output from container instances to a database in the virtual network
 * Retrieve content for container instances from a [service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) in the virtual network
-* Container communication with on-premises resources through a [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md) or [ExpressRoute](../expressroute/expressroute-introduction.md)
+* Enable container communication with on-premises resources through a [VPN gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md) or [ExpressRoute](../expressroute/expressroute-introduction.md)
 * Integrate with [Azure Firewall](../firewall/overview.md) to identify outbound traffic originating from the container 
+* Resolve names via the internal Azure DNS for communication with Azure resources in the virtual network, such as virtual machines
+* Use NSG rules to control container access to subnets or other network resources
 
 ## Unsupported networking scenarios 
 
@@ -34,14 +33,20 @@ Container groups deployed into an Azure virtual network enable scenarios like:
   * Global virtual network peering (connecting virtual networks across Azure regions) is not supported
 * **Private link** - Accessing Azure resources at a private endpoint over a private link is not supported
 * **Public IP or DNS label** - Container groups deployed to a virtual network don't currently support exposing containers directly to the internet with a public IP address or a fully qualified domain name
-* **Internal name resolution** - Name resolution for Azure resources in the virtual network via the internal Azure DNS is not supported
 
 ## Other limitations
 
+* Currently, only Linux containers are supported in a container group deployed to a virtual network.
 * To deploy container groups to a subnet, the subnet can't contain other resource types. Remove all existing resources from an existing subnet prior to deploying container groups to it, or create a new subnet.
 * You can't use a [managed identity](container-instances-managed-identity.md) in a container group deployed to a virtual network.
 * You can't enable a [liveness probe](container-instances-liveness-probe.md) or [readiness probe](container-instances-readiness-probe.md) in a container group deployed to a virtual network.
-* Due to the additional networking resources involved, deploying a container group to a virtual network is typically slower than deploying a standard container instance.
+* Due to the additional networking resources involved, deployments to a virtual network are typically slower than deploying a standard container instance.
+
+## Where to deploy
+
+The following regions and maximum resources are available to deploy a container group in an Azure virtual network.
+
+[!INCLUDE [container-instances-vnet-limits](../../includes/container-instances-vnet-limits.md)]
 
 ## Required network resources
 

articles/container-instances/container-instances-vnet.md

@@ -1,8 +1,8 @@
 ---
 title: Deploy container group to Azure virtual network
-description: Learn how to deploy a container group to a new or existing Azure virtual network.
+description: Learn how to deploy a container group to a new or existing Azure virtual network by using the Azure command-line interface.
 ms.topic: article
-ms.date: 04/20/2020
+ms.date: 04/27/2020
 ms.author: danlep
 ---
 
@@ -12,15 +12,13 @@ ms.author: danlep
 
 This article shows how to use the [az container create][az-container-create] command in the Azure CLI to deploy container groups to either a new virtual network or an existing virtual network. 
 
-Examples in this article are formatted for the Bash shell. If you prefer another shell such as PowerShell or Command Prompt, adjust the line continuation characters accordingly.
+For networking scenarios and limitations, see [Virtual network scenarios and resources for Azure Container Instances](container-instances-virtual-network-concepts.md).
 
-For background, see:
+> [!IMPORTANT]
+> Container group deployment to a virtual network is generally available for Linux containers, in most regions where Azure Container Instances is available. For details, see [Regions and resource availability](container-instances-virtual-network-concepts#where-to-deploy). 
 
-* [Virtual network scenarios and resources for Azure Container Instances](container-instances-virtual-network-concepts.md)
-* [Regions and resource availability](container-instances-region-availability.md#availability---virtual-network-deployment) for container group deployments to a virtual network.
+Examples in this article are formatted for the Bash shell. If you prefer another shell such as PowerShell or Command Prompt, adjust the line continuation characters accordingly.
 
-> [!IMPORTANT]
-> Container group deployments to a virtual network are generally available for production workloads only in the following regions: **East US, South Central US, and West US 2**. 
 
 ## Deploy to new virtual network
 

includes/container-instances-vnet-limits.md

@@ -2,15 +2,14 @@
 author: dlepow
 ms.service: container-instances
 ms.topic: include
-ms.date: 01/31/2020
+ms.date: 04/27/2020
 ms.author: danlep
 ---
 ### Regions and resource availability
 
 | Regions | OS | Max CPU | Max Memory (GB) | Storage (GB) |
 | -------- | :---: | :---: | :-----------: | :---: |
-| Australia East, Canada Central, Central US, East US<sup>1</sup>, East US 2, North Europe, South Central US<sup>1</sup>, Southeast Asia, West Europe, West US 2<sup>1</sup> | Linux | 4 | 16 | 50 |
+| Australia East, Canada Central, Central US, East US, East US 2, North Europe, South Central US, Southeast Asia, West Europe, West US 2 | Linux | 4 | 16 | 50 |
 | Japan East | Linux | 2 | 8 | 50 |
 | North Central US, South India, West US | Linux | 2 | 3.5 | 50 |
 
-<sup>1</sup>Region in which container group deployments to a virtual network are generally available for production workloads. In other regions, virtual network deployments are in preview.