Skip to content

Commit 74c4cb8

Browse files
committed
Powershell qs
1 parent 65be93e commit 74c4cb8

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,6 @@ az policy definition create \
181181
--rules "{\"if\":{\"allOf\":[{\"field\":\"Name\",\"contains\":\"vnet\"},{\"field\":\"tags['NetworkType']\",\"equals\":\"Prod\"}]},\"then\":{\"effect\":\"addToNetworkGroup\",\"details\":{\"networkGroupId\":\"/subscriptions/<subscriptionID>/resourceGroups/resource-group/providers/Microsoft.Network/networkManagers/network-manager/networkGroups/network-group\"}}}" \
182182
--subscription <subscriptionID> \
183183
--mode "Microsoft.Network.Data"
184-
185184
```
186185

187186
## Apply a policy definition

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ $ng = @{
168168

169169
## Define membership for a mesh configuration
170170

171-
In this task, you add the static members *vnet-spoke-001* and *vnet-01* to the network group *network-group* by using [New-AzNetworkManagerStaticMember](/powershell/module/az.network/new-aznetworkmanagerstaticmember).
171+
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).
172172

173173
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.
174174

@@ -182,22 +182,22 @@ Static members must have a unique name that's scoped to the network group. We re
182182

183183
```azurepowershell
184184
$sm_vnet_00 = @{
185-
Name = Get-UniqueString $vnet_spoke_001.Id
185+
Name = Get-UniqueString $vnet_00.Id
186186
ResourceGroupName = $rg.Name
187187
NetworkGroupName = $ng.Name
188188
NetworkManagerName = $networkManager.Name
189-
ResourceId = $vnet_spoke_001.Id
189+
ResourceId = $vnet_00.Id
190190
}
191191
$sm_vnet_00 = New-AzNetworkManagerStaticMember @sm_vnet_00
192192
```
193193

194194
```azurepowershell
195195
$sm_vnet_01 = @{
196-
Name = Get-UniqueString $vnet_spoke_002.Id
196+
Name = Get-UniqueString $vnet_01.Id
197197
ResourceGroupName = $rg.Name
198198
NetworkGroupName = $ng.Name
199199
NetworkManagerName = $networkManager.Name
200-
ResourceId = $vnet_spoke_002.Id
200+
ResourceId = $vnet_01.Id
201201
}
202202
$sm_vnet_01 = New-AzNetworkManagerStaticMember @sm_vnet_01
203203
```
@@ -257,7 +257,7 @@ Deploy-AzNetworkManagerCommit @deployment
257257

258258
## Clean up resources
259259

260-
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.
260+
If you no longer need the Azure Virtual Network Manager instance and it's associated resources, follow these steps to delete them:
261261

262262
1. Delete the resource group using [Remove-AzResourceGroup](/powershell/module/az.resources/remove-azresourcegroup):
263263

@@ -271,3 +271,4 @@ Now that you've created an Azure Virtual Network Manager instance, learn how to
271271
272272
> [!div class="nextstepaction"]
273273
> [Block network traffic with Azure Virtual Network Manager](how-to-block-network-traffic-powershell.md)
274+

0 commit comments

Comments
 (0)