Merge pull request #202285 from tomvcassidy/issue94486

Virtual Networking Additional Limitation

Author: PRMerger4

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

@@ -40,12 +40,13 @@ Container groups deployed into an Azure virtual network enable scenarios like:
 
 * 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.
+* To deploy container groups to a subnet, the subnet and the container group must be on the same Azure subscription.
 * 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, deployments to a virtual network are typically slower than deploying a standard container instance.
 * Outbound connection to port 25 is not supported at this time.
 * If you are connecting your container group to an Azure Storage Account, you must add a [service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) to that resource.
-* [IPv6 addresses](../virtual-network/ip-services/ipv6-overview.md) are not supported at this time. 
+* [IPv6 addresses](../virtual-network/ip-services/ipv6-overview.md) are not supported at this time
 
 ## Required network resources