Skip to content

Commit 84f0e7f

Browse files
committed
QS portal update
1 parent 20a2022 commit 84f0e7f

18 files changed

+160
-279
lines changed

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

Lines changed: 82 additions & 164 deletions
Large diffs are not rendered by default.

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

Lines changed: 55 additions & 90 deletions
Large diffs are not rendered by default.

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

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: mbender-ms
55
ms.author: mbender
66
ms.service: azure-virtual-network-manager
77
ms.topic: quickstart
8-
ms.date: 10/22/2024
8+
ms.date: 1/13/2024
99
ms.custom: template-quickstart, mode-api, engagement-fy23, devx-track-azurepowershell
1010
---
1111

@@ -51,7 +51,7 @@ Before you can create an Azure Virtual Network Manager instance, you have to cre
5151

5252
```azurepowershell
5353
# Create a resource group
54-
$location = "West US 2"
54+
$location = "westus2"
5555
$rg = @{
5656
Name = 'resource-group'
5757
Location = $location
@@ -65,7 +65,7 @@ New-AzResourceGroup @rg
6565
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.
6666

6767
```azurepowershell
68-
$subID= <subscription_id>
68+
$subID= "d9f0f529-83ab-4840-9c8b-76db5d68517f"
6969
7070
[System.Collections.Generic.List[string]]$subGroup = @()
7171
$subGroup.Add("/subscriptions/$subID")
@@ -79,12 +79,12 @@ $scope = New-AzNetworkManagerScope -Subscription $subGroup
7979

8080
## Create a Virtual Network Manager instance
8181

82-
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:
82+
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:
8383

8484
```azurepowershell
8585
$avnm = @{
8686
Name = 'network-manager'
87-
ResourceGroupName = $rg.ResourceGroupName
87+
ResourceGroupName = $rg.Name
8888
NetworkManagerScope = $scope
8989
NetworkManagerScopeAccess = $access
9090
Location = $location
@@ -94,12 +94,12 @@ $networkmanager = New-AzNetworkManager @avnm
9494

9595
## Create three virtual networks
9696

97-
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.
97+
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 *(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.
9898

9999
```azurepowershell
100100
$vnetspoke001 = @{
101101
Name = 'vnet-spoke-001'
102-
ResourceGroupName = $rg.ResourceGroupName
102+
ResourceGroupName = $rg.Name
103103
Location = $location
104104
AddressPrefix = '10.0.0.0/16'
105105
}
@@ -108,15 +108,15 @@ $vnet_spoke_001 = New-AzVirtualNetwork @vnetspoke001
108108
109109
$vnetspoke002 = @{
110110
Name = 'vnet-spoke-002'
111-
ResourceGroupName = $rg.ResourceGroupName
111+
ResourceGroupName = $rg.Name
112112
Location = $location
113113
AddressPrefix = '10.1.0.0/16'
114114
}
115115
$vnet_spoke_002 = New-AzVirtualNetwork @vnetspoke002
116116
117117
$vnethub001 = @{
118118
Name = 'vnet-hub-001'
119-
ResourceGroupName = $rg.ResourceGroupName
119+
ResourceGroupName = $rg.Name
120120
Location = $location
121121
AddressPrefix = '10.2.0.0/16'
122122
}
@@ -155,12 +155,12 @@ $vnet_hub_001 | Set-AzVirtualNetwork
155155

156156
## Create a network group
157157

158-
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:
158+
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:
159159

160160
```azurepowershell
161161
$ng = @{
162162
Name = 'network-group'
163-
ResourceGroupName = $rg.ResourceGroupName
163+
ResourceGroupName = $rg.Name
164164
NetworkManagerName = $networkManager.Name
165165
}
166166
$ng = New-AzNetworkManagerGroup @ng
@@ -183,7 +183,7 @@ Static members must have a unique name that's scoped to the network group. We re
183183
```azurepowershell
184184
$sm_vnetspoke001 = @{
185185
Name = Get-UniqueString $vnet_spoke_001.Id
186-
ResourceGroupName = $rg.ResourceGroupName
186+
ResourceGroupName = $rg.Name
187187
NetworkGroupName = $ng.Name
188188
NetworkManagerName = $networkManager.Name
189189
ResourceId = $vnet_spoke_001.Id
@@ -194,7 +194,7 @@ $sm_vnetspoke001 = @{
194194
```azurepowershell
195195
$sm_vnetspoke002 = @{
196196
Name = Get-UniqueString $vnet_spoke_002.Id
197-
ResourceGroupName = $rg.ResourceGroupName
197+
ResourceGroupName = $rg.Name
198198
NetworkGroupName = $ng.Name
199199
NetworkManagerName = $networkManager.Name
200200
ResourceId = $vnet_spoke_002.Id
@@ -227,7 +227,7 @@ In this task, you create a connectivity configuration with the network group *ne
227227
```azurepowershell
228228
$config = @{
229229
Name = 'connectivity-configuration'
230-
ResourceGroupName = $rg.ResourceGroupName
230+
ResourceGroupName = $rg.Name
231231
NetworkManagerName = $networkManager.Name
232232
ConnectivityTopology = 'Mesh'
233233
AppliesToGroup = $configGroup
@@ -247,7 +247,7 @@ $target.Add("westus2")
247247
248248
$deployment = @{
249249
Name = $networkManager.Name
250-
ResourceGroupName = $rg.ResourceGroupName
250+
ResourceGroupName = $rg.Name
251251
ConfigurationId = $configIds
252252
TargetLocation = $target
253253
CommitType = 'Connectivity'
@@ -262,7 +262,7 @@ If you no longer need the Azure Virtual Network Manager instance and it's associ
262262
1. Delete the resource group using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):
263263

264264
```azurepowershell
265-
Remove-AzResourceGroup -Name $rg.ResourceGroupName -Force
265+
Remove-AzResourceGroup -Name $rg.Name -Force
266266
```
267267
268268
## Next steps
8.09 KB
Loading
39.8 KB
Loading
12.8 KB
Loading
-7.33 KB
Loading
129 KB
Loading

0 commit comments

Comments
 (0)