Azure CLI Code tag cleanup

Author: TimShererWithAquent

articles/cosmos-db/sql/tutorial-springboot-azure-kubernetes-service.md

@@ -157,13 +157,13 @@ If you intend to run the application on Azure Kubernetes Service, skip this sect
 
 1. Log into Azure Container Registry.
 
-   ```bash
+   ```azurecli
    az acr login -n cosmosdbspringbootregistry
    ```
 
 1. Push image to Azure Container Registry and list it.
 
-   ```bash
+   ```azurecli
    docker push cosmosdbspringbootregistry.azurecr.io/spring-cosmos-app:v1
 
    az acr repository list --name cosmosdbspringbootregistry --output table

articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md

@@ -64,7 +64,7 @@ az vm image list --all --publisher "Canonical"
 
 Here is an example output when VM images of a certain publisher, offer, and SKU were queried.
 
-```output
+```azurecli
 PS /home/user> az vm image list --all --publisher "Canonical" --offer "UbuntuServer" --sku "12.04.4-LTS"
 [
   {
@@ -176,7 +176,7 @@ Create an Azure Managed Disk from your chosen Marketplace image.
 
 Here is an example output:
 
-```output
+```azurecli
 PS /home/user> $urn = “MicrosoftWindowsServer:WindowsServer:2019-Datacenter:Latest”
 PS /home/user> $diskName = "newmanageddisk1"
 PS /home/user> $diskRG = "newrgmd1"

articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-cli-python.md

@@ -292,7 +292,7 @@ Before you begin creating and managing a VM on your Azure Stack Edge Pro device
     ```
     The following shows sample usage of the above command:
     
-    ```output
+    ```azurecli
     PS C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2> az cloud register -n az-new-env --endpoint-resource-manager "https://management.team3device.teatraining1.com"
     ```
     
@@ -304,7 +304,7 @@ Before you begin creating and managing a VM on your Azure Stack Edge Pro device
     ```
     The following shows sample usage of the above command:
 
-    ```output
+    ```azurecli
     PS C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2> az cloud set -n az-new-env
     Switched active cloud to 'az-new-env'.
     Use 'az login' to log in to this cloud.

articles/synapse-analytics/spark/use-prometheus-grafana-to-monitor-apache-spark-application-level-metrics.md

