Syntax blocks azurecli.

Author: TimShererWithAquent

articles/virtual-network/create-peering-different-deployment-models-subscriptions.md

@@ -96,9 +96,10 @@ This tutorial uses different accounts for each subscription. If you're using an
 2. Run the classic CLI in Service Management mode by entering the `azure config mode asm` command.
 3. Enter the following classic CLI command to create the virtual network (classic):
 
-    ```azurecli
+    ```console
     azure network vnet create --vnet myVnetB --address-space 10.1.0.0 --cidr 16 --location "East US"
     ```
+
 4. The remaining steps must be completed using a bash shell with the Azure CLI (not the classic CLI).
 5. Copy the following script to a text editor on your PC. Replace `<SubscriptionB-Id>` with your subscription ID. If you don't know your subscription Id, enter the `az account show` command. The value for **id** in the output is your subscription Id. Copy the modified script, paste it in to your CLI session, and then press `Enter`.
 
@@ -165,6 +166,7 @@ This tutorial uses different accounts for each subscription. If you're using an
       --vnet-name myVnetA \
       --output table
     ```
+
     The output shows **Connected** in the **PeeringState** column.
 
     Any Azure resources you create in either virtual network are now able to communicate with each other through their IP addresses. If you're using default Azure name resolution for the virtual networks, the resources in the virtual networks are not able to resolve names across the virtual networks. If you want to resolve names across virtual networks in a peering, you must create your own DNS server. Learn how to set up [Name resolution using your own DNS server](virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server).
@@ -199,8 +201,8 @@ This tutorial uses different accounts for each subscription. If you're using an
 
 5. Log in to UserB's subscription as UserB to use Resource Manager commands by entering the `Connect-AzAccount` command.
 6. Assign UserA permissions to virtual network B. Copy the following script to a text editor on your PC and replace `<SubscriptionB-id>` with the ID of subscription B. If you don't know the subscription Id, enter the `Get-AzSubscription` command to view it. The value for **Id** in the returned output is your subscription ID. Azure created the virtual network (classic) you created in step 4 in a resource group named *Default-Networking*. To execute the script, copy the modified script, paste it in to PowerShell, and then press `Enter`.
-    
-    ```powershell 
+
+    ```powershell
     New-AzRoleAssignment `
       -SignInName [email protected] `
       -RoleDefinitionName "Classic Network Contributor" `

articles/virtual-network/ipv6-add-to-existing-vnet-cli.md

@@ -36,15 +36,17 @@ Before you deploy a dual stack application in Azure, you must configure your sub
 az feature register --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
 
-```azurelci
+```azurecli
 az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 After the registration is complete, run the following command:
 
-```azurelci
+```azurecli
 az provider register --namespace Microsoft.Network
 ```
 

articles/virtual-network/scripts/virtual-network-cli-sample-ipv6-dual-stack-standard-load-balancer.md

@@ -29,15 +29,17 @@ To use the IPv6 for Azure virtual network feature, you must configure your subsc
 az feature register --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
 
-```azurelci
+```azurecli
 az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 After the registration is complete, run the following command:
 
-```azurelci
+```azurecli
 az provider register --namespace Microsoft.Network
 ```
 
@@ -274,6 +276,7 @@ az vm create \
 --availability-set dsAVset \
 --image MicrosoftWindowsServer:WindowsServer:2019-Datacenter:latest 
 ```
+
 ## View IPv6 dual stack virtual network in Azure portal
 You can view the IPv6 dual stack virtual network in Azure portal as follows:
 1. In the portal's search bar, enter *dsVnet*.

articles/virtual-network/scripts/virtual-network-cli-sample-ipv6-dual-stack.md

@@ -29,15 +29,17 @@ To use the IPv6 for Azure virtual network feature, you must configure your subsc
 az feature register --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
 
-```azurelci
+```azurecli
 az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 After the registration is complete, run the following command:
 
-```azurelci
+```azurecli
 az provider register --namespace Microsoft.Network
 ```
 
@@ -256,6 +258,7 @@ az vm create \
 --image MicrosoftWindowsServer:WindowsServer:2016-Datacenter:latest
 
 ```
+
 ## Clean up deployment
 
 Run the following command to remove the resource group, VM, and all related resources:

articles/virtual-network/tutorial-create-route-table-cli.md

