Skip to content

Commit 4702f50

Browse files
authored
Update container-instances-vnet.md
1 parent b5a5e2c commit 4702f50

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,11 +62,10 @@ When you deploy to a new virtual network by using this method, the deployment ca
6262

6363
To deploy a container group to an existing virtual network:
6464

65-
1. Create a subnet within your existing virtual network, use an existing subnet in which a container group is already deployed, or use an existing subnet emptied of *all* other resources and configuration.
65+
1. Create a subnet within your existing virtual network, use an existing subnet in which a container group is already deployed, or use an existing subnet emptied of *all* other resources and configuration.The subnet that you use for container groups can contain only container groups. Before you deploy a container group to a subnet, you must explicitly delegate the subnet before provisioning. Once delegated, the subnet can be used only for container groups. If you attempt to deploy resources other than container groups to a delegated subnet, the operation fails.
6666
1. Deploy a container group with [az container create][az-container-create] and specify one of the following:
6767
* Virtual network name and subnet name
6868
* Virtual network resource ID and subnet resource ID, which allows using a virtual network from a different resource group
69-
* Network profile name or ID, which you can obtain using [az network profile list][az-network-profile-list]
7069

7170
### Example
7271

0 commit comments

Comments
 (0)