@@ -30,7 +30,7 @@ Or use the [Azure Cloud Shell](https://shell.azure.com/), which already includes
 
 ## Log in to Azure
 
-```bash
+```azurecli
 az login
 az account set --subscription "<subscription_id>"
 ```
@@ -48,7 +48,7 @@ Note: This step can be skipped if you already have an AKS cluster.
 
 ## Create a service principal and grant permission to Synapse workspace
 
-```bash
+```azurecli
 az ad sp create-for-rbac --name <service_principal_name> --role Contributor --scopes /subscriptions/<subscription_id>
 ```
 
@@ -139,7 +139,7 @@ helm delete <release_name> -n <namespace>
 
 Delete the AKS cluster.
 
-```bash
+```azurecli
 az aks delete --name <kubernetes_cluster_name> --resource-group <kubernetes_cluster_rg>
 ```
 

articles/virtual-desktop/azure-stack-hci.md

@@ -106,25 +106,25 @@ You can find the image you're looking for by using the **Search** function in Az
 
 If you're looking for Windows 10 multi-session, you can run a search with this criteria:
 
-```azure
+```azurecli
 az vm image list --all --publisher "microsoftwindowsdesktop" --offer "windows-10" --sku "21h1-evd-g2"
 ```
 
 This command should return the following URN:
 
-```azure
+```output
 MicrosoftWindowsDesktop:Windows-10:21h1-evd-g2:latest
 ```
 
 If you're looking for Windows Server 2019 datacenter, you can run the following criteria in your Azure CLI:
 
-```azure
+```azurecli
 az vm image list --all --publisher "microsoftwindowsserver" --offer "WindowsServer" --sku "2019-Datacenter-gen2"
 ```
 
 This command should return the following URN:
 
-```azure
+```output
 MicrosoftWindowsServer:windowsserver-gen2preview:2019-datacenter-gen2:latest
 ```
 
@@ -139,15 +139,15 @@ To create an Azure managed disk:
 
 1. Run the following commands in an Azure command-line prompt to set the parameters of your managed disk. Make sure to replace the items in brackets with the values relevant to your scenario.
 
-```azure
+```console
 $urn = <URN of the Marketplace image> #Example: “MicrosoftWindowsServer:WindowsServer:2019-Datacenter:Latest”
 $diskName = <disk name> #Name for new disk to be created
 $diskRG = <resource group> #Resource group that contains the new disk
 ```
 
 2. Run these commands to create the disk and generate a Serial Attached SCSI (SAS) access URL.
 
-```azure
+```azurecli
 az disk create -g $diskRG -n $diskName --image-reference $urn
 $sas = az disk grant-access --duration-in-seconds 36000 --access-level Read --name $diskName --resource-group $diskRG
 $diskAccessSAS = ($sas | ConvertFrom-Json)[0].accessSas
@@ -166,7 +166,7 @@ To export the VHD:
 >[!NOTE]
 >If you're running azcopy, you may need to skip the md5check by running this command:
 >
-> ```azure
+> ```azurecli
 > azcopy copy “$sas" "destination_path_on_cluster" --check-md5 NoCheck
 > ```
 
@@ -176,7 +176,7 @@ When you're done with your VHD, you'll need to free up space by deleting the man
 
 To delete the managed disk you created, run these commands:
 
-```azure
+```azurecli
 az disk revoke-access --name $diskName --resource-group $diskRG 
 az disk delete --name $diskName --resource-group $diskRG --yes
 ```

articles/virtual-machines/custom-data.md

@@ -22,7 +22,7 @@ To use custom data, you must Base64-encode the contents before passing the data
 
 In the CLI, you can pass your custom data as a file, as the following example shows. The file will be converted to Base64.
 
-```bash
+```azurecli
 az vm create \
   --resource-group myResourceGroup \
   --name centos74 \

articles/virtual-machines/linux/cli-ps-findimage.md

@@ -264,7 +264,7 @@ If you have an existing VHD from a VM that was created using a paid Azure Market
 
 If you still have the original VM, or another VM created using the same marketplace image, you can get the plan name, publisher, and product information from it using [az vm get-instance-view](/cli/azure/vm#az-vm-get-instance-view). This example gets a VM named *myVM* in the *myResourceGroup* resource group and then displays the purchase plan information.
 
-```azurepowershell-interactive
+```azurecli-interactive
 az vm get-instance-view -g myResourceGroup -n myVM --query plan
 ```
 

articles/virtual-machines/linux/how-to-resize-encrypted-lvm.md

@@ -48,7 +48,7 @@ There are two Azure VM Image Builder (AIB) DevOps Tasks:
     New-AzStorageAccount -ResourceGroupName $strResourceGroup -Name $storageAccName -Location $location -SkuName Standard_LRS
     ```
 
-    ```bash
+    ```azurecli
     # Az CLI
     location=westus
     scriptStorageAcc=aibstordot$(date +'%s')

articles/virtual-machines/linux/image-builder-devops-task.md

@@ -570,7 +570,7 @@ You can distribute an image to both of the target types in the same configuratio
 
 Because you can have more than one target to distribute to, Image Builder maintains a state for every distribution target that can be accessed by querying the `runOutputName`.  The `runOutputName` is an object you can query post distribution for information about that distribution. For example, you can query the location of the VHD, or regions where the image version was replicated to, or SIG Image version created. This is a property of every distribution target. The `runOutputName` must be unique to each distribution target. Here is an example, this is querying an Azure Compute Gallery distribution:
 
-```bash
+```azurecli
 subscriptionID=<subcriptionID>
 imageResourceGroup=<resourceGroup of image template>
 runOutputName=<runOutputName>
@@ -720,7 +720,7 @@ Invoke-AzResourceAction -ResourceName $imageTemplateName -ResourceGroupName $ima
 ```
 
 
-```bash
+```azurecli
 az resource invoke-action \
      --resource-group $imageResourceGroup \
      --resource-type  Microsoft.VirtualMachineImages/imageTemplates \
@@ -740,7 +740,7 @@ Examples of `cancel` commands:
 Invoke-AzResourceAction -ResourceName $imageTemplateName -ResourceGroupName $imageResourceGroup -ResourceType Microsoft.VirtualMachineImages/imageTemplates -ApiVersion "2021-10-01" -Action Cancel -Force
 ```
 
-```bash
+```azurecli
 az resource invoke-action \
      --resource-group $imageResourceGroup \
      --resource-type  Microsoft.VirtualMachineImages/imageTemplates \

articles/virtual-machines/linux/image-builder-json.md

@@ -357,7 +357,7 @@ Deployment failed. Correlation ID: XXXXXX-XXXX-XXXXXX-XXXX-XXXXXX. Failed in dis
 
 Image Builder timed out waiting for the image to be added and replicated to the Azure Compute Gallery. If the image is being injected into the SIG, it can be assumed the image build was successful. However, the overall process failed, because the image builder was waiting on Azure Compute Gallery to complete the replication. Even though the build has failed, the replication continues. You can get the properties of the image version by checking the distribution *runOutput*.
 
-```bash
+```azurecli
 $runOutputName=<distributionRunOutput>
 az resource show \
     --ids "/subscriptions/$subscriptionID/resourcegroups/$imageResourceGroup/providers/Microsoft.VirtualMachineImages/imageTemplates/$imageTemplateName/runOutputs/$runOutputName"  \

articles/virtual-machines/linux/image-builder-troubleshoot.md

@@ -65,7 +65,7 @@ az group create -n $imageResourceGroup -l $location
 
 If you do not have an existing VNET\Subnet\NSG, use the following script to create one.
 
-```bash
+```azurecli
 
 # Create a resource group
 
@@ -151,7 +151,7 @@ sed -i -e "s/<vnetRgName>/$vnetRgName/g" aibRoleNetworking.json
 
 Image Builder will use the [user-identity](../../active-directory/managed-identities-azure-resources/qs-configure-cli-windows-vm.md#user-assigned-managed-identity) provided to inject the image into the Azure Compute Gallery (formerly known as Shared Image Gallery). In this example, you will create an Azure role definition that has the granular actions to perform distributing the image to the SIG. The role definition will then be assigned to the user-identity.
 
-```bash
+```azurecli
 # create user assigned identity for image builder
 idenityName=aibBuiUserId$(date +'%s')
 az identity create -g $imageResourceGroup -n $idenityName
@@ -176,7 +176,7 @@ sed -i -e "s/Azure Image Builder Service Networking Role/$netRoleDefName/g" aibR
 
 Instead of granting Image Builder lower granularity and increased privilege, you can create two roles. One gives the builder permissions to create an image, the other allows it to connect the build VM and load balancer to your VNET.
 
-```bash
+```azurecli
 # create role definitions
 az role definition create --role-definition ./aibRoleImageCreation.json
 az role definition create --role-definition ./aibRoleNetworking.json

articles/virtual-machines/linux/image-builder-vnet.md

@@ -48,13 +48,13 @@ This demo will show how you can take an existing Marketplace image (in this case
 
 ### Create the resource group and base VM:
 
-```bash
+```azurecli
 $ az group create --location eastus --name demo1
 ```
 
 Create the base VM:
 
-```bash
+```azurecli
 $ az vm create \
     --resource-group demo1 \
     --name demo1 \
@@ -284,14 +284,14 @@ Now the VM is ready to be generalized and have an image created from it.
 
 Back on your development machine, run the following to prepare for image creation from the base VM:
 
-```bash
+```azurecli
 $ az vm deallocate --resource-group demo1 --name demo1
 $ az vm generalize --resource-group demo1 --name demo1
 ```
 
 And create the image from this VM:
 
-```bash
+```azurecli
 $ az image create \
     --resource-group demo1 \
     --source demo1 \
@@ -301,7 +301,7 @@ $ az image create \
 
 Now we are ready to create a new VM (or multiple VMs) from the image:
 
-```bash
+```azurecli
 $ IMAGE_ID=$(az image show -g demo1 -n demo1img --query id -o tsv)
 $ az vm create \
     --resource-group demo12 \

articles/virtual-machines/linux/no-agent.md

@@ -67,15 +67,15 @@ After you create the VM, Azure CLI displays information similar to the following
 ```
 ## Create and attach a new disk for Oracle datafiles and FRA
 
-```bash
+```azurecli
 az vm disk attach --name oradata01 --new --resource-group rg-oracle --size-gb 64 --sku StandardSSD_LRS --vm-name vmoracle19c
 ```
 
 ## Open ports for connectivity
 In this task you must configure some external endpoints for the database listener to use by setting up the Azure Network Security Group that protects the VM. 
 
 1. To open the endpoint that you use to access the Oracle database remotely, create a Network Security Group rule as follows:
-   ```bash
+   ```azurecli
    az network nsg rule create ^
        --resource-group rg-oracle ^
        --nsg-name vmoracle19cNSG ^
@@ -85,7 +85,7 @@ In this task you must configure some external endpoints for the database listene
        --destination-port-range 1521
    ```
 2. To open the endpoint that you use to access Oracle remotely, create a Network Security Group rule with az network nsg rule create as follows:
-   ```bash
+   ```azurecli
    az network nsg rule create ^
        --resource-group rg-oracle ^
        --nsg-name vmoracle19cNSG ^
@@ -96,7 +96,7 @@ In this task you must configure some external endpoints for the database listene
    ```
 3. If needed, obtain the public IP address of your VM again with az network public-ip show as follows:
 
-   ```bash
+   ```azurecli
    az network public-ip show ^
        --resource-group rg-oracle ^
        --name vmoracle19cPublicIP ^

articles/virtual-machines/workloads/oracle/oracle-database-quick-create.md

@@ -383,7 +383,7 @@ The sample SAP Library configuration file `MGMT-NOEU-SAP_LIBRARY.tfvars` is in t
 
 - If you have authentication issues directly after running the script `prepare_region.sh`, run:
 
-    ```bash
+    ```azurecli
     az logout
 
     az login
@@ -488,7 +488,7 @@ For this example configuration, the resource group is `MGMT-NOEU-DEP00-INFRASTRU
     > [!NOTE]
     > The use of single quotes when setting `sap_user_password` is important. The use of special characters in the password can otherwise cause unpredictable results!
 
-    ```bash
+    ```azurecli
     sap_user_password='<sap-password>'
 
     az keyvault secret set --name "S-Password" --vault-name "${key_vault}" --value "${sap_user_password}";

articles/virtual-machines/workloads/sap/automation-tutorial.md

@@ -178,7 +178,7 @@ Use [az network public-ip show](/cli/azure/network/public-ip#az-network-public-i
     --output tsv
 ```
 
-```bash
+```azurecli
 user@Azure:~$ az network public-ip show \
 >     --resource-group myResourceGroup \
 >     --name myPublicIP-IPv4 \
@@ -195,7 +195,7 @@ user@Azure:~$ az network public-ip show \
     --output tsv
 ```
 
-```bash
+```azurecli
 user@Azure:~$ az network public-ip show \
 >     --resource-group myResourceGroup \
 >     --name myPublicIP-IPv6 \

articles/virtual-network/ip-services/create-vm-dual-stack-ipv6-cli.md

@@ -39,13 +39,13 @@ You can view the queue in the [Azure portal](../articles/storage/queues/storage-
 
     # [bash](#tab/bash)
 
-    ```bash
+    ```azurecli
     echo `echo $(az storage message get --queue-name outqueue -o tsv --query '[].{Message:content}') | base64 --decode`
     ```
 
     # [PowerShell](#tab/powershell)
 
-    ```powershell
+    ```azurecli
     [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($(az storage message get --queue-name outqueue -o tsv --query '[].{Message:content}')))
     ```