Merge pull request #104511 from john-par/1669724-update-documents-with-correct-azure-cli-tags-02-14

1669724, update documents with correct azure cli tags 02-14

Author: megvanhuygen

articles/aks/deployment-center-launcher.md

@@ -34,7 +34,7 @@ In this tutorial, you will:
 
 1. To create the AKS cluster, run the following commands:
 
-    ```cmd
+    ```azurecli
     # Create a resource group in the South India location:
 
     az group create --name azooaks --location southindia

articles/dev-spaces/get-started-java.md

@@ -26,7 +26,7 @@ Azure Dev Spaces requires minimal local machine setup. Most of your dev space's
 ### Sign in to Azure CLI
 Sign in to Azure. Type the following command in a terminal window:
 
-```cmd
+```azurecli
 az login
 ```
 
@@ -36,28 +36,28 @@ az login
 #### If you have multiple Azure subscriptions...
 You can view your subscriptions by running: 
 
-```cmd
+```azurecli
 az account list --output table
 ```
 
 Locate the  subscription which has *True* for *IsDefault*.
 If this isn't the subscription you want to use, you can change the default subscription:
 
-```cmd
+```azurecli
 az account set --subscription <subscription ID>
 ```
 
 ## Create a Kubernetes cluster enabled for Azure Dev Spaces
 
 At the command prompt, create the resource group in a [region that supports Azure Dev Spaces][supported-regions].
 
-```cmd
+```azurecli
 az group create --name MyResourceGroup --location <region>
 ```
 
 Create a Kubernetes cluster with the following command:
 
-```cmd
+```azurecli
 az aks create -g MyResourceGroup -n MyAKS --location <region> --generate-ssh-keys
 ```
 
@@ -67,7 +67,7 @@ It takes a few minutes to create the cluster.
 
 Enter the following Azure CLI command, using the resource group that contains your AKS cluster, and your AKS cluster name. The command configures your cluster with support for Azure Dev Spaces.
 
-   ```cmd
+   ```azurecli
    az aks use-dev-spaces -g MyResourceGroup -n MyAKS
    ```
 

articles/dev-spaces/get-started-netcore.md

@@ -23,7 +23,7 @@ Azure Dev Spaces requires minimal local machine setup. Most of your dev space's
 ### Sign in to Azure CLI
 Sign in to Azure. Type the following command in a terminal window:
 
-```cmd
+```azurecli
 az login
 ```
 
@@ -33,28 +33,28 @@ az login
 #### If you have multiple Azure subscriptions...
 You can view your subscriptions by running: 
 
-```cmd
+```azurecli
 az account list --output table
 ```
 
 Locate the subscription which has *True* for *IsDefault*.
 If this isn't the subscription you want to use, you can change the default subscription:
 
-```cmd
+```azurecli
 az account set --subscription <subscription ID>
 ```
 
 ## Create a Kubernetes cluster enabled for Azure Dev Spaces
 
 At the command prompt, create the resource group in a [region that supports Azure Dev Spaces][supported-regions].
 
-```cmd
+```azurecli
 az group create --name MyResourceGroup --location <region>
 ```
 
 Create a Kubernetes cluster with the following command:
 
-```cmd
+```azurecli
 az aks create -g MyResourceGroup -n MyAKS --location <region> --generate-ssh-keys
 ```
 
@@ -64,7 +64,7 @@ It takes a few minutes to create the cluster.
 
 Enter the following Azure CLI command, using the resource group that contains your AKS cluster, and your AKS cluster name. The command configures your cluster with support for Azure Dev Spaces.
 
-   ```cmd
+   ```azurecli
    az aks use-dev-spaces -g MyResourceGroup -n MyAKS
    ```
 
@@ -251,4 +251,4 @@ Refresh the web app in the browser, and go to the About page. You should see you
 > [Learn about multi-service development](multi-service-netcore.md)
 
 
