Merge pull request #108788 from TimShererWithAquent/us1669724t

Jak-MS · web-flow · commit c9d29e30b248 · 2020-03-24T14:15:50.000-06:00
Azure CLI syntax blocks.
diff --git a/articles/hpc-cache/hpc-cache-netapp.md b/articles/hpc-cache/hpc-cache-netapp.md
@@ -71,7 +71,7 @@ Follow the [mount instructions in the Azure NetApp Files documentation](../azure
 
 You also can find IP addresses with the Azure CLI:
 
-```bash
+```azurecli
 az netappfiles volume list -g ${RESOURCE_GROUP} --account-name ${ANF_ACCOUNT} --pool-name ${POOL} --query "[].mountTargets[].ipAddress" | grep -Ee '[0-9]+[.][0-9]+[.][0-9]+[.][0-9]+' | tr -d '"' | tr -d , | sort | uniq
 ```
 
diff --git a/articles/iot-accelerators/howto-opc-twin-deploy-modules.md b/articles/iot-accelerators/howto-opc-twin-deploy-modules.md
@@ -181,7 +181,7 @@ The easiest way to deploy the modules to an Azure IoT Edge gateway device is thr
 
 2. Use the following command to apply the configuration to an IoT Edge device:
 
-   ```bash
+   ```azurecli
    az iot edge set-modules --device-id [device id] --hub-name [hub name] --content ./deployment.json
    ```
 
@@ -190,7 +190,7 @@ The easiest way to deploy the modules to an Azure IoT Edge gateway device is thr
 
 3. Once you've deployed modules to your device, you can view all of them with the following command:
 
-   ```bash
+   ```azurecli
    az iot hub module-identity list --device-id [device id] --hub-name [hub name]
    ```
 
diff --git a/articles/iot-accelerators/iot-accelerators-remote-monitoring-customize-page.md b/articles/iot-accelerators/iot-accelerators-remote-monitoring-customize-page.md
@@ -153,15 +153,15 @@ Optionally, you can connect your local running copy of the web UI to the Remote
 
 1. Use the Azure portal or the [az CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest) to enable SSH access to the virtual machine that hosts the microservices in your solution. For example:
 
-    ```sh
+    ```azurecli
     az network nsg rule update --name SSH --nsg-name {your solution name}-nsg --resource-group {your solution name} --access Allow
     ```
 
     You should only enable SSH access during test and development. If you enable SSH, [you should disable it again as soon as possible](../security/fundamentals/network-best-practices.md).
 
 1. Use the Azure portal or the [az CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest) to find the name and public IP address of your virtual machine. For example:
 
-    ```sh
+    ```azurecli
     az resource list --resource-group {your solution name} -o table
     az vm list-ip-addresses --name {your vm name from previous command} --resource-group {your solution name} -o table
     ```
diff --git a/articles/iot-central/core/howto-monitor-devices-azure-cli.md b/articles/iot-central/core/howto-monitor-devices-azure-cli.md
@@ -27,19 +27,19 @@ Use the Azure CLI IoT extension to see messages your devices are sending to IoT
 
 Run the following command from your command line to install:
 
-```cmd/sh
+```azurecli
 az extension add --name azure-iot
 ```
 
 Check the version of the extension by running:
 
-```cmd/sh
+```azurecli
 az --version
 ```
 
 You should see the azure-iot extension is 0.8.1 or higher. If it is not, run:
 
-```cmd/sh
+```azurecli
 az extension update --name azure-iot
 ```
 
@@ -53,7 +53,7 @@ The following sections describe common commands and options that you can use whe
 
 Start by signing into the Azure CLI. 
 
-```cmd/sh
+```azurecli
 az login
 ```
 
@@ -63,14 +63,14 @@ In **Administration/Application Settings**, copy the **Application ID**. You wil
 ### Monitor messages
 Monitor the messages that are being sent to your IoT Central app from your devices. This will include all headers and annotations.
 
-```cmd/sh
+```azurecli
 az iot central app monitor-events --app-id <app-id> --properties all
 ```
 
 ### View device properties
 View the current read and read/write device properties for a given device.
 
-```cmd/sh
+```azurecli
 az iot central device-twin show --app-id <app-id> --device-id <device-id>
 ```
 
diff --git a/articles/iot-edge/how-to-deploy-modules-cli.md b/articles/iot-edge/how-to-deploy-modules-cli.md
@@ -111,7 +111,7 @@ Change directories into the folder where your deployment manifest is saved. If y
 
 Use the following command to apply the configuration to an IoT Edge device:
 
-   ```cli
+   ```azurecli
    az iot edge set-modules --device-id [device id] --hub-name [hub name] --content [file path]
    ```
 
@@ -125,7 +125,7 @@ Once you've deployed modules to your device, you can view all of them with the f
 
 View the modules on your IoT Edge device:
 
-   ```cli
+   ```azurecli
    az iot hub module-identity list --device-id [device id] --hub-name [hub name]
    ```
 
diff --git a/articles/iot-edge/how-to-register-device.md b/articles/iot-edge/how-to-register-device.md
@@ -119,7 +119,7 @@ The [Azure CLI](https://docs.microsoft.com/cli/azure?view=azure-cli-latest) is a
 
 Use the [az iot hub device-identity create](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-create) command to create a new device identity in your IoT hub. For example:
 
-   ```cli
+   ```azurecli
    az iot hub device-identity create --device-id [device id] --hub-name [hub name] --edge-enabled
    ```
 
@@ -135,7 +135,7 @@ This command includes three parameters:
 
 Use the [az iot hub device-identity list](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-list) command to view all devices in your IoT hub. For example:
 
-   ```cli
+   ```azurecli
    az iot hub device-identity list --hub-name [hub name]
    ```
 
@@ -145,7 +145,7 @@ Any device that is registered as an IoT Edge device will have the property **cap
 
 When you're ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub. Use the [az iot hub device-identity show-connection-string](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-hub-device-identity-show-connection-string) command to return the connection string for a single device:
 
-   ```cli
+   ```azurecli
    az iot hub device-identity show-connection-string --device-id [device id] --hub-name [hub name]
    ```
 
diff --git a/articles/iot-edge/offline-capabilities.md b/articles/iot-edge/offline-capabilities.md
@@ -65,7 +65,7 @@ You can declare the parent-child relationship when creating a new device. Or for
 
 Using the [Azure command-line interface](https://docs.microsoft.com/cli/azure/?view=azure-cli-latest) with [IoT extension](https://github.com/azure/azure-iot-cli-extension) (v0.7.0 or newer), you can manage parent child relationships with the [device-identity](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/hub/device-identity?view=azure-cli-latest) subcommands. The example below uses a query to assign all non-IoT Edge devices in the hub to be child devices of an IoT Edge device.
 
-```shell
+```azurecli
 # Set IoT Edge parent device
 egde_device="edge-device1"
 
diff --git a/articles/iot-edge/quickstart-linux.md b/articles/iot-edge/quickstart-linux.md
@@ -133,7 +133,7 @@ If you're running IoT Edge on your local machine or an ARM32 or ARM64 device, yo
 
 The rest of the commands in this quickstart take place on your IoT Edge device itself, so that you can see what's happening on the device. If you're using a virtual machine, connect to that machine now using the public IP address that was output by the creation command. You can also find the public IP address on your virtual machine's overview page in the Azure portal. Use the following command to connect to your virtual machine. Replace `{azureuser}` if you used a different username than the one suggested in the prerequisites. Replace `{publicIpAddress}` with your machine's address.
 
-   ```azurecli-interactive
+   ```console
    ssh azureuser@{publicIpAddress}
    ```
 
diff --git a/articles/iot-edge/tutorial-machine-learning-edge-05-configure-edge-device.md b/articles/iot-edge/tutorial-machine-learning-edge-05-configure-edge-device.md
@@ -190,7 +190,7 @@ We will deal with the leaf device later in the tutorial. In this section, downlo
 
 1. From the SSH session on the Linux virtual machine, sign in to Azure with the Azure CLI.
 
-    ```bash
+    ```azurecli
     az login
     ```
 
@@ -200,7 +200,7 @@ We will deal with the leaf device later in the tutorial. In this section, downlo
 
 1. Set the Azure subscription that you want to use for Azure CLI commands.
 
-    ```bash
+    ```azurecli
     az account set --subscription <subscriptionId>
     ```
 
@@ -212,7 +212,7 @@ We will deal with the leaf device later in the tutorial. In this section, downlo
 
 1. Download the certificates that you stored in the key vault: new-edge-device-full-chain.cert.pem, new-edge-device.key.pem, and azure-iot-test-only.root.ca.cert.pem
 
-    ```bash
+    ```azurecli
     key_vault_name="<key vault name>"
     sudo az keyvault secret download --vault-name $key_vault_name --name new-edge-device-full-chain-cert-pem -f /edgeMlCertificates/new-edge-device-full-chain.cert.pem
     sudo az keyvault secret download --vault-name $key_vault_name --name new-edge-device-key-pem -f /edgeMlCertificates/new-edge-device.key.pem
diff --git a/articles/iot-hub/iot-hub-arduino-iot-devkit-az3166-get-started.md b/articles/iot-hub/iot-hub-arduino-iot-devkit-az3166-get-started.md
@@ -139,7 +139,7 @@ The DevKit connects to a device-specific endpoint on your IoT hub and sends temp
 
 1. To verify the telemetry data sent to Azure, run the following command in Azure Cloud Shell:
 
-    ```bash
+    ```azurecli
     az iot hub monitor-events --hub-name YourIoTHubName --output table
     ```
 
diff --git a/articles/iot-hub/iot-hub-automatic-device-management-cli.md b/articles/iot-hub/iot-hub-automatic-device-management-cli.md
@@ -117,7 +117,7 @@ You configure target devices by creating a configuration that consists of the ta
 
 Use the following command to create a configuration:
 
-```cli
+```azurecli
    az iot hub configuration create --config-id [configuration id] \
      --labels [labels] --content [file path] --hub-name [hub name] \
      --target-condition [target query] --priority [int] \
@@ -142,7 +142,7 @@ Use the following command to create a configuration:
 
 Use the following command to display the contents of a configuration:
 
-```cli
+```azurecli
 az iot hub configuration show --config-id [configuration id] \
   --hub-name [hub name]
 ```
@@ -161,7 +161,7 @@ Inspect the configuration in the command window. The **metrics** property lists
 
 You can show a list of device IDs, module IDs, or objects for each of the metrics by using the following command:
 
-```cli
+```azurecli
 az iot hub configuration show-metric --config-id [configuration id] \
    --metric-id [metric id] --hub-name [hub name] --metric-type [type] 
 ```
@@ -188,7 +188,7 @@ If you update the target condition, the following updates occur:
 
 Use the following command to update a configuration:
 
-```cli
+```azurecli
 az iot hub configuration update --config-id [configuration id] \
    --hub-name [hub name] --set [property1.property2='value']
 ```
@@ -211,10 +211,11 @@ When you delete a configuration, any device twins or module twins take on their
 
 Use the following command to delete a configuration:
 
-```cli
+```azurecli
 az iot hub configuration delete --config-id [configuration id] \
    --hub-name [hub name] 
 ```
+
 * --**config-id** - The name of the configuration that exists in the IoT hub.
 
 * --**hub-name** - Name of the IoT hub in which the configuration exists. The hub must be in the current subscription. Switch to the desired subscription with the command `az account set -s [subscription name]`.
diff --git a/articles/iot-hub/iot-hub-device-management-iot-extension-azure-cli-2-0.md b/articles/iot-hub/iot-hub-device-management-iot-extension-azure-cli-2-0.md
@@ -66,13 +66,13 @@ Run Azure CLI and the IoT extension for Azure CLI with various management option
 
 Sign in to your Azure account by running the following command:
 
-```bash
+```azurecli
 az login
 ```
 
 ## Direct methods
 
-```bash
+```azurecli
 az iot hub invoke-device-method --device-id <your device id> \
   --hub-name <your hub name> \
   --method-name <the method name> \
@@ -83,7 +83,7 @@ az iot hub invoke-device-method --device-id <your device id> \
 
 Set a desired property interval = 3000 by running the following command:
 
-```bash
+```azurecli
 az iot hub device-twin update -n <your hub name> \
   -d <your device id> --set properties.desired.interval = 3000
 ```
@@ -94,7 +94,7 @@ This property can be read from your device.
 
 Get the reported properties of the device by running the following command:
 
-```bash
+```azurecli
 az iot hub device-twin show -n <your hub name> -d <your device id>
 ```
 
@@ -104,13 +104,13 @@ One of the twin reported properties is $metadata.$lastUpdated, which shows the l
 
 Display the tags and properties of the device by running the following command:
 
-```bash
+```azurecli
 az iot hub device-twin show --hub-name <your hub name> --device-id <your device id>
 ```
 
 Add a field role = temperature&humidity to the device by running the following command:
 
-```bash
+```azurecli
 az iot hub device-twin update \
   --hub-name <your hub name> \
   --device-id <your device id> \
@@ -121,14 +121,14 @@ az iot hub device-twin update \
 
 Query devices with a tag of role = 'temperature&humidity' by running the following command:
 
-```bash
+```azurecli
 az iot hub query --hub-name <your hub name> \
   --query-command "SELECT * FROM devices WHERE tags.role = 'temperature&humidity'"
 ```
 
 Query all devices except those with a tag of role = 'temperature&humidity' by running the following command:
 
-```bash
+```azurecli
 az iot hub query --hub-name <your hub name> \
   --query-command "SELECT * FROM devices WHERE tags.role != 'temperature&humidity'"
 ```
diff --git a/articles/iot-pnp/concepts-common-interfaces.md b/articles/iot-pnp/concepts-common-interfaces.md
@@ -32,11 +32,11 @@ All IoT Plug and Play devices are expected to implement some common interfaces.
 
 You can use the Azure IoT extension for Azure CLI to retrieve the common interfaces from the public model repository.
 
-```cmd/sh
+```azurecli
 az iot pnp interface show --interface {InterfaceID}
 ```
 
-```cmd/sh
+```azurecli
 az iot pnp capability-model show --model {ModelID}
 ```
 
diff --git a/articles/iot-pnp/howto-install-pnp-cli.md b/articles/iot-pnp/howto-install-pnp-cli.md
diff --git a/articles/iot-pnp/tutorial-build-device-certification.md b/articles/iot-pnp/tutorial-build-device-certification.md
