Skip to content

Commit a200d4c

Browse files
committed
edits
1 parent bea4594 commit a200d4c

File tree

3 files changed

+8
-7
lines changed

3 files changed

+8
-7
lines changed

articles/container-instances/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@
5151
href: container-instances-orchestrator-relationship.md
5252
- name: Security considerations
5353
href: container-instances-image-security.md
54-
- name: Virtual network considerations
54+
- name: Virtual networking
5555
href: container-instances-virtual-network-concepts.md
5656
- name: How-to guides
5757
items:

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,19 @@
11
---
2-
title: About using Azure Virtual Network
3-
description: Scenarios, limitations, and resources to deploy container groups to an Azure virtual network.
2+
title: Scenarios to use a virtual network
3+
description: Scenarios, resources, and limitations to deploy container groups to an Azure virtual network.
44
ms.topic: article
55
ms.date: 04/20/2020
66
ms.author: danlep
77

88
---
99

10-
# Virtual network background and scenarios
10+
# Virtual network scenarios and resources
1111

1212
[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.
1313

1414
For deployment information, see:
1515

16-
*[Deploy container instances into an Azure virtual network](container-instances-vnet.md).
16+
* [Deploy container instances into an Azure virtual network](container-instances-vnet.md).
1717
* [Regions and resource availability](container-instances-region-availability.md#availability---virtual-network-deployment) for container group deployments to a virtual network
1818

1919
## Scenarios
@@ -79,4 +79,5 @@ In the following diagram, several container groups have been deployed to a subne
7979

8080
<!-- LINKS - Internal -->
8181
[az-container-create]: /cli/azure/container#az-container-create
82+
[az-network-profile-list]: /cli/azure/network/profile#az-network-profile-list
8283

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Examples in this article are formatted for the Bash shell. If you prefer another
1616

1717
For background, see:
1818

19-
* [Virtual network scenarios, limitations, and resources for Azure Container Instances](container-instances-virtual-network-concepts.md)
19+
* [Virtual network scenarios and resources for Azure Container Instances](container-instances-virtual-network-concepts.md)
2020
* [Regions and resource availability](container-instances-region-availability.md#availability---virtual-network-deployment) for container group deployments to a virtual network.
2121

2222
> [!IMPORTANT]
@@ -52,7 +52,7 @@ az container create \
5252

5353
When you deploy to a new virtual network by using this method, the deployment can take a few minutes while the network resources are created. After the initial deployment, additional container group deployments to the same subnet complete more quickly.
5454

55-
### Deploy to existing virtual network
55+
## Deploy to existing virtual network
5656

5757
To deploy a container group to an existing virtual network:
5858

0 commit comments

Comments
 (0)