Merge pull request #293014 from mbender-ms/avnm-qs-updates

virtual network manager | Major Updates & Freshness | Quickstarts

Author: v-shils

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

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: azure-virtual-network-manager
 ms.topic: quickstart
-ms.date: 10/22/2024
+ms.date: 1/13/2024
 ms.custom: template-quickstart, mode-api, engagement-fy23, devx-track-azurepowershell
 ---
 
@@ -20,8 +20,8 @@ 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).
-- Perform this quickstart by using PowerShell locally, not through Azure Cloud Shell. The version of *Az.Network* in Azure Cloud Shell does not currently support the Azure Virtual Network Manager cmdlets.
-- 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.
+- Perform this quickstart by using PowerShell locally, not through Azure Cloud Shell. The version of *Az.Network* in Azure Cloud Shell doesn't currently support the Azure Virtual Network Manager cmdlets.
+- 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.
 
 ## Sign in to your Azure account and select your subscription
 
@@ -47,11 +47,11 @@ Install the latest *Az.Network* Azure PowerShell module by using this command:
 
 ## Create a resource group
 
-Before you can create an Azure Virtual Network Manager instance, you have to create a resource group to host it. Create a resource group by using [New-AzResourceGroup](/powershell/module/az.Resources/New-azResourceGroup). This example creates a resource group named *resource-group* in the *West US 2* region:
+In this task, create a resource group to host a network manager instance. Create a resource group by using [New-AzResourceGroup](/powershell/module/az.Resources/New-azResourceGroup). This example creates a resource group named *resource-group* in the *West US 2* region:
 
 ```azurepowershell
 # Create a resource group
-$location = "West US 2"
+$location = "westus2"
 $rg = @{
     Name = 'resource-group'
     Location = $location
@@ -62,10 +62,10 @@ New-AzResourceGroup @rg
 
 ## Define the scope and access type
 
-Define the scope and access type for the Azure Virtual Network Manager instance by using [New-AzNetworkManagerScope](/powershell/module/az.network/new-aznetworkmanagerscope). This example defines a scope with a single subscription and sets the access type to *Connectivity*. Replace `<subscription_id>` with the ID of the subscription that you want to manage through Azure Virtual Network Manager.
+In this task, define the scope and access type for the Azure Virtual Network Manager instance by using [New-AzNetworkManagerScope](/powershell/module/az.network/new-aznetworkmanagerscope). This example defines a scope with a single subscription and sets the access type to *Connectivity*. Replace `<subscription_id>` with the ID of the subscription that you want to manage through Azure Virtual Network Manager.
 
 ```azurepowershell
-$subID= <subscription_id>
+$subID= "<subscription_id>"
 
 [System.Collections.Generic.List[string]]$subGroup = @()  
 $subGroup.Add("/subscriptions/$subID")
@@ -79,12 +79,12 @@ $scope = New-AzNetworkManagerScope -Subscription $subGroup
 
 ## Create a Virtual Network Manager instance
 
-Create a Virtual Network Manager instance by using [New-AzNetworkManager](/powershell/module/az.network/new-aznetworkmanager). This example creates an instance named *network-manager* in the *West US 2* region:
+In this task, create a Virtual Network Manager instance by using [New-AzNetworkManager](/powershell/module/az.network/new-aznetworkmanager). This example creates an instance named *network-manager* in the *(US) West US 2* region:
 
 ```azurepowershell
 $avnm = @{
     Name = 'network-manager'
-    ResourceGroupName = $rg.ResourceGroupName
+    ResourceGroupName = $rg.Name
     NetworkManagerScope = $scope
     NetworkManagerScopeAccess = $access
     Location = $location
@@ -94,81 +94,81 @@ $networkmanager = New-AzNetworkManager @avnm
 
 ## Create three virtual networks
 
-Create three virtual networks by using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). This example creates virtual networks named *vnet-spoke-001*, *vnet-spoke-002*, and *vnet-hub-001* in the *West US 2* region. If you already have virtual networks that you want create a mesh network with, you can skip to the next section.
+In this task, create three virtual networks by using [New-AzVirtualNetwork](/powershell/module/az.network/new-azvirtualnetwork). This example creates virtual networks named *vnet-00*, *vnet-01*, and *vnet-02* in the *(US) West US 2* region. If you already have virtual networks that you want create a mesh network with, you can skip to the next section.
 
 ```azurepowershell
