Merge pull request #279329 from mbender-ms/avnm-updates-FYH2

virtual network manager - Quickstart and Create-Instance includes image updates

Author: JamesJBarnett

articles/virtual-network-manager/create-virtual-network-manager-portal.md

@@ -20,7 +20,7 @@ In this quickstart, you deploy three virtual networks and use Azure Virtual Netw
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- To modify dynamic network groups, you must be [granted access via Azure RBAC role](concept-network-groups.md#network-groups-and-azure-policy) assignment only. Classic Admin/legacy authorization is not supported.
+- To modify dynamic network groups, you must be [granted access via Azure RBAC role](concept-network-groups.md#network-groups-and-azure-policy) assignment only. Classic Admin/legacy authorization isn't supported.
 
 [!INCLUDE [virtual-network-manager-create-instance](../../includes/virtual-network-manager-create-instance.md)]
 
@@ -59,7 +59,7 @@ Create three virtual networks by using the portal. Each virtual network has a `n
     | ------- | ----- |
     | **Subscription** | Select the same subscription that you selected in step 2. |
     | **Resource group** | Select **rg-learn-eastus-001**. |
-    | **Name** | Enter **vnet-learn-prod-eastus-002** and **vnet-learn-test-eastus-003** for each additional virtual network. |
+    | **Name** | Enter **vnet-learn-prod-eastus-002** and **vnet-learn-test-eastus-003** for the other virtual networks. |
     | **Region** | Select **(US) East US**. |
     | **vnet-learn-prod-eastus-002 IP addresses** | IPv4 address space: **10.1.0.0/16** </br> Subnet name: **default** </br> Subnet address space: **10.1.0.0/24**|
     | **vnet-learn-test-eastus-003 IP addresses** | IPv4 address space: **10.2.0.0/16** </br> Subnet name: **default** </br> Subnet address space: **10.2.0.0/24**|
@@ -68,19 +68,7 @@ Create three virtual networks by using the portal. Each virtual network has a `n
 
 Virtual Network Manager applies configurations to groups of virtual networks by placing them in network groups. To create a network group:
 
-1. Browse to the **rg-learn-eastus-001** resource group, and select the **vnm-learn-eastus-001** Virtual Network Manager instance.
-
-1. Under **Settings**, select **Network groups**. Then select **Create**.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/add-network-group-2.png" alt-text="Screenshot of an empty list of network groups and the button for creating a network group.":::
-
-1. On the **Create a network group** pane, enter **ng-learn-prod-eastus-001** and select **Create**.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/create-network-group.png" alt-text="Screenshot of the pane for creating a network group."  lightbox="./media/create-virtual-network-manager-portal/create-network-group.png":::
-
-1. Confirm that the new network group is now listed on the **Network groups** pane.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/network-groups-list.png" alt-text="Screenshot of a newly created network group on the pane that list network groups.":::
+[!INCLUDE [virtual-network-manager-create-network-group](../../includes/virtual-network-manager-create-network-group.md)]
 
 ## Define membership for a connectivity configuration
 
@@ -92,7 +80,7 @@ After you create your network group, you add virtual networks as members. Choose
 
 In this task, you manually add two virtual networks for your mesh configuration to your network group:
 
-1. From the list of network groups, select **ng-learn-prod-eastus-001**.  On the **ng-learn-prod-eastus-001** pane, under **Manually add members**, select **Add virtual networks**.
+1. From the list of network groups, select **ng-learn-prod-eastus-001**. On the **ng-learn-prod-eastus-001** pane, under **Manually add members**, select **Add virtual networks**.
 
     :::image type="content" source="./media/create-virtual-network-manager-portal/add-static-member.png" alt-text="Screenshot of add a virtual network f.":::
 
@@ -110,7 +98,7 @@ In this task, you manually add two virtual networks for your mesh configuration
 
 By using [Azure Policy](concept-azure-policy-integration.md), you define a condition to dynamically add two virtual networks to your network group when the name of the virtual network includes *prod*:
 
-1. From the list of network groups, select **ng-learn-prod-eastus-001**.  Under **Create policy to dynamically add members**, select **Create Azure policy**.
+1. From the list of network groups, select **ng-learn-prod-eastus-001**. Under **Create policy to dynamically add members**, select **Create Azure policy**.
 
     :::image type="content" source="media/create-virtual-network-manager-portal/define-dynamic-membership.png" alt-text="Screenshot of the button for creating an Azure policy.":::
 
@@ -126,21 +114,21 @@ By using [Azure Policy](concept-azure-policy-integration.md), you define a condi
     | **Operator** | Select **Contains** from the dropdown list.|
     | **Condition** | Enter **-prod**. |
 
-1. The **Effective virtual networks** pane shows the virtual networks that will be added to the network group based on the conditions that you defined in Azure Policy. When you're ready, select **Close**.
+2. The **Effective virtual networks** pane shows the virtual networks for addition to the network group based on the defined conditions in Azure Policy. When you're ready, select **Close**.
 
     :::image type="content" source="media/create-virtual-network-manager-portal/effective-virtual-networks.png" alt-text="Screenshot of the pane for effective virtual networks.":::
 
-1. Select **Save** to deploy the group membership. It can take up to one minute for the policy to take effect and be added to your network group.
+3. Select **Save** to deploy the group membership. It can take up to one minute for the policy to take effect and be added to your network group.
 
-1. On the **Network Group** pane, under **Settings**, select **Group members** to view the membership of the group based on the conditions that you defined in Azure Policy. Confirm that **Source** is listed as **azpol-learn-prod-eastus-001 - subscriptions/subscription_id**.
+4. On the **Network Group** pane, under **Settings**, select **Group members** to view the membership of the group based on the conditions that you defined in Azure Policy. Confirm that **Source** is listed as **azpol-learn-prod-eastus-001 - subscriptions/subscription_id**.
 
     :::image type="content" source="media/create-virtual-network-manager-portal/group-members-list.png" alt-text="Screenshot of listed group members with a configured source." lightbox="media/create-virtual-network-manager-portal/group-members-list.png":::
 
 ---
 
 ## Create a configuration
 
-Now that you've created the network group and given it the correct virtual networks, create a mesh network topology configuration. Replace `<subscription_id>` with your subscription.
+Now that you created the network group and updated its membership with virtual networks, you create a mesh network topology configuration. Replace `<subscription_id>` with your subscription.
 
 1. Under **Settings**, select **Configurations**. Then select **Create**.
 
@@ -157,7 +145,7 @@ Now that you've created the network group and given it the correct virtual netwo
     | **Name** | Enter **cc-learn-prod-eastus-001**. |
     | **Description** | *(Optional)* Provide a description about this connectivity configuration. |
 
-1. On the **Topology** tab, select the **Mesh** topology if it's not selected, and leave the **Enable mesh connectivity across regions** checkbox cleared.  Cross-region connectivity isn't required for this setup, because all the virtual networks are in the same region. When you're ready, select **Add** > **Add network group**.
+1. On the **Topology** tab, select the **Mesh** topology, and leave the **Enable mesh connectivity across regions** checkbox cleared. Cross-region connectivity isn't required for this setup, because all the virtual networks are in the same region. When you're ready, select **Add** > **Add network group**.
 
      :::image type="content" source="./media/create-virtual-network-manager-portal/topology-configuration.png" alt-text="Screenshot of topology selection for network group connectivity configuration.":::
 
@@ -192,7 +180,7 @@ To apply your configurations to your environment, you need to commit the configu
     | Setting | Value |
     | ------- | ----- |
     | **Configurations** | Select **Include connectivity configurations in your goal state**. |
-    | **Connectivity configurations** | Select **cc-learn-prod-eastus-001**.  |
+    | **Connectivity configurations** | Select **cc-learn-prod-eastus-001**. |
     | **Target regions** | Select **East US** as the deployment region. |
 
 1. Select **Deploy** to complete the deployment.
@@ -272,7 +260,5 @@ If you no longer need Azure Virtual Network Manager, you can remove it after you
 
 ## Next steps
 
-Now that you've created an Azure Virtual Network Manager instance, learn how to block network traffic by using a security admin configuration:
-
 > [!div class="nextstepaction"]
 > [Block network traffic with Azure Virtual Network Manager](how-to-block-network-traffic-portal.md)

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
 ms.topic: how-to
-ms.date: 05/07/2024
+ms.date: 06/20/2024
 ms.custom: template-concept, engagement-fy23
 ---
 
@@ -23,18 +23,10 @@ In this article, you learn how to create a hub and spoke network topology with A
 
 This section helps you create a network group containing the virtual networks you're using for the hub-and-spoke network topology.
 
-1. Go to your Azure Virtual Network Manager instance. This how-to guide assumes you've created one using the [quickstart](create-virtual-network-manager-portal.md) guide.
-
-1. Select **Network Groups** under *Settings*, then select **+ Create**.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/add-network-group-2.png" alt-text="Screenshot of add a network group button.":::
-
-1. On the *Create a network group* page, enter a **Name** for the network group. This example uses the name **myNetworkGroup**. Select **Add** to create the network group.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/network-group-basics.png" alt-text="Screenshot of create a network group page.":::
+> [!NOTE]
+> This how-to guide assumes you created a network manager instance using the [quickstart](create-virtual-network-manager-portal.md) guide.
 
-1. The *Network Groups* page lists the new network group.
-    :::image type="content" source="./media/create-virtual-network-manager-portal/network-groups-list.png" alt-text="Screenshot of network group page with list of network groups.":::
+[!INCLUDE [virtual-network-manager-create-network-group](../../includes/virtual-network-manager-create-network-group.md)]
 
 ## Define network group members
 

articles/virtual-network-manager/how-to-create-mesh-network.md

@@ -23,18 +23,10 @@ In this article, you learn how to create a mesh network topology using Azure Vir
 
 This section helps you create a network group containing the virtual networks you're using for the mesh network topology.
 
-1. Go to your Azure Virtual Network Manager instance. This how-to guide assumes you've created one using the [quickstart](create-virtual-network-manager-portal.md) guide.
+> [!NOTE]
+> This how-to guide assumes you created a network manager instance using the [quickstart](create-virtual-network-manager-portal.md) guide.
 
-1. Select **Network Groups** under *Settings*, then select **+ Create**.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/add-network-group-2.png" alt-text="Screenshot of add a network group button.":::
-
-1. On the *Create a network group* page, enter a **Name** for the network group. This example uses the name **myNetworkGroup**. Select **Add** to create the network group.
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/network-group-basics.png" alt-text="Screenshot of create a network group page.":::
-
-1. The *Network Groups* page now lists the new network group.
-    :::image type="content" source="./media/create-virtual-network-manager-portal/network-groups-list.png" alt-text="Screenshot of network group page with list of network groups.":::
+[!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).

articles/virtual-network-manager/media/create-virtual-network-manager-portal/create-network-group.png

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
 ms.topic: tutorial
-ms.date: 08/01/2023
+ms.date: 06/26/2024
 ms.custom: FY23 content-maintenance, engagement-FY24
 ---
 
@@ -99,26 +99,16 @@ Deploy a virtual network gateway into the hub virtual network. This virtual netw
 
 1. Select **Review + create** and then select **Create** after validation has passed. The deployment of a virtual network gateway can take about 30 minutes. You can move on to the next section while waiting for this deployment to complete. However, you may find **gw-learn-hub-eastus-001** doesn't display that it has a gateway due to timing and sync across the Azure portal.
 
-## Create a dynamic network group
+## Create a network group
 
-1. Go to your Azure Virtual Network Manager instance. This tutorial assumes you've created one using the [quickstart](create-virtual-network-manager-portal.md) guide. The network group in this tutorial is called **ng-learn-prod-eastus-001**.
+> [!NOTE]
+> This how-to guide assumes you created a network manager instance using the [quickstart](create-virtual-network-manager-portal.md) guide. The network group in this tutorial is called **ng-learn-prod-eastus-001**.
 
-1. Select **Network groups** under *Settings*, and then select **+ Create** to create a new network group.
+[!INCLUDE [virtual-network-manager-create-network-group](../../includes/virtual-network-manager-create-network-group.md)]
 
-    :::image type="content" source="./media/create-virtual-network-manager-portal/add-network-group-2.png" alt-text="Screenshot of add a network group button.":::
+## Define dynamic group membership with Azure policy
 
-1. On the **Create a network group** screen, enter the following information:
-
-    :::image type="content" source="./media/create-virtual-network-manager-portal/create-network-group.png" alt-text="Screenshot of the Basics tab on Create a network group page.":::
-
-    | Setting | Value |
-    | ------- | ----- |
-    | Name | Enter **ng-learn-prod-eastus-001** for the network group name. |
-    | Description | Provide a description about this network group. |
-
-1. Select **Create** to create the virtual network group.
-1. From the **Network groups** page, select the created network group from above to configure the network group.
-1. On the **Overview** page, select **Create Azure Policy** under *Create policy to dynamically add members*.
+1. From the list of network groups, select **ng-learn-prod-eastus-001**. Under **Create policy to dynamically add members**, select **Create Azure policy**.
 
     :::image type="content" source="./media/tutorial-create-secured-hub-and-spoke/define-dynamic-membership.png" alt-text="Screenshot of the defined dynamic membership button.":::