Validation bulk update: Fix code tags for Azure CLI code blocks - batch 6

Author: dksimpson

articles/chaos-studio/chaos-studio-quickstart-dns-outage.md

@@ -39,14 +39,14 @@ First you register a fault provider on the subscription where your network secur
 1. Launch a [Cloud Shell](https://shell.azure.com/).
 1. Replace **$SUBSCRIPTION_ID** with the Azure subscription ID containing the network security group you wish to use in your experiment and run the following command to ensure the provider will be registered on the correct subscription.
 
-    ```bash
+    ```azurecli
     az account set --subscription $SUBSCRIPTION_ID
     ```
 
 1. Drag and drop the **AzureNetworkSecurityGroupChaos.json** into the cloud shell window to upload the file.
 1. Replace **$SUBSCRIPTION_ID** used in the prior step and execute the following command to register the AzureNetworkSecurityGroupChaos fault provider.
 
-    ```bash
+    ```azurecli
     az rest --method put --url "https://management.azure.com/subscriptions/$SUBSCRIPTION_ID/providers/microsoft.chaos/chaosProviderConfigurations/AzureNetworkSecurityGroupChaos?api-version=2021-06-21-preview" --body @AzureNetworkSecurityGroupChaos.json --resource "https://management.azure.com"
     ```
 
@@ -168,6 +168,6 @@ Follow these steps if you're not going to continue to using any faults related t
 1. Launch a [Cloud Shell](https://shell.azure.com/).
 1. Replace **$SUBSCRIPTION_ID** with the Azure subscription ID where the network security group fault provider was provisioned and run the following command.
 
-    ```bash
+    ```azurecli
     az rest --method delete --url "https://management.azure.com/subscriptions/$SUBSCRIPTION_ID/providers/microsoft.chaos/chaosProviderConfigurations/AzureNetworkSecurityGroupChaos?api-version=2021-06-21-preview" --resource "https://management.azure.com"
     ```

articles/chaos-studio/chaos-studio-samples-rest-api.md

@@ -31,95 +31,95 @@ The Squall REST APIs can be used to start and stop experiments, query target sta
 
 #### Enumerate details about the Microsoft.Chaos Resource Provider
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Chaos?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### List all the operations of the Chaos Studio Resource Provider
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/providers/Microsoft.Chaos/operations?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### List Chaos Provider Configurations
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/providers/microsoft.chaos/chaosProviderConfigurations/?api-version={apiVersion}" --resource "https://management.azure.com" --verbose 
 ```
 
 #### Create Chaos Provider Configuration
 
-```bash
+```azurecli
 az rest --method put --url "https://management.azure.com/subscriptions/{subscriptionId}/providers/microsoft.chaos/chaosProviderConfigurations/{chaosProviderType}?api-version={apiVersion}" --body @{providerSettings.json} --resource "https://management.azure.com"
 ```
 
 ### Chaos Target and Agent Commands
 
 #### List All the Targets or Agents Under a Subscription
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Chaos/chaosTargets/?api-version={apiVersion}" --url-parameter "chaosProviderType={chaosProviderType}" --resource "https://management.azure.com"
 ```
 
 ### Chaos Experiment Commands
 
 #### List all experiments in a resource group
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Chaos/chaosExperiments?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### Get an experiment configuration details by name
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### Create or update an experiment
 
-```bash
+```azurecli
 az rest --method put --url "https://management.azure.com/{experimentId}?api-version={apiVersion}" --body @{experimentName.json} --resource "https://management.azure.com"
 ```
 
 #### Delete an experiment
 
-```bash
+```azurecli
 az rest --method delete --url "https://management.azure.com/{experimentId}?api-version={apiVersion}" --resource "https://management.azure.com" --verbose
 ```
 
 #### Start an experiment
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/start?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### Get statuses (History) of an experiment
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/statuses?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### Get status of an experiment
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/status?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### Cancel (Stop) an experiment
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/cancel?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### List the details of the last two experiment executions
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/executiondetails?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 
 #### List the details of a specific experiment execution
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/{experimentId}/executiondetails/{executionDetailsId}?api-version={apiVersion}" --resource "https://management.azure.com"
 ```
 

articles/chaos-studio/chaos-studio-targets-capabilities.md

@@ -52,7 +52,7 @@ An experiment can only inject faults on onboarded targets with the corresponding
 ## Listing capability names and parameters
 For reference, a list of capability names, fault URNs, and parameters is available [in our fault library](chaos-studio-fault-library.md), but you can use the HTTP response to creating a capability or do a GET on an existing capability to get this information on demand. For example, doing a GET on a VM shutdown capability:
 
-```bash
+```azurecli
 az rest --method get --url "https://management.azure.com/subscriptions/fd9ccc83-faf6-4121-9aff-2a2d685ca2a2/resourceGroups/myRG/providers/Microsoft.Compute/virtualMachines/myVM/providers/Microsoft.Chaos/targets/Microsoft-VirtualMachine/capabilities/shutdown-1.0?api-version=2021-08-11-preview"
 ```
 
@@ -83,7 +83,7 @@ Will return the following JSON:
 
 The `properties.urn` property is used to define the fault you want to run in a chaos experiment. To understand the schema for this fault's parameters, you can GET the schema referenced by `properties.parametersSchema`.
 
-```bash
+```azurecli
 az rest --method get --url "https://schema-tc.eastus.chaos-prod.azure.com/targetTypes/Microsoft-VirtualMachine/capabilityTypes/Shutdown-1.0/parametersSchema.json"
 ```
 

articles/chaos-studio/chaos-studio-tutorial-aks-portal.md

@@ -29,8 +29,11 @@ Before you can run Chaos Mesh faults in Chaos Studio, you need to install Chaos
 
 1. Run the following commands in an [Azure Cloud Shell](../cloud-shell/overview.md) window where you have the active subscription set to be the subscription where your AKS cluster is deployed. Replace `$RESOURCE_GROUP` and `$CLUSTER_NAME` with the resource group and name of your cluster resource.
 
-```bash
+```azurecli
 az aks get-credentials -g $RESOURCE_GROUP -n $CLUSTER_NAME
+```
+
+```bash
 helm repo add chaos-mesh https://charts.chaos-mesh.org
 helm repo update
 kubectl create ns chaos-testing

articles/cognitive-services/Computer-vision/spatial-analysis-container.md

@@ -252,20 +252,20 @@ Use the Azure CLI to create an instance of Azure IoT Hub. Replace the parameters
 ```bash
 curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
 ```
-```bash
+```azurecli
 sudo az login
 ```
-```bash
+```azurecli
 sudo az account set --subscription "<name or ID of Azure Subscription>"
 ```
-```bash
+```azurecli
 sudo az group create --name "<resource-group-name>" --location "<your-region>"
 ```
 See [Region Support](https://azure.microsoft.com/global-infrastructure/services/?products=cognitive-services) for available regions.
-```bash
+```azurecli
 sudo az iot hub create --name "<iothub-group-name>" --sku S1 --resource-group "<resource-group-name>"
 ```
-```bash
+```azurecli
 sudo az iot hub device-identity create --hub-name "<iothub-name>" --device-id "<device-name>" --edge-enabled
 ```
 
@@ -306,7 +306,7 @@ Next, register the host computer as an IoT Edge device in your IoT Hub instance,
 
 You need to connect the IoT Edge device to your Azure IoT Hub. You need to copy the connection string from the IoT Edge device you created earlier. Alternatively, you can run the below command in the Azure CLI.
 
-```bash
+```azurecli
 sudo az iot hub device-identity connection-string show --device-id my-edge-device --hub-name test-iot-hub-123
 ```
 
@@ -418,20 +418,20 @@ Use the Azure CLI to create an instance of Azure IoT Hub. Replace the parameters
 ```bash
 curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
 ```
-```bash
+```azurecli
 sudo az login
 ```
-```bash
+```azurecli
 sudo az account set --subscription "<name or ID of Azure Subscription>"
 ```
-```bash
+```azurecli
 sudo az group create --name "<resource-group-name>" --location "<your-region>"
 ```
 See [Region Support](https://azure.microsoft.com/global-infrastructure/services/?products=cognitive-services) for available regions.
-```bash
+```azurecli
 sudo az iot hub create --name "<iothub-name>" --sku S1 --resource-group "<resource-group-name>"
 ```
-```bash
+```azurecli
 sudo az iot hub device-identity create --hub-name "<iothub-name>" --device-id "<device-name>" --edge-enabled
 ```
 
@@ -472,7 +472,7 @@ Next, register the VM as an IoT Edge device in your IoT Hub instance, using a [c
 
 You need to connect the IoT Edge device to your Azure IoT Hub. You need to copy the connection string from the IoT Edge device you created earlier. Alternatively, you can run the below command in the Azure CLI.
 
-```bash
+```azurecli
 sudo az iot hub device-identity connection-string show --device-id my-edge-device --hub-name test-iot-hub-123
 ```
 

articles/confidential-computing/quick-create-confidential-vm-arm-amd.md

@@ -77,13 +77,13 @@ To create and deploy a confidential VM using an ARM template through the Azure C
 
 1. Sign in to your Azure account in the Azure CLI.
 
-    ```powershell-interactive
+    ```azurecli
     az login
     ```
 
 1. Set your Azure subscription. Replace `<subscription-id>` with your subscription identifier. Make sure to use a subscription that meets the [prerequisites](#prerequisites).
 
-    ```powershell-interactive
+    ```azurecli
     az account set --subscription <subscription-id>
     ```
 
@@ -101,14 +101,14 @@ To create and deploy a confidential VM using an ARM template through the Azure C
 
     If the resource group you specified doesn't exist, create a resource group with that name.
     
-    ```powershell-interactive
+    ```azurecli
     az group create -n $resourceGroup -l $region
     ```
 
 1. Deploy your VM to Azure using ARM template with custom parameter file
 
       
-    ```powershell-interactive
+    ```azurecli
     az deployment group create `
      -g $resourceGroup `
      -n $deployName `

articles/container-apps/background-processing.md

@@ -107,7 +107,7 @@ QUEUE_CONNECTION_STRING=`az storage account show-connection-string -g $RESOURCE_
 
 # [PowerShell](#tab/powershell)
 
-```powershell
+```azurecli
  $QUEUE_CONNECTION_STRING=(az storage account show-connection-string -g $RESOURCE_GROUP --name $STORAGE_ACCOUNT_NAME --query connectionString --out json)  -replace '"',''
 ```
 

articles/container-apps/microservices-dapr-azure-resource-manager.md

@@ -216,11 +216,11 @@ Next, retrieve the Log Analytics Client ID and client secret.
 
 Make sure to run each query separately to give enough time for the request to complete.
 
-```bash
+```azurecli
 LOG_ANALYTICS_WORKSPACE_CLIENT_ID=`az monitor log-analytics workspace show --query customerId -g $RESOURCE_GROUP -n $LOG_ANALYTICS_WORKSPACE -o tsv | tr -d '[:space:]'`
 ```
 
-```bash
+```azurecli
 LOG_ANALYTICS_WORKSPACE_CLIENT_SECRET=`az monitor log-analytics workspace get-shared-keys --query primarySharedKey -g $RESOURCE_GROUP -n $LOG_ANALYTICS_WORKSPACE -o tsv | tr -d '[:space:]'`
 ```
 
@@ -236,7 +236,7 @@ $LOG_ANALYTICS_WORKSPACE_CLIENT_ID=(Get-AzOperationalInsightsWorkspace -Resource
 $LOG_ANALYTICS_WORKSPACE_CLIENT_SECRET=(Get-AzOperationalInsightsWorkspaceSharedKey -ResourceGroupName $RESOURCE_GROUP -Name $LOG_ANALYTICS_WORKSPACE).PrimarySharedKey
 --->
 
-```powershell
+```azurecli
 $LOG_ANALYTICS_WORKSPACE_CLIENT_SECRET=(az monitor log-analytics workspace get-shared-keys --query primarySharedKey -g $RESOURCE_GROUP -n $LOG_ANALYTICS_WORKSPACE --out tsv)
 ```
 
@@ -308,7 +308,7 @@ Get the storage account key with the following command:
 
 # [Bash](#tab/bash)
 
-```bash
+```azurecli
 STORAGE_ACCOUNT_KEY=`az storage account keys list --resource-group $RESOURCE_GROUP --account-name $STORAGE_ACCOUNT --query '[0].value' --out tsv`
 ```
 

articles/container-apps/microservices-dapr.md

@@ -139,7 +139,7 @@ Get the storage account key with the following command:
 
 # [Bash](#tab/bash)
 
-```bash
+```azurecli
 STORAGE_ACCOUNT_KEY=`az storage account keys list --resource-group $RESOURCE_GROUP --account-name $STORAGE_ACCOUNT --query '[0].value' --out tsv`
 ```
 

articles/container-apps/monitor.md

@@ -48,7 +48,7 @@ Set the name of your resource group and Log Analytics workspace, and then retrie
 
 # [Bash](#tab/bash)
 
-```bash
+```azurecli
 RESOURCE_GROUP="my-containerapps"
 LOG_ANALYTICS_WORKSPACE="containerapps-logs"
 
@@ -57,7 +57,7 @@ LOG_ANALYTICS_WORKSPACE_CLIENT_ID=`az monitor log-analytics workspace show --que
 
 # [PowerShell](#tab/powershell)
 
-```powershell
+```azurecli
 $RESOURCE_GROUP="my-containerapps"
 $LOG_ANALYTICS_WORKSPACE="containerapps-logs"