Merge pull request #104727 from TimShererWithAquent/us1669724b

[Azure CLI code blocks]

Author: v-shils

articles/ansible/ansible-create-configure-mysql.md

@@ -19,7 +19,7 @@ ms.date: 04/30/2019
 > * Create a MySql server
 > * Create a MySql database
 > * Configure a firewall rule so that an external app can connect to your server
-> * Connect to your MySql server from the Azure cloud shell
+> * Connect to your MySql server from the Azure Cloud Shell
 > * Query your available MySQL servers
 > * List all databases in your connected servers
 
@@ -150,11 +150,15 @@ ansible-playbook mysql_firewall.yml
 
 ## Connect to the server
 
-In this section, you use the Azure cloud shell to connect to the server you created previously.
+In this section, you use the Azure Cloud Shell to connect to the server you created previously.
 
-1. Select the **Try It** button in the following code:
+1. Open shell.azure.com by selecting below.
 
-    ```azurecli-interactive
+   [![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
+
+1. Enter the following code:
+
+    ```sql
     mysql -h mysqlserveransible.mysql.database.azure.com -u mysqladmin@mysqlserveransible -p
     ```
 
@@ -166,7 +170,7 @@ In this section, you use the Azure cloud shell to connect to the server you crea
 
     If everything goes well, you see output similar to the following results:
 
-    ```
+    ```output
     demo@Azure:~$ mysql -h mysqlserveransible.mysql.database.azure.com -u mysqladmin@mysqlserveransible -p
     Enter password:
     Welcome to the MySQL monitor.  Commands end with ; or \g.

articles/ansible/ansible-manage-azure-dynamic-inventories.md

@@ -86,25 +86,25 @@ Ansible provides a Python script named [azure_rm.py](https://github.com/ansible/
 
 1. Use the GNU `wget` command to retrieve the `azure_rm.py` script:
 
-    ```azurecli-interactive
+    ```python
     wget https://raw.githubusercontent.com/ansible/ansible/devel/contrib/inventory/azure_rm.py
     ```
 
 1. Use the `chmod` command to change the access permissions to the `azure_rm.py` script. The following command uses the `+x` parameter to allow for execution (running) of the specified file (`azure_rm.py`):
 
-    ```azurecli-interactive
+    ```python
     chmod +x azure_rm.py
     ```
 
 1. Use the [ansible command](https://docs.ansible.com/ansible/2.4/ansible.html) to connect to your resource group: 
 
-    ```azurecli-interactive
+    ```python
     ansible -i azure_rm.py ansible-inventory-test-rg -m ping 
     ```
 
 1. Once connected, you see results similar to the following output:
 