-$vnetspoke001 = @{
-    Name = 'vnet-spoke-001'
-    ResourceGroupName = $rg.ResourceGroupName
+$vnet_00 = @{
+    Name = 'vnet-00'
+    ResourceGroupName = $rg.Name
     Location = $location
     AddressPrefix = '10.0.0.0/16'    
 }
 
-$vnet_spoke_001 = New-AzVirtualNetwork @vnetspoke001
+$vnet_00 = New-AzVirtualNetwork @vnet_00
 
-$vnetspoke002 = @{
-    Name = 'vnet-spoke-002'
-    ResourceGroupName = $rg.ResourceGroupName
+$vnet_01 = @{
+    Name = 'vnet-01'
+    ResourceGroupName = $rg.Name
     Location = $location
     AddressPrefix = '10.1.0.0/16'    
 }
-$vnet_spoke_002 = New-AzVirtualNetwork @vnetspoke002
+$vnet_01 = New-AzVirtualNetwork @vnet_01
 
-$vnethub001 = @{
-    Name = 'vnet-hub-001'
-    ResourceGroupName = $rg.ResourceGroupName
+$vnet_02 = @{
+    Name = 'vnet-02'
+    ResourceGroupName = $rg.Name
     Location = $location
     AddressPrefix = '10.2.0.0/16'    
 }
-$vnet_hub_001 = New-AzVirtualNetwork @vnethub001
+$vnet_02 = New-AzVirtualNetwork @vnet_02
 ```
 
 ### Add a subnet to each virtual network
 
-To complete the configuration of the virtual networks, create a subnet configuration named *default* with a subnet address prefix of */24* by using [Add-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/add-azvirtualnetworksubnetconfig). Then, use [Set-AzVirtualNetwork](/powershell/module/az.network/set-azvirtualnetwork) to apply the subnet configuration to the virtual network.
+In this task, create a subnet configuration named *default* with a subnet address prefix of */24* by using [Add-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/add-azvirtualnetworksubnetconfig). Then, use [Set-AzVirtualNetwork](/powershell/module/az.network/set-azvirtualnetwork) to apply the subnet configuration to the virtual network.
 
 ```azurepowershell
-$subnet_vnetspoke001 = @{
+$subnet_vnet_00 = @{
     Name = 'default'
-    VirtualNetwork = $vnet_spoke_001
+    VirtualNetwork = $vnet_00
     AddressPrefix = '10.0.0.0/24'
 }
-$subnetConfig_vnetspoke001 = Add-AzVirtualNetworkSubnetConfig @subnet_vnetspoke001
-$vnet_spoke_001 | Set-AzVirtualNetwork
+$subnetConfig_vnet_00 = Add-AzVirtualNetworkSubnetConfig @subnet_vnet_00
+$vnet_00 | Set-AzVirtualNetwork
 
-$subnet_vnetspoke002 = @{
+$subnet_vnet_01 = @{
     Name = 'default'
-    VirtualNetwork = $vnet_spoke_002
+    VirtualNetwork = $vnet_01
     AddressPrefix = '10.1.0.0/24'
 }
-$subnetConfig_vnetspoke002 = Add-AzVirtualNetworkSubnetConfig @subnet_vnetspoke002
-$vnet_spoke_002 | Set-AzVirtualNetwork
+$subnetConfig_vnet_01 = Add-AzVirtualNetworkSubnetConfig @subnet_vnet_01
+$vnet_01 | Set-AzVirtualNetwork
 
-$subnet_vnet_hub_001 = @{
+$subnet_vnet_02 = @{
     Name = 'default'
-    VirtualNetwork = $vnet_hub_001
+    VirtualNetwork = $vnet_02
     AddressPrefix = '10.2.0.0/24'
 }
-$subnetConfig_vnet_hub_001 = Add-AzVirtualNetworkSubnetConfig @subnet_vnet_hub_001
-$vnet_hub_001 | Set-AzVirtualNetwork
+$subnetConfig_vnet_02 = Add-AzVirtualNetworkSubnetConfig @subnet_vnet_02
+$vnet_02 | Set-AzVirtualNetwork
 ```
 
 ## Create a network group
 
-Virtual Network Manager applies configurations to groups of virtual networks by placing them in network groups. Create a network group by using [New-AzNetworkManagerGroup](/powershell/module/az.network/new-aznetworkmanagergroup). This example creates a network group named *network-group* in the West US 2 region:
+Virtual Network Manager applies configurations to groups of virtual networks by placing them in network groups. Create a network group by using [New-AzNetworkManagerGroup](/powershell/module/az.network/new-aznetworkmanagergroup). This example creates a network group named *network-group* in the *(US) West US 2* region:
 
 ```azurepowershell
 $ng = @{
         Name = 'network-group'
-        ResourceGroupName = $rg.ResourceGroupName
+        ResourceGroupName = $rg.Name
         NetworkManagerName = $networkManager.Name
     }
     $ng = New-AzNetworkManagerGroup @ng
 ```
 
 ## Define membership for a mesh configuration
 
-In this task, you add the static members *vnet-spoke-001* and *vnet-spoke-002* to the network group *network-group* by using [New-AzNetworkManagerStaticMember](/powershell/module/az.network/new-aznetworkmanagerstaticmember).
+In this task, you add the static members *vnet-00* and *vnet-01* to the network group *network-group* by using [New-AzNetworkManagerStaticMember](/powershell/module/az.network/new-aznetworkmanagerstaticmember).
 
 Static members must have a unique name that's scoped to the network group. We recommend that you use a consistent hash of the virtual network ID. This approach uses the Azure Resource Manager template's `uniqueString()` implementation.
 
@@ -181,25 +181,25 @@ Static members must have a unique name that's scoped to the network group. We re
 ```
 
 ```azurepowershell
-$sm_vnetspoke001 = @{
-        Name = Get-UniqueString $vnet_spoke_001.Id
-        ResourceGroupName = $rg.ResourceGroupName
+$sm_vnet_00 = @{
+        Name = Get-UniqueString $vnet_00.Id
+        ResourceGroupName = $rg.Name
         NetworkGroupName = $ng.Name
         NetworkManagerName = $networkManager.Name
-        ResourceId = $vnet_spoke_001.Id
+        ResourceId = $vnet_00.Id
     }
-    $sm_vnetspoke001 = New-AzNetworkManagerStaticMember @sm_vnetspoke001
+    $sm_vnet_00 = New-AzNetworkManagerStaticMember @sm_vnet_00
 ```
 
 ```azurepowershell
-$sm_vnetspoke002 = @{
-        Name = Get-UniqueString $vnet_spoke_002.Id
-        ResourceGroupName = $rg.ResourceGroupName
+$sm_vnet_01 = @{
+        Name = Get-UniqueString $vnet_01.Id
+        ResourceGroupName = $rg.Name
         NetworkGroupName = $ng.Name
         NetworkManagerName = $networkManager.Name
-        ResourceId = $vnet_spoke_002.Id
+        ResourceId = $vnet_01.Id
     }
-    $sm_vnetspoke002 = New-AzNetworkManagerStaticMember @sm_vnetspoke002
+    $sm_vnet_01 = New-AzNetworkManagerStaticMember @sm_vnet_01
 ```
 
 ## Create a connectivity configuration
@@ -227,7 +227,7 @@ In this task, you create a connectivity configuration with the network group *ne
     ```azurepowershell
     $config = @{
         Name = 'connectivity-configuration'
-        ResourceGroupName = $rg.ResourceGroupName
+        ResourceGroupName = $rg.Name
         NetworkManagerName = $networkManager.Name
         ConnectivityTopology = 'Mesh'
         AppliesToGroup = $configGroup
@@ -247,7 +247,7 @@ $target.Add("westus2")
 
 $deployment = @{
     Name = $networkManager.Name
-    ResourceGroupName = $rg.ResourceGroupName
+    ResourceGroupName = $rg.Name
     ConfigurationId = $configIds
     TargetLocation = $target
     CommitType = 'Connectivity'
@@ -257,17 +257,18 @@ Deploy-AzNetworkManagerCommit @deployment
 
 ## Clean up resources
 
-If you no longer need the Azure Virtual Network Manager instance and it's associate resources, delete the resource group that contains them. Deleting the resource group also deletes the resources that you created.
+If you no longer need the Azure Virtual Network Manager instance and its resources, follow these steps to delete them by deleting the resource group containing the resources:
 
 1. Delete the resource group using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):
 
     ```azurepowershell
-    Remove-AzResourceGroup -Name $rg.ResourceGroupName -Force
+    Remove-AzResourceGroup -Name $rg.Name -Force
     ```
 
 ## 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:
+In this step, 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-powershell.md)
+