@@ -47,11 +47,11 @@ Before you can create a route table, create a resource group with [az group crea
 az group create \
   --name myResourceGroup \
   --location eastus
-``` 
+```
 
 Create a route table with [az network route-table create](/cli/azure/network/route-table#az-network-route-table-create). The following example creates a route table named *myRouteTablePublic*. 
 
-```azurecli-interactive 
+```azurecli-interactive
 # Create a route table
 az network route-table create \
   --resource-group myResourceGroup \
@@ -151,6 +151,7 @@ az vm extension set \
   --publisher Microsoft.Azure.Extensions \
   --settings '{"commandToExecute":"sudo sysctl -w net.ipv4.ip_forward=1"}'
 ```
+
 The command may take up to a minute to execute.
 
 ## Create virtual machines
@@ -188,7 +189,7 @@ az vm create \
 
 The VM takes a few minutes to create. After the VM is created, the Azure CLI shows information similar to the following example: 
 
-```azurecli 
+```output
 {
   "fqdns": "",
   "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVmPrivate",
@@ -200,21 +201,22 @@ The VM takes a few minutes to create. After the VM is created, the Azure CLI sho
   "resourceGroup": "myResourceGroup"
 }
 ```
+
 Take note of the **publicIpAddress**. This address is used to access the VM from the internet in a later step.
 
 ## Route traffic through an NVA
 
 Use the following command to create an SSH session with the *myVmPrivate* VM. Replace *\<publicIpAddress>* with the public IP address of your VM. In the example above, the IP address is *13.90.242.231*.
 
-```bash 
+```bash
 ssh azureuser@<publicIpAddress>
 ```
 
 When prompted for a password, enter the password you selected in [Create virtual machines](#create-virtual-machines).
 
 Use the following command to install trace route on the *myVmPrivate* VM:
 
-```bash 
+```bash
 sudo apt-get install traceroute
 ```
 
@@ -226,7 +228,7 @@ traceroute myVmPublic
 
 The response is similar to the following example:
 
-```bash
+```output
 traceroute to myVmPublic (10.0.0.4), 30 hops max, 60 byte packets
 1  10.0.0.4 (10.0.0.4)  1.404 ms  1.403 ms  1.398 ms
 ```
@@ -235,13 +237,13 @@ You can see that traffic is routed directly from the *myVmPrivate* VM to the *my
 
 Use the following command to SSH to the *myVmPublic* VM from the *myVmPrivate* VM:
 
-```bash 
+```bash
 ssh azureuser@myVmPublic
 ```
 
 Use the following command to install trace route on the *myVmPublic* VM:
 
-```bash 
+```bash
 sudo apt-get install traceroute
 ```
 
@@ -258,6 +260,7 @@ traceroute to myVmPrivate (10.0.1.4), 30 hops max, 60 byte packets
 1  10.0.2.4 (10.0.2.4)  0.781 ms  0.780 ms  0.775 ms
 2  10.0.1.4 (10.0.0.4)  1.404 ms  1.403 ms  1.398 ms
 ```
+
 You can see that the first hop is 10.0.2.4, which is the NVA's private IP address. The second hop is 10.0.1.4, the private IP address of the *myVmPrivate* VM. The route added to the *myRouteTablePublic* route table and associated to the *Public* subnet caused Azure to route the traffic through the NVA, rather than directly to the *Private* subnet.
 
 Close the SSH sessions to both the *myVmPublic* and *myVmPrivate* VMs.
@@ -266,7 +269,7 @@ Close the SSH sessions to both the *myVmPublic* and *myVmPrivate* VMs.
 
 When no longer needed, use [az group delete](/cli/azure/group) to remove the resource group and all of the resources it contains.
 
-```azurecli-interactive 
+```azurecli-interactive
 az group delete --name myResourceGroup --yes
 ```
 

articles/virtual-network/tutorial-tap-virtual-network-cli.md

@@ -82,6 +82,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
       --query id \
       --out tsv)
       ```
+
    - Create the virtual network TAP using the ID of the frontend IP configuration as the destination and an optional port property. The port specifies the destination port on front end IP configuration where the TAP traffic will be received :  
 
       ```azurecli-interactive
@@ -136,7 +137,7 @@ Read [prerequisites](virtual-network-tap-overview.md#prerequisites) before you c
 
 ## Delete the TAP configuration on a network interface
 
-   ```azure-cli-interactive
+   ```azurecli-interactive
    az network nic vtap-config delete \
    --resource-group myResourceGroup \
    --nic myNetworkInterface \

articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-cli.md

@@ -39,15 +39,17 @@ az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
 It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
 
-```azurelci
+```azurecli
 az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 After the registration is complete, run the following command:
 
-```azurelci
+```azurecli
 az provider register --namespace Microsoft.Network
 ```
+
 ## Create a resource group
 
 Before you can create your dual-stack virtual network, you must create a resource group with [az group create](/cli/azure/group). The following example creates a resource group named *DsResourceGroup01* in the *eastus* location:
@@ -146,12 +148,14 @@ az network lb address-pool create \
 --name dsLbBackEndPool_v6  \
 --resource-group DsResourceGroup01
 ```
+
 ### Create a health probe
 Create a health probe with [az network lb probe create](https://docs.microsoft.com/cli/azure/network/lb/probe?view=azure-cli-latest) to monitor the health of the virtual machines. 
 
 ```azurecli
 az network lb probe create -g DsResourceGroup01  --lb-name dsLB -n dsProbe --protocol tcp --port 3389
 ```
+
 ### Create a load balancer rule
 
 A load balancer rule is used to define how traffic is distributed to the VMs. You define the frontend IP configuration for the incoming traffic and the backend IP pool to receive the traffic, along with the required source and destination port. 
@@ -295,7 +299,7 @@ az network vnet subnet create \
 ### Create NICs
 
 Create virtual NICs for each VM with [az network nic create](https://docs.microsoft.com/cli/azure/network/nic?view=azure-cli-latest#az-network-nic-create). The following example creates a virtual NIC for each VM. Each NIC has two IP configurations (1 IPv4 config, 1 IPv6 config). You create the IPV6 configuration with [az network nic ip-config create](https://docs.microsoft.com/cli/azure/network/nic/ip-config?view=azure-cli-latest#az-network-nic-ip-config-create).
- 
+
 ```azurecli
 # Create NICs
 az network nic create \
@@ -358,6 +362,7 @@ Create virtual machine *dsVM0* as follows:
 --availability-set dsAVset \
 --image MicrosoftWindowsServer:WindowsServer:2019-Datacenter:latest  
 ```
+
 Create virtual machine *dsVM1* as follows:
 
 ```azurecli

articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-cli.md

@@ -35,17 +35,20 @@ To use the IPv6 for Azure virtual network feature, you must configure your subsc
 az feature register --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
 
-```azurelci
+```azurecli
 az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
 az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
 ```
+
 After the registration is complete, run the following command:
 
-```azurelci
+```azurecli
 az provider register --namespace Microsoft.Network
 ```
+
 ## Create a resource group
 
 Before you can create your dual-stack virtual network, you must create a resource group with [az group create](/cli/azure/group). The following example creates a resource group named *DsResourceGroup01* in the *eastus* location:
@@ -151,6 +154,7 @@ Create a health probe with [az network lb probe create](https://docs.microsoft.c
 ```azurecli
 az network lb probe create -g DsResourceGroup01  --lb-name dsLB -n dsProbe --protocol tcp --port 3389
 ```
+
 ### Create a load balancer rule
 
 A load balancer rule is used to define how traffic is distributed to the VMs. You define the frontend IP configuration for the incoming traffic and the backend IP pool to receive the traffic, along with the required source and destination port. 
@@ -357,6 +361,7 @@ Create virtual machine *dsVM0* as follows:
 --availability-set dsAVset \
 --image MicrosoftWindowsServer:WindowsServer:2019-Datacenter:latest  
 ```
+
 Create virtual machine *dsVM1* as follows:
 
 ```azurecli

articles/virtual-network/virtual-network-multiple-ip-addresses-cli.md

@@ -171,7 +171,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
 	To add a private IP address to a NIC, you must create an IP configuration using the command that follows. The static IP address must be an unused address for the subnet.
 
-	```bash
+	```azurecli
 	az network nic ip-config create \
 	--resource-group myResourceGroup \
 	--nic-name myNic1 \
@@ -191,7 +191,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
 		Whenever you add a public IP address in a new IP configuration, you must also add a private IP address, because all IP configurations must have a private IP address. You can either add an existing public IP address resource, or create a new one. To create a new one, enter the following command:
 
-		```bash
+		```azurecli
 		az network public-ip create \
 		--resource-group myResourceGroup \
 		--location westcentralus \
@@ -201,7 +201,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
  		To create a new IP configuration with a static private IP address and the associated *myPublicIP3* public IP address resource, enter the following command:
 
-		```bash
+		```azurecli
 		az network nic ip-config create \
 		--resource-group myResourceGroup \
 		--nic-name myNic1 \
@@ -213,7 +213,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 	- **Associate the resource to an existing IP configuration**
 		A public IP address resource can only be associated to an IP configuration that doesn't already have one associated. You can determine whether an IP configuration has an associated public IP address by entering the following command:
 
-		```bash
+		```azurecli
 		az network nic ip-config list \
 		--resource-group myResourceGroup \
 		--nic-name myNic1 \
@@ -230,7 +230,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
 		Since the **PublicIpAddressId** column for *IpConfig-3* is blank in the output, no public IP address resource is currently associated to it. You can add an existing public IP address resource to IpConfig-3, or enter the following command to create one:
 
-		```bash
+		```azurecli
 		az network public-ip create \
 		--resource-group  myResourceGroup
 		--location westcentralus \
@@ -241,7 +241,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
 		Enter the following command to associate the public IP address resource to the existing IP configuration named *IPConfig-3*:
 
-		```bash
+		```azurecli
 		az network nic ip-config update \
 		--resource-group myResourceGroup \
 		--nic-name myNic1 \
@@ -251,7 +251,7 @@ You can add additional private and public IP addresses to an existing Azure netw
 
 3. View the private IP addresses and the public IP address resource Ids assigned to the NIC by entering the following command:
 
-	```bash
+	```azurecli
 	az network nic ip-config list \
 	--resource-group myResourceGroup \
 	--nic-name myNic1 \