Merge pull request #108783 from TimShererWithAquent/us1669724r

Azure CLI syntax blocks.

Author: GitHubber17

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

@@ -201,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

@@ -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
@@ -227,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
 ```

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 \

articles/vpn-gateway/create-routebased-vpn-gateway-cli.md

@@ -25,15 +25,15 @@ If you choose to install and use the CLI locally, this article requires that you
 Create a resource group using the [az group create](/cli/azure/group) command. A resource group is a logical container into which Azure resources are deployed and managed. 
 
 
-```azurecli-interactive 
+```azurecli-interactive
 az group create --name TestRG1 --location eastus
 ```
 
 ## <a name="vnet"></a>Create a virtual network
 
 Create a virtual network using the [az network vnet create](/cli/azure/network/vnet) command. The following example creates a virtual network named **VNet1** in the **EastUS** location:
 
-```azurecli-interactive 
+```azurecli-interactive
 az network vnet create \
   -n VNet1 \
   -g TestRG1 \
@@ -47,7 +47,7 @@ az network vnet create \
 
 The gateway subnet contains the reserved IP addresses that the virtual network gateway services use. Use the following examples to add a gateway subnet:
 
-```azurepowershell-interactive
+```azurecli-interactive
 az network vnet subnet create \
   --vnet-name VNet1 \
   -n GatewaySubnet \
@@ -97,7 +97,7 @@ az network vnet-gateway show \
 
 The response looks similar to this:
 
-```
+```output
 {
   "activeActive": false,
   "bgpSettings": null,
@@ -155,7 +155,7 @@ The value associated with the **ipAddress** field is the public IP address of yo
 
 Example response:
 
-```
+```output
 {
   "dnsSettings": null,
   "etag": "W/\"a12d4d03-b27a-46cc-b222-8d9364b8166a\"",
@@ -166,6 +166,7 @@ Example response:
     "etag": null,
     "id": "/subscriptions/<subscription ID>/resourceGroups/TestRG1/providers/Microsoft.Network/virtualNetworkGateways/VNet1GW/ipConfigurations/vnetGatewayConfig0",
 ```
+
 ## Clean up resources
 
 When you no longer need the resources you created, use [az group delete](/cli/azure/group) to delete the resource group. This will delete the resource group and all of the resources it contains.