-[supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
+[supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service

articles/dev-spaces/get-started-nodejs.md

@@ -23,7 +23,7 @@ Azure Dev Spaces requires minimal local machine setup. Most of your dev space's
 ### Sign in to Azure CLI
 Sign in to Azure. Type the following command in a terminal window:
 
-```cmd
+```azurecli
 az login
 ```
 
@@ -33,28 +33,28 @@ az login
 #### If you have multiple Azure subscriptions...
 You can view your subscriptions by running: 
 
-```cmd
+```azurecli
 az account list --output table
 ```
 
 Locate the subscription which has *True* for *IsDefault*.
 If this isn't the subscription you want to use, you can change the default subscription:
 
-```cmd
+```azurecli
 az account set --subscription <subscription ID>
 ```
 
 ## Create a Kubernetes cluster enabled for Azure Dev Spaces
 
 At the command prompt, create the resource group in a [region that supports Azure Dev Spaces][supported-regions].
 
-```cmd
+```azurecli
 az group create --name MyResourceGroup --location <region>
 ```
 
 Create a Kubernetes cluster with the following command:
 
-```cmd
+```azurecli
 az aks create -g MyResourceGroup -n MyAKS --location <region> --generate-ssh-keys
 ```
 
@@ -64,7 +64,7 @@ It takes a few minutes to create the cluster.
 
 Enter the following Azure CLI command, using the resource group that contains your AKS cluster, and your AKS cluster name. The command configures your cluster with support for Azure Dev Spaces.
 
-   ```cmd
+   ```azurecli
    az aks use-dev-spaces -g MyResourceGroup -n MyAKS
    ```
 
@@ -278,4 +278,4 @@ In this configuration, the container is configured to start *nodemon*. When serv
 > [Learn about multi-service development](multi-service-nodejs.md)
 
 
-[supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
+[supported-regions]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service

articles/dev-spaces/how-to/dev-spaces-business-continuity.md

@@ -35,7 +35,7 @@ Repeat this process for each cluster.
 
 You can also enable Dev Spaces at the command line:
 
-```cmd
+```azurecli
 az aks use-dev-spaces -g <resource group name> -n <cluster name>
 ```
 
@@ -51,7 +51,7 @@ Once you've properly configured a backup cluster running your team's baseline, y
 
 Select a different cluster with the following CLI command:
 
-```cmd
+```azurecli
 az aks use-dev-spaces -g <new resource group name> -n <new cluster name>
 ```
 

articles/dev-spaces/how-to/github-actions.md

@@ -33,7 +33,7 @@ In this guide, you will learn how to:
 
 Create an Azure Container Registry (ACR):
 
-```cmd
+```azurecli
 az acr create --resource-group MyResourceGroup --name <acrName> --sku Basic
 ```
 
@@ -46,27 +46,27 @@ Save the *loginServer* value from the output because it is used in a later step.
 
 Use [az ad sp create-for-rbac][az-ad-sp-create-for-rbac] to create a service principal. For example:
 
-```cmd
+```azurecli
 az ad sp create-for-rbac --sdk-auth --skip-assignment
 ```
 
 Save the JSON output because it is used in a later step.
 
 Use [az aks show][az-aks-show] to display the *ID* of your AKS cluster:
 
-```cmd
+```azurecli
 az aks show -g MyResourceGroup -n MyAKS  --query id
 ```
 
 Use [az acr show][az-acr-show] to display the *ID* of the ACR:
 
-```cmd
+```azurecli
 az acr show --name <acrName> --query id
 ```
 
 Use [az role assignment create][az-role-assignment-create] to give *Contributor* access to your AKS cluster and *AcrPush* access to your ACR.
 
-```cmd
+```azurecli
 az role assignment create --assignee <ClientId> --scope <AKSId> --role Contributor
 az role assignment create --assignee <ClientId>  --scope <ACRId> --role AcrPush
 ```
@@ -152,7 +152,7 @@ If you merge your changes into the *master* branch in your fork, another action
 
 ## Clean up your Azure resources
 
-```cmd
+```azurecli
 az group delete --name MyResourceGroup --yes --no-wait
 ```
 

articles/dev-spaces/how-to/install-dev-spaces.md

@@ -20,15 +20,13 @@ Before you can install Dev Spaces using the CLI, you need:
 
 Use the `use-dev-spaces` command to enable Dev Spaces on your AKS cluster and follow the prompts.
 
-```cmd
+```azurecli
 az aks use-dev-spaces -g myResourceGroup -n myAKSCluster
 ```
 
 The above command enables Dev Spaces on the *myAKSCluster* cluster in the *myResourceGroup* group and creates a *default* dev space.
 
-```cmd
-$ az aks use-dev-spaces -g myResourceGroup -n myAKSCluster
-
+```console
 'An Azure Dev Spaces Controller' will be created that targets resource 'myAKSCluster' in resource group 'myResourceGroup'. Continue? (y/N): y
 
 Creating and selecting Azure Dev Spaces Controller 'myAKSCluster' in resource group 'myResourceGroup' that targets resource 'myAKSCluster' in resource group 'myResourceGroup'...2m 24s

articles/jenkins/deploy-jenkins-app-service-plugin.md

@@ -204,10 +204,13 @@ For the **Docker registry URL** value, supply the URL by using the format https:
 ### For Azure App Service on Linux
 
 1. To verify your web app, run the following command in the Azure CLI:
-    ```CLI
+    
+    ```azurecli
     az acr repository list -n <myRegistry> -o json
     ```
+    
     The following message is displayed:
+    
     ```CLI
     ["calculator"]
     ```

articles/jenkins/jenkins-azure-functions-deploy.md

@@ -26,19 +26,19 @@ The following steps show how to create a Java function using the Azure CLI:
 
 1. Create a resource group, replacing the **<resource_group>** placeholder with your resource group name.
 
-    ```cli
+    ```azurecli
     az group create --name <resource_group> --location eastus
     ```
 
 1. Create an Azure storage account, replacing the placeholders with the appropriate values.
  
-    ```cli
+    ```azurecli
     az storage account create --name <storage_account> --location eastus --resource-group <resource_group> --sku Standard_LRS    
     ```
 
 1. Create the test function app, replacing the placeholders with the appropriate values.
 
-    ```cli
+    ```azurecli
     az functionapp create --resource-group <resource_group> --consumption-plan-location eastus --name <function_app> --storage-account <storage_account>
     ```
 
@@ -144,7 +144,7 @@ It's now time to run the Jenkins job.
 If you're not going to continue to use this application, delete
 the resources you created with the following step:
 
-```cli
+```azurecli
 az group delete -y --no-wait -n <resource_group>
 ```
 

articles/service-fabric-mesh/service-fabric-mesh-faq.md

@@ -41,8 +41,11 @@ If you see this happen, you can validate that the system shut it down by running
 
 For example: 
 
-```cli
-~$ az mesh app show --resource-group myResourceGroup --name helloWorldApp
+```azurecli
+az mesh app show --resource-group myResourceGroup --name helloWorldApp
+```
+
+```output
 {
   "debugParams": null,
   "description": "Service Fabric Mesh HelloWorld Application!",