Merge pull request #108083 from TimShererWithAquent/us1669724m

Syntax block azurecli fixes.

Author: v-shils

articles/virtual-machine-scale-sets/tutorial-autoscale-cli.md

@@ -113,13 +113,13 @@ The following example output shows the instance name, public IP address of the l
 
 SSH to your first VM instance. Specify your own public IP address and port number with the `-p` parameter, as shown from the preceding command:
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50001
 ```
 
 Once logged in, install the **stress** utility. Start *10* **stress** workers that generate CPU load. These workers run for *420* seconds, which is enough to cause the autoscale rules to implement the desired action.
 
-```azurecli-interactive
+```console
 sudo apt-get -y install stress
 sudo stress --cpu 10 --timeout 420 &
 ```
@@ -128,26 +128,26 @@ When **stress** shows output similar to *stress: info: [2688] dispatching hogs:
 
 To confirm that **stress** generates CPU load, examine the active system load with the **top** utility:
 
-```azurecli-interactive
+```console
 top
 ```
 
 Exit **top**, then close your connection to the VM instance. **stress** continues to run on the VM instance.
 
-```azurecli-interactive
+```console
 Ctrl-c
 exit
 ```
 
 Connect to second VM instance with the port number listed from the previous [az vmss list-instance-connection-info](/cli/azure/vmss):
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50003
 ```
 
 Install and run **stress**, then start ten workers on this second VM instance.
 
-```azurecli-interactive
+```console
 sudo apt-get -y install stress
 sudo stress --cpu 10 --timeout 420 &
 ```
@@ -156,7 +156,7 @@ Again, when **stress** shows output similar to *stress: info: [2713] dispatching
 
 Close your connection to the second VM instance. **stress** continues to run on the VM instance.
 
-```azurecli-interactive
+```console
 exit
 ```
 
@@ -173,7 +173,7 @@ watch az vmss list-instances \
 
 Once the CPU threshold has been met, the autoscale rules increase the number of VM instances in the scale set. The following output shows three VMs created as the scale set autoscales out:
 
-```bash
+```output
 Every 2.0s: az vmss list-instances --resource-group myResourceGroup --name myScaleSet --output table
 
   InstanceId  LatestModelApplied    Location    Name          ProvisioningState    ResourceGroup    VmId
@@ -187,7 +187,7 @@ Every 2.0s: az vmss list-instances --resource-group myResourceGroup --name mySca
 
 Once **stress** stops on the initial VM instances, the average CPU load returns to normal. After another 5 minutes, the autoscale rules then scale in the number of VM instances. Scale in actions remove VM instances with the highest IDs first. When a scale set uses Availability Sets or Availability Zones, scale in actions are evenly distributed across those VM instances. The following example output shows one VM instance deleted as the scale set autoscales in:
 
-```bash
+```output
            6  True                  eastus      myScaleSet_6  Deleting             myResourceGroup  9e4133dd-2c57-490e-ae45-90513ce3b336
 ```
 

articles/virtual-machine-scale-sets/tutorial-autoscale-template.md

@@ -170,13 +170,13 @@ The following example output shows the instance name, public IP address of the l
 
 SSH to your first VM instance. Specify your own public IP address and port number with the `-p` parameter, as shown from the preceding command:
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50001
 ```
 
 Once logged in, install the **stress** utility. Start *10* **stress** workers that generate CPU load. These workers run for *420* seconds, which is enough to cause the autoscale rules to implement the desired action.
 
-```azurecli-interactive
+```console
 sudo apt-get -y install stress
 sudo stress --cpu 10 --timeout 420 &
 ```
@@ -185,26 +185,26 @@ When **stress** shows output similar to *stress: info: [2688] dispatching hogs:
 
 To confirm that **stress** generates CPU load, examine the active system load with the **top** utility:
 
-```azurecli-interactive
+```console
 top
 ```
 
 Exit **top**, then close your connection to the VM instance. **stress** continues to run on the VM instance.
 
-```azurecli-interactive
+```console
 Ctrl-c
 exit
 ```
 
 Connect to second VM instance with the port number listed from the previous [az vmss list-instance-connection-info](/cli/azure/vmss):
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50003
 ```
 
 Install and run **stress**, then start ten workers on this second VM instance.
 
-```azurecli-interactive
+```console
 sudo apt-get -y install stress
 sudo stress --cpu 10 --timeout 420 &
 ```
@@ -213,7 +213,7 @@ Again, when **stress** shows output similar to *stress: info: [2713] dispatching
 
 Close your connection to the second VM instance. **stress** continues to run on the VM instance.
 
