Merge pull request #106241 from TimShererWithAquent/us1669724e

Azure CLI syntax blocks.

Author: megvanhuygen

articles/cognitive-services/Anomaly-Detector/quickstarts/detect-data-anomalies-csharp-sdk.md

@@ -51,7 +51,7 @@ dotnet build
 
 The build output should contain no warnings or errors. 
 
-```console
+```output
 ...
 Build succeeded.
  0 Warning(s)

articles/cognitive-services/Custom-Vision-Service/logo-detector-mobile.md

@@ -102,15 +102,15 @@ The app requires an Azure service principal account to deploy services to your A
 
 You can create a service principal by using either Azure Cloud Shell or the Azure CLI, as shown here. To begin, sign in and select the subscription you want to use.
 
-```console
+```azurecli
 az login
 az account list
 az account set --subscription "<subscription name or subscription id>"
 ```
 
 Then create your service principal. (This process might take some time to finish.)
 
-```console
+```azurecli
 az ad sp create-for-rbac --name <servicePrincipalName> --password <yourSPStrongPassword>
 ```
 

articles/cognitive-services/Face/QuickStarts/csharp-sdk.md

@@ -58,7 +58,7 @@ dotnet build
 
 The build output should contain no warnings or errors. 
 
-```console
+```output
 ...
 Build succeeded.
  0 Warning(s)

articles/cognitive-services/LUIS/luis-how-to-azure-subscription.md

@@ -76,21 +76,21 @@ Resource `kind`:
 
 1. Sign in to the Azure CLI:
 
