Merge pull request #293151 from mbender-ms/lb-use-cases

virtual network manager | Maintenance | Update concept-use-cases.md

Author: prmerger-automator[bot]

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

@@ -4,7 +4,7 @@ description: This article covers common use cases for customers who use Azure Vi
 author: mbender-ms
 ms.author: mbender
 ms.topic: overview 
-ms.date: 10/31/2024
+ms.date: 01/16/2025
 ms.custom: template-overview
 ms.service: azure-virtual-network-manager
 # Customer Intent: As a network admin, I need to know when I should use Azure Virtual Network Manager in my organization for managing virtual networks across my organization in a scalable, flexible, and secure manner with minimal administrative overhead.
@@ -22,6 +22,8 @@ You can use a connectivity configuration to create various network topologies ba
 
 When you deploy a [mesh topology](concept-connectivity-configuration.md#mesh-network-topology), all virtual networks have direct connectivity with each other. They don't need to go through other hops on the network to communicate. A mesh topology is useful when all the virtual networks need to communicate directly with each other.
 
+One common scenario is to mesh specific spoke virtual networks to boost latency and throughput. You don't have to mesh all the spoke virtual networks. You can also mesh spoke VNets connected to VWAN hubs, which allow for direct communication and better latency while still using the hubs to communicate with other virtual networks.
+
 ### Hub-and-spoke topology
 
 We recommend a [hub-and-spoke topology](concept-connectivity-configuration.md#hub-and-spoke-topology) 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.