Merge pull request #302647 from andreamichaelmsft/andrea-branch-5

[Azure Doc-a-thon] Updated all connectivity config pages

Author: JamesJBarnett

articles/virtual-network-manager/concept-connectivity-configuration.md

@@ -20,7 +20,7 @@ You can use a connectivity configuration to create various network topologies ba
 
 ### Mesh topology
 
-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.
+When you deploy a [mesh topology](concept-connectivity-configuration.md#mesh-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.
 

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

@@ -1,49 +1,52 @@
 ---
-title: 'Create a hub and spoke topology in Azure - Portal'
-description: Learn how to create a hub and spoke network topology for multiple virtual networks with Azure Virtual Network Manager using the Azure portal.
+title: 'Create a hub-and-spoke topology in Azure - Portal'
+description: Learn how to create a hub-and-spoke network topology for multiple virtual networks with Azure Virtual Network Manager using the Azure portal.
 author: mbender-ms
 ms.author: mbender
 ms.service: azure-virtual-network-manager
 ms.topic: how-to
-ms.date: 10/23/2024
+ms.date: 07/11/2025
 ms.custom: template-concept, engagement-fy23
 ---
 
-# Create a hub and spoke topology in Azure - Portal
+# Create a hub-and-spoke topology in Azure - Portal
 
-In this article, you learn how to create a hub and spoke network topology with Azure Virtual Network Manager. With this configuration, you select a virtual network to act as a hub and all spoke virtual networks have bi-directional peering with only the hub by default. You also can enable direct connectivity between spoke virtual networks and enable the spoke virtual networks to use the virtual network gateway in the hub.
+In this article, you learn how to create a hub-and-spoke topology with Azure Virtual Network Manager. With this configuration, you select a virtual network to act as a hub and all spoke virtual networks have bi-directional peering with only the hub by default. You also can enable direct connectivity between spoke virtual networks in the same spoke network group and enable the spoke virtual networks to use the gateway in the hub virtual network.
 
 ## Prerequisites
 
-* Read about [Hub-and-spoke](concept-connectivity-configuration.md#hub-and-spoke-topology) network topology.
-* Created a [Azure Virtual Network Manager instance](create-virtual-network-manager-portal.md#create-a-virtual-network-manager-instance).
-* Identify virtual networks you want to use in the hub-and-spokes configuration or create new [virtual networks](../virtual-network/quick-create-portal.md). 
+* Read about the [Hub-and-spoke](concept-connectivity-configuration.md#hub-and-spoke-topology) network topology.
+* Create an [Azure Virtual Network Manager instance](create-virtual-network-manager-portal.md#create-a-virtual-network-manager-instance).
+* Identify the virtual networks you want to use in the hub-and-spoke configuration or create new [virtual networks](../virtual-network/quick-create-portal.md). 
 
 ## <a name="group"></a> Create a network group
 
-This section helps you create a network group containing the virtual networks you're using for the hub-and-spoke network topology.
+This section helps you create a network group containing the virtual networks you're using as the spokes for the hub-and-spoke topology.
 
 > [!NOTE]
-> This how-to guide assumes you created a network manager instance using the [quickstart](create-virtual-network-manager-portal.md) guide.
+> This how-to guide assumes you created an Azure Virtual Network Manager instance using the [quickstart](create-virtual-network-manager-portal.md) guide.
 
 [!INCLUDE [virtual-network-manager-create-network-group](../../includes/virtual-network-manager-create-network-group.md)]
 
 ## Define network group members
 
-Azure Virtual Network manager allows you two methods for adding membership to a network group. You can manually add virtual networks or use Azure Policy to dynamically add virtual networks based on conditions. This how-to covers [manually adding membership](concept-network-groups.md#static-membership). For information on defining group membership with Azure Policy, see [Define network group membership with Azure Policy](concept-network-groups.md#dynamic-membership).
+Azure Virtual Network Manager provides you with two methods for adding membership to a network group. You can manually add virtual networks or use Azure Policy to conditionally add virtual networks to the network group. This how-to [manually adds membership](concept-network-groups.md#static-membership). For information on defining group membership with Azure Policy, see [Define network group membership with Azure Policy](concept-network-groups.md#dynamic-membership).
 
 ### Manually adding virtual networks
-To manually add the desired virtual networks for your Mesh configuration to your Network Group, follow the steps below:
+
+To manually add the desired virtual networks to your network group for use in your connectivity configuration, follow these steps:
 
 1. From the list of network groups, select your network group and select **Add virtual networks** under *Manually add members* on the network group page.
 
-1. On the *Manually add members* page, select all the virtual networks and select **Add**.
+1. On the *Manually add members* pane, select all desired virtual networks and select **Add**.
+
+1. To review the network group membership that you manually added, select **Group Members** on the *Network Group* page under **Settings**.
 
-1. To review the network group membership manually added, select **Group Members** on the *Network Group* page under **Settings**.
+## Create a hub-and-spoke connectivity configuration
 
-## Create a hub and spoke connectivity configuration
+This section guides you through creating a hub-and-spoke configuration with the network group you created in the previous section.
 
-This section guides you through how to create a hub-and-spoke configuration with the network group you created in the previous section.
+1. Select **Configurations** under *Settings*, then select **+ Create**.
 
 1. Select **Connectivity configuration** from the drop-down menu to begin creating a connectivity configuration.
 
@@ -52,53 +55,59 @@ This section guides you through how to create a hub-and-spoke configuration with
     | Setting | Value |
     | ------- | ----- |
     | Name | Enter a *name* for this configuration. |
-    | Description | *Optional* Enter a description about what this configuration does. |
+    | Description | *(Optional)* Enter a description about what this configuration does. |
 
 1. On the **Topology** tab, select the **Hub and spoke** topology under *Topology*.
 
-1. Select **Delete existing peerings** checkbox if you want to remove all previously created virtual network peering between virtual networks in the network group defined in this configuration,  and then select **Select a hub**.
-1. On the **Select a hub** page, Select the virtual network that will be the hub virtual network and select **Select**.
+1. Select the **Delete existing peerings** checkbox if you want to remove all previously created virtual network peerings between virtual networks in the network groups included in this configuration. Then select **Select a hub**.
+
+1. On the **Select a hub** pane, select the virtual network intended as the hub virtual network and select **Select**.
 
-1. Then select **+ Add network groups**. 
+1. Select **+ Add network groups**. 
 
-1. On the **Add network groups** page, select the network groups you want to add to this configuration. Then select **Add** to save.
+1. On the **Add network groups** page, select the network groups you want to add to this configuration as spokes. Then select **Add** to save.
 
-1. Select the settings you want to enable for each network group. The following three options appear next to the network group name under **Spoke network groups**:
+1. Select the settings you want to enable for each spoke network group. The following three options appear next to each network group name under **Spoke network groups**:
 
-    - *Direct connectivity*: Select **Enable peering within network group** if you want to establish virtual network peering between virtual networks in the network group of the same region.
-    - *Global Mesh*: Select **Enable mesh connectivity across regions** if you want to establish virtual network peering for all virtual networks in the network group across regions.
-    - *Gateway*: Select **Use hub as a gateway** if you have a virtual network gateway in the hub virtual network that you want this network group to use to pass traffic to on-premises.
+    - *Direct connectivity*: Select **Enable peering within network group** if you want to establish connectivity between virtual networks in the network group. By default, this connectivity will only be established between virtual networks in this network group that belong to the same region.
+    - *Global Mesh*: This option is only selectable if *direct connectivity* is enabled. Select **Enable mesh connectivity across regions** if you want to establish connectivity across regions for all virtual networks in this network group.
+    - *Gateway*: Select **Use hub as a gateway** if you have a virtual network gateway in the hub virtual network that you want the virtual networks of this spoke network group to use to pass traffic to on-premises.
 
 1. Select **Review + Create > Create** to create the hub-and-spoke connectivity configuration.
 
-## Deploy the hub and spoke configuration
+## Deploy the hub-and-spoke configuration
 
-To have this configuration take effect in your environment, you need to deploy the configuration to the regions where your selected virtual networks are created.
+To have this configuration take effect in your environment, you need to deploy the configuration to the regions in which your selected virtual networks reside.
 
 1. Select **Deployments** under *Settings*, then select **Deploy a configuration**.
+
 1. On the **Deploy a configuration** page, select the following settings:
 
     | Setting | Value |
     | ------- | ----- |
     | Configurations | Select **Include connectivity configurations in your goal state** . |
     | Connectivity configurations | Select the name of the configuration you created in the previous section. |
-    | Target regions | Select all the regions that apply to virtual networks you select for the configuration. |
+    | Target regions | Select all the regions that apply to virtual networks you select for the configuration. You might choose to select a subset of regions at a time if you want to gradually roll out this configuration. |
 
 1. Select **Next** and then select **Deploy** to complete the deployment.
-1. The deployment displays in the list for the selected region. The deployment of the configuration can take a few minutes to complete.
+
+1. The deployment displays in the list for the selected region. The deployment of the configuration can take a few minutes to complete. Select the **Refresh** button to check on the status of the deployment.
 
     :::image type="content" source="./media/how-to-create-hub-and-spoke/deployment-succeeded.png" alt-text="Screenshot of configuration deployment in progress status.":::
 
 > [!NOTE]
-> If you're currently using peering and want to manage topology and connectivity with Azure Virtual Network Manager, you can migrate without any downtime to your network. Virtual network manager instances are fully compatible with pre-existing hub and spoke topology deployment using peering. This means that you won't need to delete any existing peered connections between the spokes and the hub as the network manager will automatically detect and manage them.
+> If you're currently using virtual network peerings created outside of Azure Virtual Network Manager and want to manage your topology and connectivity with Azure Virtual Network Manager, you can migrate without any downtime to your network. Azure Virtual Network Manager instances are fully compatible with preexisting hub-and-spoke topology deployments using manual peerings. When you deploy a connectivity configuration, the connectivity established is additive by default. This means that you aren't required to delete any existing peered connections between the hub and spoke virtual networks while you verify the connectivity configuration is establishing connectivity as desired.
 
 ## Confirm configuration deployment
 
-1. See [view applied configuration](how-to-view-applied-configurations.md).
+1. See [view applied configurations](how-to-view-applied-configurations.md).
 
-1. To test *direct connectivity* between spokes, deploy a virtual machine into each spokes virtual network. Then initiate an ICMP request from one virtual machine to the other.
+1. To test *direct connectivity* between spoke virtual networks, deploy a virtual machine into each spoke virtual network. Then initiate an ICMP request from one virtual machine to the other.
 
 ## Next steps
 
+- [Create a secured hub-and-spoke topology in this tutorial](tutorial-create-secured-hub-and-spoke.md).
+- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
+- [Learn how to create a mesh connectivity configuration](how-to-create-mesh-network.md).
 - Learn about [Security admin rules](concept-security-admins.md)
-- Learn how to block network traffic with a [SecurityAdmin configuration](how-to-block-network-traffic-portal.md).
+- Learn how to block network traffic with a [Security admin configuration](how-to-block-network-traffic-portal.md).

articles/virtual-network-manager/how-to-create-hub-and-spoke.md

@@ -15,7 +15,7 @@ In this article, you'll learn how to create a mesh network topology with Azure V
 
 ## Prerequisites
 
-* Read about [mesh](concept-connectivity-configuration.md#mesh-network-topology) network topology.
+* Read about [mesh](concept-connectivity-configuration.md#mesh-topology) network topology.
 * Created a [Azure Virtual Network Manager instance](create-virtual-network-manager-powershell.md#create-a-virtual-network-manager-instance).
 * Identify virtual networks you want to use in the mesh configuration or create new [virtual networks](../virtual-network/quick-create-powershell.md).
 * Version `5.3.0` of `Az.Network` is required to access the required cmdlets for Azure Virtual Network Manager.