-```azurecli-interactive
+```console
 exit
 ```
 
@@ -229,7 +229,7 @@ watch az vmss list-instances \
 
 Once the CPU threshold has been met, the autoscale rules increase the number of VM instances in the scale set. The following output shows three VMs created as the scale set autoscales out:
 
-```bash
+```output
 Every 2.0s: az vmss list-instances --resource-group myResourceGroup --name myScaleSet --output table
 
   InstanceId  LatestModelApplied    Location    Name          ProvisioningState    ResourceGroup    VmId
@@ -243,7 +243,7 @@ Every 2.0s: az vmss list-instances --resource-group myResourceGroup --name mySca
 
 Once **stress** stops on the initial VM instances, the average CPU load returns to normal. After another 5 minutes, the autoscale rules then scale in the number of VM instances. Scale in actions remove VM instances with the highest IDs first. When a scale set uses Availability Sets or Availability Zones, scale in actions are evenly distributed across those VM instances. The following example output shows one VM instance deleted as the scale set autoscales in:
 
-```bash
+```output
            6  True                  eastus      myScaleSet_6  Deleting             MYRESOURCEGROUP  9e4133dd-2c57-490e-ae45-90513ce3b336
 ```
 

articles/virtual-machine-scale-sets/tutorial-create-and-manage-cli.md

@@ -64,7 +64,7 @@ az vmss list-instances \
 
 The following example output shows two VM instances in the scale set:
 
-```bash
+```output
   InstanceId  LatestModelApplied    Location    Name          ProvisioningState    ResourceGroup    VmId
 ------------  --------------------  ----------  ------------  -------------------  ---------------  ------------------------------------
            1  True                  eastus      myScaleSet_1  Succeeded            MYRESOURCEGROUP  c059be0c-37a2-497a-b111-41272641533c
@@ -95,7 +95,7 @@ az vmss list-instance-connection-info \
 
 The following example output shows the instance name, public IP address of the load balancer, and port number that the NAT rules forward traffic to:
 