-    ```Output
+    ```output
     ansible-inventory-test-vm1 | SUCCESS => {
         "changed": false,
         "failed": false,
@@ -142,7 +142,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
 
 1. When running the preceding command, you could receive the following error:
 
-    ```Output
+    ```output
     Failed to connect to the host via ssh: Host key verification failed.
     ```
 
@@ -154,7 +154,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
 
 1. When you run the playbook, you see results similar to the following output:
 
-    ```Output
+    ```output
     ansible-inventory-test-vm1_0324 : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
     ansible-inventory-test-vm2_8971 : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
     ```
@@ -165,7 +165,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
 
 - Once you've set a tag, you need to "enable" that tag. One way to enable a tag is by exporting the tag to an environment variable  `AZURE_TAGS` via the `export` command:
 
-    ```azurecli-interactive
+    ```console
     export AZURE_TAGS=nginx
     ```
 
@@ -177,7 +177,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
 
     You now see only one virtual machine (the one whose tag matches the value exported into the `AZURE_TAGS` environment variable):
 
-    ```Output
+    ```output
        ansible-inventory-test-vm1 | SUCCESS => {
         "changed": false,
         "failed": false,
@@ -189,7 +189,7 @@ Starting with Ansible 2.8, Ansible provides an [Azure dynamic-inventory plug-in]
 
 - Run the command `ansible-inventory -i myazure_rm.yml --graph` to get the following output:
 
-    ```Output
+    ```output
         @all:
           |--@tag_Ansible_nginx:
           |  |--ansible-inventory-test-vm1_9e2f
@@ -210,7 +210,7 @@ The purpose of tags is to enable the ability to quickly and easily work with sub
 
 1. Create a file named `nginx.yml`:
 
-   ```azurecli-interactive
+   ```console
    code nginx.yml
    ```
 
@@ -250,7 +250,7 @@ The purpose of tags is to enable the ability to quickly and easily work with sub
 
 1. After running the playbook, you see output similar to the following results:
 
-    ```Output
+    ```output
     PLAY [Install and start Nginx on an Azure virtual machine] 
 
     TASK [Gathering Facts] 
@@ -280,13 +280,13 @@ This section illustrates one technique to test that Nginx is installed on your v
 
 1. While connected to the `ansible-inventory-test-vm1` virtual machine, run the [nginx -v](https://nginx.org/en/docs/switches.html) command to determine if Nginx is installed.
 
-    ```azurecli-interactive
+    ```console
     nginx -v
     ```
 
 1. Once you run the `nginx -v` command, you see the Nginx version (second line) that indicates that Nginx is installed.
 
-    ```Output
+    ```output
     tom@ansible-inventory-test-vm1:~$ nginx -v
 
     nginx version: nginx/1.10.3 (Ubuntu)
@@ -298,7 +298,7 @@ This section illustrates one technique to test that Nginx is installed on your v
 
 1. Doing the preceding steps for the `ansible-inventory-test-vm2` virtual machine yields an informational message indicating where you can get Nginx (which implies that you don't have it installed at this point):
 
-    ```Output
+    ```output
     tom@ansible-inventory-test-vm2:~$ nginx -v
     The program 'nginx' can be found in the following packages:
     * nginx-core

articles/ansible/ansible-run-playbook-in-cloudshell.md

@@ -8,7 +8,7 @@ ms.date: 04/30/2019
 
 # Quickstart: Run Ansible playbooks via Bash in Azure Cloud Shell
 
-Azure Cloud Shell is an interactive, browser-accessible shell for managing Azure resources. Cloud Shell provides enables you to use either a Bash or Powershell command line. In this article, you use Bash within Azure Cloud Shell to run an Ansible playbook.
+Azure Cloud Shell is an interactive, browser-accessible shell for managing Azure resources. Cloud Shell provides enables you to use either a Bash or PowerShell command line. In this article, you use Bash within Azure Cloud Shell to run an Ansible playbook.
 
 ## Prerequisites
 
@@ -30,7 +30,7 @@ az account list
 
 Using your Azure subscription ID, set the `AZURE_SUBSCRIPTION_ID` as follows:
 
-```azurecli-interactive
+```console
 export AZURE_SUBSCRIPTION_ID=<your-subscription-id>
 ```
 

articles/app-service/app-service-web-get-started-nodejs.experimental.md

@@ -1,5 +1,5 @@
 ---
-title: 'QuickStart: Create a Node.js web app'
+title: 'Quickstart: Create a Node.js web app'
 description: Deploy your first Node.js Hello World to Azure App Service in minutes. You deploy using a ZIP package, which is one of many ways to deploy to App Service.
 ms.assetid: 582bb3c2-164b-42f5-b081-95bfcb7a502a
 ms.topic: quickstart
@@ -30,21 +30,21 @@ You can follow the steps here using a Mac, Windows, or Linux machine. It takes a
 
 In the Cloud Shell, create a quickstart directory and then change to it.
 
-```azurecli-interactive
+```console
 mkdir quickstart
 
 cd $HOME/quickstart
 ```
 
 Next, run the following command to clone the sample app repository to your quickstart directory.
 
-```azurecli-interactive
+```console
 git clone https://github.com/Azure-Samples/nodejs-docs-hello-world
 ```
 
 While running, it displays information similar to the following example:
 
-```bash
+```output
 Cloning into 'nodejs-docs-hello-world'...
 remote: Counting objects: 40, done.
 remote: Total 40 (delta 0), reused 0 (delta 0), pack-reused 40
@@ -98,7 +98,7 @@ az webapp config appsettings set --resource-group myResourceGroup --name <app_na
 
 Browse to your newly created web app. Replace `<app_name>` with a unique app name.
 
-```
+```http
 http://<app_name>.azurewebsites.net
 ```
 
@@ -109,7 +109,7 @@ Here is what your new web app should look like:
 
 In the Cloud Shell, navigate to your application's root directory, create a new ZIP file for your sample project.
 
-```azurecli-interactive
+```console
 cd nodejs-docs-hello-world  
 
 zip -r myUpdatedAppFiles.zip *.*
@@ -127,7 +127,7 @@ This command deploys the files and directories from the ZIP file to your default
 
 Browse to the deployed application using your web browser.
 
-```
+```http
 http://<app_name>.azurewebsites.net
 ```
 

articles/app-service/containers/app-service-linux-ssh-support.md

@@ -48,28 +48,28 @@ az webapp create-remote-connection --subscription <subscription-id> --resource-g
 
 The command output gives you the information you need to open an SSH session.
 
-```
+```output
 Port 21382 is open
 SSH is available { username: root, password: Docker! }
 Start your favorite client and connect to port 21382
 ```
 
 Open an SSH session with your container with the client of your choice, using the local port. The following example uses the default [ssh](https://ss64.com/bash/ssh.html) command:
 
-```azurecli-interactive
+```bash
 ssh [email protected] -p <port>
 ```
 
 When being prompted, type `yes` to continue connecting. You are then prompted for the password. Use `Docker!`, which was shown to you earlier.
 
-```
+```output
 Warning: Permanently added '[127.0.0.1]:21382' (ECDSA) to the list of known hosts.
 [email protected]'s password:
 ```
 
 Once you're authenticated, you should see the session welcome screen.
 
-```
+```output
   _____
   /  _  \ __________ _________   ____
  /  /_\  \___   /  |  \_  __ \_/ __ \
@@ -85,7 +85,7 @@ You are now connected to your connector.
 
 Try running the [top](https://ss64.com/bash/top.html) command. You should be able to see your app's process in the process list. In the example output below, it's the one with `PID 263`.
 
-```
+```output
 Mem: 1578756K used, 127032K free, 8744K shrd, 201592K buff, 341348K cached
 CPU:   3% usr   3% sys   0% nic  92% idle   0% io   0% irq   0% sirq
 Load average: 0.07 0.04 0.08 4/765 45738

articles/azure-resource-manager/managed-applications/test-createuidefinition.md

@@ -62,7 +62,7 @@ For PowerShell, use:
 
 For Azure CLI, use:
 
-```azurecli
+```bash
 ./sideload-createuidef.sh \
   -l southcentralus \
   -a .\100-Marketplace-Sample
@@ -78,7 +78,7 @@ For PowerShell, use:
 
 For Azure CLI, use:
 
-```azurecli
+```bash
 ./sideload-createuidef.sh
 ```
 

articles/container-registry/container-registry-tutorial-base-image-update.md

@@ -49,7 +49,9 @@ If you haven't already done so, complete the following tutorials before proceedi
 
 Populate these shell environment variables with values appropriate for your environment. This step isn't strictly required, but makes executing the multiline Azure CLI commands in this tutorial a bit easier. If you don't populate these environment variables, you must manually replace each value wherever it appears in the example commands.
 
-```azurecli-interactive
+[![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
+
+```console
 ACR_NAME=<registry-name>        # The name of your Azure container registry
 GIT_USER=<github-username>      # Your GitHub user account name
 GIT_PAT=<personal-access-token> # The PAT you generated in the second tutorial

articles/container-registry/container-registry-tutorial-build-task.md

@@ -39,7 +39,9 @@ Now that you've completed the steps required to enable ACR Tasks to read commit
 
 First, populate these shell environment variables with values appropriate for your environment. This step isn't strictly required, but makes executing the multiline Azure CLI commands in this tutorial a bit easier. If you don't populate these environment variables, you must manually replace each value wherever it appears in the example commands.
 
-```azurecli-interactive
+[![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
+
+```console
 ACR_NAME=<registry-name>        # The name of your Azure container registry
 GIT_USER=<github-username>      # Your GitHub user account name
 GIT_PAT=<personal-access-token> # The PAT you generated in the previous section
@@ -205,13 +207,13 @@ Now that you've tested the task by manually running it, trigger it automatically
 
 First, ensure you're in the directory containing your local clone of the [repository][sample-repo]:
 
-```azurecli-interactive
+```console
 cd acr-build-helloworld-node
 ```
 
 Next, execute the following commands to create, commit, and push a new file to your fork of the repo on GitHub:
 
-```azurecli-interactive
+```console
 echo "Hello World!" > hello.txt
 git add hello.txt
 git commit -m "Testing ACR Tasks"

articles/container-registry/container-registry-tutorial-multistep-task.md

@@ -66,7 +66,9 @@ This multi-step task does the following:
 
 First, populate these shell environment variables with values appropriate for your environment. This step isn't strictly required, but makes executing the multiline Azure CLI commands in this tutorial a bit easier. If you don't populate these environment variables, you must manually replace each value wherever it appears in the example commands.
 
-```azurecli-interactive
+[![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
+
+```console
 ACR_NAME=<registry-name>        # The name of your Azure container registry
 GIT_USER=<github-username>      # Your GitHub user account name
 GIT_PAT=<personal-access-token> # The PAT you generated in the previous section
@@ -214,13 +216,13 @@ Now that you've tested the task by manually running it, trigger it automatically
 
 First, ensure you're in the directory containing your local clone of the [repository][sample-repo]:
 
-```azurecli-interactive
+```console
 cd acr-build-helloworld-node
 ```
 
 Next, execute the following commands to create, commit, and push a new file to your fork of the repo on GitHub:
 
-```azurecli-interactive
+```console
 echo "Hello World!" > hello.txt
 git add hello.txt
 git commit -m "Testing ACR Tasks"

articles/container-registry/container-registry-tutorial-quick-task.md

@@ -50,13 +50,13 @@ Once you've forked the repo, clone your fork and enter the directory containing
 
 Clone the repo with `git`, replace **\<your-github-username\>** with your GitHub username:
 
-```azurecli-interactive
+```console
 git clone https://github.com/<your-github-username>/acr-build-helloworld-node
 ```
 
 Enter the directory containing the source code:
 
-```azurecli-interactive
+```console
 cd acr-build-helloworld-node
 ```
 
@@ -70,7 +70,9 @@ Now that you've pulled the source code down to your machine, follow these steps
 
 To make executing the sample commands easier, the tutorials in this series use shell environment variables. Execute the following command to set the `ACR_NAME` variable. Replace **\<registry-name\>** with a unique name for your new container registry. The registry name must be unique within Azure, contain only lower case letters, and contain 5-50 alphanumeric characters. The other resources you create in the tutorial are based on this name, so you should need to modify only this first variable.
 
-```azurecli-interactive
+[![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
+
+```console
 ACR_NAME=<registry-name>
 ```