Skip to content

Commit 5d60140

Browse files
committed
finishing edits
1 parent 74c4cb8 commit 5d60140

File tree

3 files changed

+17
-17
lines changed

3 files changed

+17
-17
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ az extension update --name virtual-network-manager
4848

4949
## Create a resource group
5050

51-
Before you can deploy Azure Virtual Network Manager, you have to create a resource group to host it by using [az group create](/cli/azure/group#az-group-create). This example creates a resource group named *resource-group* in the *(US) West 2* location:
51+
In this task, you create a resource group to host a network manager instance by using [az group create](/cli/azure/group#az-group-create). This example creates a resource group named *resource-group* in the *(US) West 2* location:
5252

5353
```azurecli
5454
az group create \
@@ -58,7 +58,7 @@ az group create \
5858

5959
## Create a Virtual Network Manager instance
6060

61-
Define the scope and access type for this Virtual Network Manager instance. Create the scope by using [az network manager create](/cli/azure/network/manager#az-network-manager-create). Replace the value `<subscriptionID>` with the subscription that you want Virtual Network Manager to manage virtual networks for. Replace `<mgName\>` with the management group that you want to manage.
61+
In this task, define the scope and access type for this Virtual Network Manager instance. Create the scope by using [az network manager create](/cli/azure/network/manager#az-network-manager-create). Replace the value `<subscriptionID>` with the subscription that you want Virtual Network Manager to manage virtual networks for. Replace `<mgName\>` with the management group that you want to manage.
6262

6363
```azurecli
6464
az network manager create \
@@ -71,7 +71,7 @@ az network manager create \
7171

7272
## Create a network group
7373

74-
Virtual Network Manager applies configurations to groups of virtual networks by placing them in network groups. Create a network group by using [az network manager group create](/cli/azure/network/manager/group#az-network-manager-group-create):
74+
In this task, create a network group by using [az network manager group create](/cli/azure/network/manager/group#az-network-manager-group-create):
7575

7676
```azurecli
7777
az network manager group create \
@@ -83,7 +83,7 @@ az network manager group create \
8383

8484
## Create virtual networks
8585

86-
Create five virtual networks by using [az network vnet create](/cli/azure/network/vnet#az-network-vnet-create). This example creates virtual networks named three virtual in the *(US) West 2* location. Each virtual network has a tag of `networkType` that's used for dynamic membership. If you already have virtual networks that you want create a mesh network with, you can skip to the next section.
86+
In this task, create three virtual networks using [az network vnet create](/cli/azure/network/vnet#az-network-vnet-create). This example creates virtual networks named three virtual in the *(US) West 2* location. Each virtual network has a tag of `networkType` that's used for dynamic membership. If you already have virtual networks that you want create a mesh network with, you can skip to the next section.
8787

8888
```azurecli
8989
az network vnet create \
@@ -107,7 +107,7 @@ az network vnet create \
107107

108108
### Add a subnet to each virtual network
109109

110-
Complete the configuration of the virtual networks by adding a */24* subnet to each one. Create a subnet configuration named *default* by using [az network vnet subnet create](/cli/azure/network/vnet/subnet#az-network-vnet-subnet-create):
110+
In this task, complete the configuration of the virtual networks by adding a */24* subnet to each one. Create a subnet configuration named *default* by using [az network vnet subnet create](/cli/azure/network/vnet/subnet#az-network-vnet-subnet-create):
111111

112112
```azurecli
113113
az network vnet subnet create \
@@ -172,7 +172,7 @@ You can apply policies to a subscription or a management group, and you must alw
172172

173173
## Create a policy definition
174174

175-
Create a policy definition by using [az policy definition create](/cli/azure/policy/definition#az-policy-definition-create) for virtual networks tagged as `Prod`. Replace `<subscriptionID>` with the subscription that you want to apply this policy to. If you want to apply it to a management group, replace `--subscription <subscriptionID>` with `--management-group <mgName>`.
175+
In this task, create a policy definition by using [az policy definition create](/cli/azure/policy/definition#az-policy-definition-create) for virtual networks tagged as `Prod`. Replace `<subscriptionID>` with the subscription that you want to apply this policy to. If you want to apply it to a management group, replace `--subscription <subscriptionID>` with `--management-group <mgName>`.
176176

177177
```azurecli
178178
az policy definition create \
@@ -185,7 +185,7 @@ az policy definition create \
185185

186186
## Apply a policy definition
187187

188-
After you define a policy, you must apply it by using [az policy assignment create](/cli/azure/policy/assignment#az-policy-assignment-create). Replace `<subscriptionID>` with the subscription that you want to apply this policy to. If you want to apply it to a management group, replace `--scope "/subscriptions/<subscriptionID>"` with `--scope "/providers/Microsoft.Management/managementGroups/<mgName>`, and replace `<mgName\>` with your management group.
188+
In this task, you apply the previously created policy using [az policy assignment create](/cli/azure/policy/assignment#az-policy-assignment-create). Replace `<subscriptionID>` with the subscription that you want to apply this policy to. If you want to apply it to a management group, replace `--scope "/subscriptions/<subscriptionID>"` with `--scope "/providers/Microsoft.Management/managementGroups/<mgName>`, and replace `<mgName\>` with your management group.
189189

190190
```azurecli
191191
@@ -199,7 +199,7 @@ az policy assignment create \
199199

200200
## Create a configuration
201201

202-
In this step, create a mesh network topology configuration by using [az network manager connect-config create](/cli/azure/network/manager/connect-config#az-network-manager-connect-config-create). Replace `<subscriptionID>` with your subscription ID.
202+
In this task, create a mesh network topology configuration by using [az network manager connect-config create](/cli/azure/network/manager/connect-config#az-network-manager-connect-config-create). Replace `<subscriptionID>` with your subscription ID.
203203

204204
```azurecli
205205
az network manager connect-config create \

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ In this quickstart, you deploy three virtual networks and use Azure Virtual Netw
2020
## Prerequisites
2121

2222
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
23-
- 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.
24-
- 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.
23+
- 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.
24+
- 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.
2525

2626
## Sign in to your Azure account and select your subscription
2727

@@ -47,7 +47,7 @@ Install the latest *Az.Network* Azure PowerShell module by using this command:
4747

4848
## Create a resource group
4949

50-
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:
50+
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:
5151

5252
```azurepowershell
5353
# Create a resource group
@@ -62,7 +62,7 @@ New-AzResourceGroup @rg
6262

6363
## Define the scope and access type
6464

65-
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.
65+
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.
6666

6767
```azurepowershell
6868
$subID= "d9f0f529-83ab-4840-9c8b-76db5d68517f"
@@ -79,7 +79,7 @@ $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 *(US) West US 2* region:
82+
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:
8383

8484
```azurepowershell
8585
$avnm = @{
@@ -94,7 +94,7 @@ $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-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.
97+
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.
9898

9999
```azurepowershell
100100
$vnet_00 = @{
@@ -125,7 +125,7 @@ $vnet_02 = New-AzVirtualNetwork @vnet_02
125125

126126
### Add a subnet to each virtual network
127127

128-
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.
128+
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.
129129

130130
```azurepowershell
131131
$subnet_vnet_00 = @{
@@ -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 associated resources, follow these steps to delete them:
260+
If you no longer need the Azure Virtual Network Manager instance and it's resources, follow these steps to delete them by deleting the resource group containing the resources:
261261

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

@@ -267,7 +267,7 @@ If you no longer need the Azure Virtual Network Manager instance and it's associ
267267
268268
## Next steps
269269
270-
Now that you've created an Azure Virtual Network Manager instance, learn how to block network traffic by using a security admin configuration:
270+
In this step, learn how to block network traffic by using a security admin configuration:
271271
272272
> [!div class="nextstepaction"]
273273
> [Block network traffic with Azure Virtual Network Manager](how-to-block-network-traffic-powershell.md)
4.2 KB
Loading

0 commit comments

Comments
 (0)