-```bash
+```output
 {
   "instance 1": "13.92.224.66:50001",
   "instance 3": "13.92.224.66:50003"
@@ -104,13 +104,13 @@ The following example output shows the instance name, public IP address of the l
 
 SSH to your first VM instance. Specify your public IP address and port number with the `-p` parameter, as shown from the preceding command:
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50001
 ```
 
 Once logged in to the VM instance, you could perform some manual configuration changes as needed. For now, close the SSH session as normal:
 
-```bash
+```console
 exit
 ```
 
@@ -124,7 +124,7 @@ az vm image list --output table
 
 The following example output shows the most common VM images on Azure. The *UrnAlias* can be used to specify one of these common images when you create a scale set.
 
-```bash
+```output
 Offer          Publisher               Sku                 Urn                                                             UrnAlias             Version
 -------------  ----------------------  ------------------  --------------------------------------------------------------  -------------------  ---------
 CentOS         OpenLogic               7.3                 OpenLogic:CentOS:7.3:latest                                     CentOS               latest
@@ -148,7 +148,7 @@ az vm image list --offer CentOS --all --output table
 
 The following condensed output shows some of the CentOS 7.3 images available:
 
-```azurecli-interactive 
+```output
 Offer    Publisher   Sku   Urn                                 Version
 -------  ----------  ----  ----------------------------------  -------------
 CentOS   OpenLogic   7.3   OpenLogic:CentOS:7.3:7.3.20161221   7.3.20161221
@@ -197,7 +197,7 @@ az vm list-sizes --location eastus --output table
 
 The output is similar to the following condensed example, which shows the resources assigned to each VM size:
 
-```azurecli-interactive
+```output
   MaxDataDiskCount    MemoryInMb  Name                      NumberOfCores    OsDiskSizeInMb    ResourceDiskSizeInMb
 ------------------  ------------  ----------------------  ---------------  ----------------  ----------------------
                  4          3584  Standard_DS1_v2                       1           1047552                    7168

articles/virtual-machine-scale-sets/tutorial-use-custom-image-cli.md

@@ -46,7 +46,7 @@ az vm create \
 
 The public IP address of your VM is shown in the output of the [az vm create](/cli/azure/vm) command. SSH to the public IP address of your VM as follows:
 
-```azurecli-interactive
+```console
 ssh azureuser@<publicIpAddress>
 ```
 

articles/virtual-machine-scale-sets/tutorial-use-disks-cli.md

@@ -141,7 +141,7 @@ az vmss list-instance-connection-info \
 
 Use your own public IP address and port number to connect to the first VM instance, as shown in the following example:
 
-```azurecli-interactive
+```console
 ssh [email protected] -p 50001
 ```
 
@@ -193,7 +193,7 @@ sudo df -h
 
 The following example output shows that the three disks have their filesystems correctly mounted under */datadisks*:
 
-```bash
+```output
 Filesystem      Size  Used Avail Use% Mounted on
 /dev/sda1        30G  1.3G   28G   5% /
 /dev/sdb1        50G   52M   47G   1% /mnt

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maintenance-notifications.md

@@ -142,7 +142,7 @@ You can view planned maintenance information by using [az vmss list-instances](/
 
 Maintenance information is returned only if maintenance is planned. If no maintenance that affects the VM instance is scheduled, the command doesn't return any maintenance information. 
 
-```azure-cli
+```azurecli
 az vmss list-instances -g rgName -n vmssName --expand instanceView
 ```
 
@@ -162,7 +162,7 @@ The following properties are returned under **MaintenanceRedeployStatus** for ea
 
 The following call initiates maintenance on a VM instance if `IsCustomerInitiatedMaintenanceAllowed` is set to **true**:
 
-```azure-cli
+```azurecli
 az vmss perform-maintenance -g rgName -n vmssName --instance-ids id
 ```
 

articles/virtual-machines/maintenance-control-powershell.md

@@ -247,7 +247,7 @@ Get-AzApplyUpdate `
 
 Use [Remove-AzMaintenanceConfiguration](https://docs.microsoft.com/powershell/module/az.maintenance/remove-azmaintenanceconfiguration) to delete a maintenance configuration.
 
-```azurecli-interactive
+```azurepowershell-interactive
 Remove-AzMaintenanceConfiguration `
    -ResourceGroupName myResourceGroup `
    -Name $config.Name

articles/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands.md

@@ -58,31 +58,31 @@ For additional documentation and instructions, see [az vm repair](https://docs.m
 
 2. If this is the first time you have used the `az vm repair` commands, add the vm-repair CLI extension.
 
-   ```azurepowershell-interactive
+   ```azurecli-interactive
    az extension add -n vm-repair
    ```
 
    If you have previously used the `az vm repair` commands, apply any updates to the vm-repair extension.
 
-   ```azurepowershell-interactive
+   ```azurecli-interactive
    az extension update -n vm-repair
    ```
 
 3. Run `az vm repair create`. This command will create a copy of the OS disk for the non-functional VM, create a repair VM, and attach the disk.
 
-   ```azurepowershell-interactive
+   ```azurecli-interactive
    az vm repair create -g MyResourceGroup -n myVM --repair-username username --repair-password password!234 --verbose
    ```
 
 4. Run `az vm repair run`. This command will run the specified repair script on the attached disk via the repair VM.
 
-   ```azurepowershell-interactive
+   ```azurecli-interactive
    az vm repair run  –g MyResourceGroup –n MyVM -–run-on-repair --run-id 2 --verbose
    ```
 
 5. Run `az vm repair restore`. This command will swap the repaired OS disk with the original OS disk of the VM.
 
-   ```azurepowershell-interactive
+   ```azurecli-interactive
    az vm repair restore -g MyResourceGroup -n MyVM --verbose
    ```
 
@@ -92,7 +92,7 @@ The following example enables the diagnostic extension on the VM named ``myVMDep
 
 Azure CLI
 
-```azurepowershell-interactive
+```azurecli-interactive
 az vm boot-diagnostics enable --name myVMDeployed --resource-group myResourceGroup --storage https://mystor.blob.core.windows.net/
 ```
 

includes/virtual-machines-common-classic-resource-manager-migration-common-errors.md

@@ -159,13 +159,15 @@ Update-AzureVM       b0ad3d4c-4v68-45vb-xxc1-134fd010d0f8 Succeeded
 After you complete the migration process, you may want to move the VM to another subscription. However, if you have a secret/certificate on the VM that references a Key Vault resource, the move is currently not supported. The below instructions will allow you to workaround the issue. 
 
 #### PowerShell
+
 ```powershell
 $vm = Get-AzVM -ResourceGroupName "MyRG" -Name "MyVM"
 Remove-AzVMSecret -VM $vm
 Update-AzVM -ResourceGroupName "MyRG" -VM $vm
 ```
+
 #### Azure CLI
 
-```bash
+```azurecli
 az vm update -g "myrg" -n "myvm" --set osProfile.Secrets=[]
 ```

includes/virtual-machines-common-shared-image-galleries.md

@@ -228,7 +228,7 @@ To list all the Shared Image Gallery resources across subscriptions that you hav
 
    To list all the Shared Image Gallery resources across subscriptions that you have permissions to, use the following command in the Azure CLI:
 
-   ```bash
+   ```azurecli
    az account list -otsv --query "[].id" | xargs -n 1 az sig list --subscription
    ```