Skip to content

Commit 78c3853

Browse files
committed
fine tuning per suggestions
1 parent a2912e0 commit 78c3853

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/virtual-network-manager/concept-use-cases.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,14 +24,13 @@ Learn about use cases for Azure Virtual Network Manager including managing conne
2424
Connectivity configuration allows you to create different network topologies based on your network needs. You create a connectivity configuration by adding new or existing virtual networks into [network groups](concept-network-groups.md) and creating a topology that meets your needs. The connectivity configuration offers three topology options: mesh, hub and spoke, or hub and spoke with direct connectivity.
2525

2626
### Mesh topology
27-
When a mesh topology is deployed, all virtual networks have direct connectivity with each other. They don't need to go through other hops on the network to communicate. This topology is recommended when you don't have central infrastructure resources like Azure Private DNS deployed in a hub virtual network.
28-
27+
When a mesh topology is deployed, all virtual networks have direct connectivity with each other. They don't need to go through other hops on the network to communicate. Mesh topology is useful when all the virtual networks need to communicate directly with each other.
2928

3029
### Hub and spoke topology
3130
Hub and spoke topology is recommended when you're deploying central infrastructure services in a hub virtual network that are shared by spoke virtual networks. This topology can be more efficient than having these common components in all spoke virtual networks.
3231

3332
### Hub and spoke topology with direct connectivity
34-
This topology combines the two above topologies. It's recommended when you have common central infrastructure in the hub, and you want direct communication between all spokes. Direct connectivity helps you reduce the latency caused additional network hops for traffic going through a hub.
33+
This topology combines the two above topologies. It's recommended when you have common central infrastructure in the hub, and you want direct communication between all spokes. Direct connectivity helps you reduce the latency caused by extra network hops when going through a hub.
3534

3635
### Maintaining topology
3736
AVNM automatically maintains the desired topology you defined in the connectivity configuration when changes are made to your infrastructure. For example, when you add new spoke to the topology, AVNM can handle the changes necessary to create the connectivity to the spoke and its virtual networks.

0 commit comments

Comments
 (0)