-    ```console
+    ```azurecli
     az login
     ```
 
     This opens a browser to allow you to select the correct account and provide authentication.
 
 1. Create a **LUIS authoring resource**, of kind `LUIS.Authoring`, named `my-luis-authoring-resource` in the _existing_ resource group named `my-resource-group` for the `westus` region. 
 
-    ```console
+    ```azurecli
     az cognitiveservices account create -n my-luis-authoring-resource -g my-resource-group --kind LUIS.Authoring --sku F0 -l westus --yes
     ```
 
 1. Create a **LUIS prediction endpoint resource**, of kind `LUIS`, named `my-luis-prediction-resource` in the _existing_ resource group named `my-resource-group` for the `westus` region. If you want a higher throughput than the free tier, change `F0` to `S0`. Learn more about [pricing tiers and throughput](luis-boundaries.md#key-limits).
 
-    ```console
+    ```azurecli
     az cognitiveservices account create -n my-luis-prediction-resource -g my-resource-group --kind LUIS --sku F0 -l westus --yes
     ```
 

articles/cognitive-services/cognitive-services-apis-create-account-cli.md

@@ -29,7 +29,7 @@ In this quickstart, you'll learn how to sign up for Azure Cognitive Services and
 
 Install the [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest). To sign into your local installation of the CLI, run the [az login](https://docs.microsoft.com/cli/azure/reference-index#az-login) command:
 
-```console
+```azurecli-interactive
 az login
 ```
 
@@ -151,7 +151,7 @@ az cognitiveservices account create \
 
 To log into your local installation of the Command-Line Interface(CLI), use the [az login](https://docs.microsoft.com/cli/azure/reference-index?view=azure-cli-latest#az-login) command.
 
-```console
+```azurecli-interactive
 az login
 ```
 

articles/cognitive-services/containers/azure-kubernetes-recipe.md

@@ -75,8 +75,11 @@ To deploy the container to the Azure Kubernetes Service, the container images ne
 
     Save the results to get the **loginServer** property. This will be part of the hosted container's address, used later in the `language.yml` file.
 
-    ```console
-    > az acr create --resource-group cogserv-container-rg --name pattyregistry --sku Basic
+    ```azurecli-interactive
+    az acr create --resource-group cogserv-container-rg --name pattyregistry --sku Basic
+    ```
+
+    ```output
     {
         "adminUserEnabled": false,
         "creationDate": "2019-01-02T23:49:53.783549+00:00",
@@ -131,8 +134,7 @@ To deploy the container to the Azure Kubernetes Service, the container images ne
 
     When the process is done, the results should be similar to:
 
-    ```console
-    > docker push pattyregistry.azurecr.io/language-frontend:v1
+    ```output
     The push refers to repository [pattyregistry.azurecr.io/language-frontend]
     82ff52ee6c73: Pushed
     07599c047227: Pushed
@@ -175,8 +177,7 @@ The following steps are needed to get the required information to connect your c
 
     Save the results `appId` value for the assignee parameter in step 3, `<appId>`. Save the `password` for the next section's client-secret parameter `<client-secret>`.
 
-    ```console
-    > az ad sp create-for-rbac --skip-assignment
+    ```output
     {
       "appId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
       "displayName": "azure-cli-2018-12-31-18-39-32",
@@ -194,8 +195,7 @@ The following steps are needed to get the required information to connect your c
 
     Save the output for the scope parameter value, `<acrId>`, in the next step. It looks like:
 
-    ```console
-    > az acr show --resource-group cogserv-container-rg --name pattyregistry --query "id" --o table
+    ```output
     /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/cogserv-container-rg/providers/Microsoft.ContainerRegistry/registries/pattyregistry
     ```
 
@@ -217,8 +217,7 @@ The following steps are needed to get the required information to connect your c
 
     This step may take a few minutes. The result is:
 
-    ```console
-    > az aks create --resource-group cogserv-container-rg --name patty-kube --node-count 2  --service-principal <appId>  --client-secret <client-secret>  --generate-ssh-keys
+    ```output
     {
       "aadProfile": null,
       "addonProfiles": null,
@@ -295,8 +294,7 @@ This section uses the **kubectl** CLI to talk with the Azure Kubernetes Service.
 
     The response looks like:
 
-    ```console
-    > kubectl get nodes
+    ```output
     NAME                       STATUS    ROLES     AGE       VERSION
     aks-nodepool1-13756812-0   Ready     agent     6m        v1.9.11
     aks-nodepool1-13756812-1   Ready     agent     6m        v1.9.11
@@ -332,8 +330,7 @@ This section uses the **kubectl** CLI to talk with the Azure Kubernetes Service.
 
     The response is:
 
-    ```console
-    > kubectl apply -f language.yml
+    ```output
     service "language-frontend" created
     deployment.apps "language-frontend" created
     service "language" created
@@ -348,8 +345,7 @@ For the two containers, verify the `language-frontend` and `language` services a
 kubectl get all
 ```
 
-```console
-> kubectl get all
+```output
 NAME                                     READY     STATUS    RESTARTS   AGE
 pod/language-586849d8dc-7zvz5            1/1       Running   0          13h
 pod/language-frontend-68b9969969-bz9bg   1/1       Running   1          13h

articles/container-service/dcos-swarm/container-service-dcos-acr.md

@@ -97,7 +97,7 @@ Run the following command to login to the Azure Container Registry. Replace the
 
 This command stores the authentication values locally under the `~/.docker` path.
 
-```azurecli-interactive
+```console
 docker -H tcp://localhost:2375 login --username=myContainerRegistry23489 --password=//=ls++q/m+w+pQDb/xCi0OhD=2c/hST mycontainerregistry.azurecr.io
 ```
 

articles/container-service/dcos-swarm/container-service-dcos-manage-tutorial.md

@@ -13,7 +13,7 @@ ms.custom: mvc
 
 [!INCLUDE [ACS deprecation](../../../includes/container-service-deprecation.md)]
 
-DC/OS provides a distributed platform for running modern and containerized applications. With Azure Container Service, provisioning of a production ready DC/OS cluster is simple and quick. This quick start details basic steps needed to deploy a DC/OS cluster and run basic workload.
+DC/OS provides a distributed platform for running modern and containerized applications. With Azure Container Service, provisioning of a production ready DC/OS cluster is simple and quick. This quickstart details basic steps needed to deploy a DC/OS cluster and run basic workload.
 
 > [!div class="checklist"]
 > * Create an ACS DC/OS cluster
@@ -61,7 +61,7 @@ ip=$(az network public-ip list --resource-group myResourceGroup --query "[?conta
 
 To create the SSH tunnel, run the following command and follow the on-screen instructions. If port 80 is already in use, the command fails. Update the tunneled port to one not in use, such as `85:localhost:80`. 
 
-```azurecli
+```console
 sudo ssh -i ~/.ssh/id_rsa -fNL 80:localhost:80 -p 2200 azureuser@$ip
 ```
 
@@ -75,7 +75,7 @@ az acs dcos install-cli
 
 Before the CLI can be used with the cluster, it must be configured to use the SSH tunnel. To do so, run the following command, adjusting the port if needed.
 
-```azurecli
+```console
 dcos config set core.dcos_url http://localhost
 ```
 
@@ -111,19 +111,19 @@ The default scheduling mechanism for an ACS DC/OS cluster is Marathon. Marathon
 
 Run the following command to schedule the application to run on the DC/OS cluster.
 
-```azurecli
+```console
 dcos marathon app add marathon-app.json
 ```
 
 To see the deployment status for the app, run the following command.
 
-```azurecli
+```console
 dcos marathon app list
 ```
 
 When the **TASKS** column value switches from *0/1* to *1/1*, application deployment has completed.
 
-```azurecli
+```output
 ID     MEM  CPUS  TASKS  HEALTH  DEPLOYMENT  WAITING  CONTAINER  CMD   
 /test   32   1     0/1    ---       ---      False      DOCKER   None
 ```
@@ -160,19 +160,19 @@ In the previous example, a single instance application was created. To update th
 
 Update the application using the `dcos marathon app update` command.
 
-```azurecli
+```console
 dcos marathon app update demo-app-private < marathon-app.json
 ```
 
 To see the deployment status for the app, run the following command.
 
-```azurecli
+```console
 dcos marathon app list
 ```
 
 When the **TASKS** column value switches from *1/3* to *3/1*, application deployment has completed.
 
-```azurecli
+```output
 ID     MEM  CPUS  TASKS  HEALTH  DEPLOYMENT  WAITING  CONTAINER  CMD   
 /test   32   1     1/3    ---       ---      False      DOCKER   None
 ```
@@ -217,13 +217,13 @@ Create a file named **nginx-public.json** and copy the following contents into i
 
 Run the following command to schedule the application to run on the DC/OS cluster.
 
-```azurecli 
+```console
 dcos marathon app add nginx-public.json
 ```
 
 Get the public IP address of the DC/OS public cluster agents.
 
-```azurecli 
+```azurecli
 az network public-ip list --resource-group myResourceGroup --query "[?contains(name,'dcos-agent')].[ipAddress]" -o tsv
 ```
 
@@ -251,7 +251,7 @@ az acs scale --resource-group myResourceGroup --name myDCOSCluster --new-agent-c
 
 When no longer needed, you can use the [az group delete](/cli/azure/group#az-group-delete) command to remove the resource group, DC/OS cluster, and all related resources.
 
-```azurecli 
+```azurecli
 az group delete --name myResourceGroup --no-wait
 ```
 

articles/container-service/dcos-swarm/container-service-dcos-quickstart.md

@@ -13,7 +13,7 @@ ms.custom: mvc
 
 [!INCLUDE [ACS deprecation](../../../includes/container-service-deprecation.md)]
 
-DC/OS provides a distributed platform for running modern and containerized applications. With Azure Container Service, provisioning of a production ready DC/OS cluster is simple and quick. This quick start details the basic steps needed to deploy a DC/OS cluster and run basic workload.
+DC/OS provides a distributed platform for running modern and containerized applications. With Azure Container Service, provisioning of a production ready DC/OS cluster is simple and quick. This quickstart details the basic steps needed to deploy a DC/OS cluster and run basic workload.
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
@@ -123,19 +123,19 @@ The default scheduling mechanism for an ACS DC/OS cluster is Marathon. Marathon
 
 Run the following command to schedule the application to run on the DC/OS cluster.
 
-```azurecli
+```console
 dcos marathon app add marathon-app.json
 ```
 
 To see the deployment status for the app, run the following command.
 
-```azurecli
+```console
 dcos marathon app list
 ```
 
 When the **WAITING** column value switches from *True* to *False*, application deployment has completed.
 
-```azurecli
+```output
 ID     MEM  CPUS  TASKS  HEALTH  DEPLOYMENT  WAITING  CONTAINER  CMD   
 /test   32   1     1/1    ---       ---      False      DOCKER   None
 ```
@@ -160,7 +160,7 @@ az group delete --name myResourceGroup --no-wait
 
 ## Next steps
 
-In this quick start, you’ve deployed a DC/OS cluster and have run a simple Docker container on the cluster. To learn more about Azure Container Service, continue to the ACS tutorials.
+In this quickstart, you’ve deployed a DC/OS cluster and have run a simple Docker container on the cluster. To learn more about Azure Container Service, continue to the ACS tutorials.
 
 > [!div class="nextstepaction"]
 > [Manage an ACS DC/OS Cluster](container-service-dcos-manage-tutorial.md)

articles/container-service/kubernetes/container-service-tutorial-kubernetes-prepare-acr.md

@@ -70,7 +70,7 @@ docker images
 
 Output:
 
-```bash
+```output
 REPOSITORY                   TAG                 IMAGE ID            CREATED             SIZE
 azure-vote-front             latest              4675398c9172        13 minutes ago      694MB
 redis                        latest              a1b99da73d05        7 days ago          106MB
@@ -99,7 +99,7 @@ docker images
 
 Output:
 
-```bash
+```output
 REPOSITORY                                           TAG                 IMAGE ID            CREATED             SIZE
 azure-vote-front                                     latest              eaf2b9c57e5e        8 minutes ago       716 MB
 mycontainerregistry082.azurecr.io/azure-vote-front   v1            eaf2b9c57e5e        8 minutes ago       716 MB
@@ -129,7 +129,7 @@ az acr repository list --name <acrName> --output table
 
 Output:
 
-```azurecli
+```output
 Result
 ----------------
 azure-vote-front
@@ -143,7 +143,7 @@ az acr repository show-tags --name <acrName> --repository azure-vote-front --out
 
 Output:
 
-```azurecli
+```output
 Result
 --------
 v1