Merge pull request #274933 from kgremban/may9-clideprecated

Remove deprecated cli commands

Author: prmerger-automator[bot]

articles/iot-dps/quick-setup-auto-provision-cli.md

@@ -64,12 +64,12 @@ az iot dps create --name my-sample-dps --resource-group my-sample-resource-group
 
 ## Get the connection string for the IoT hub
 
-You need your IoT hub's connection string to link it with the Device Provisioning Service. Use the [az iot hub show-connection-string](/cli/azure/iot/hub#az-iot-hub-show-connection-string) command to get the connection string and use its output to set a variable that's used later, when you link the two resources. 
+You need your IoT hub's connection string to link it with the Device Provisioning Service. Use the [az iot hub connection-string show](/cli/azure/iot/hub/connection-string#az-iot-hub-connection-string-show) command to get the connection string and use its output to set a variable that's used later, when you link the two resources.
 
 The following example sets the *hubConnectionString* variable to the value of the connection string for the primary key of the hub's *iothubowner* policy (the `--policy-name` parameter can be used to specify a different policy). Trade out *my-sample-hub* for the unique IoT hub name you chose earlier. The command uses the Azure CLI [query](/cli/azure/query-azure-cli) and [output](/cli/azure/format-output-azure-cli#tsv-output-format) options to extract the connection string from the command output.
 
 ```azurecli-interactive
-hubConnectionString=$(az iot hub show-connection-string --name my-sample-hub --key primary --query connectionString -o tsv)
+hubConnectionString=$(az iot hub connection-string show --name my-sample-hub --key primary --query connectionString -o tsv)
 ```
 
 You can use the `echo` command to see the connection string.
@@ -80,7 +80,7 @@ echo $hubConnectionString
 
 > [!NOTE]
 > These two commands are valid for a host running under Bash.
-> 
+>
 > If you're using a local Windows/CMD shell or a PowerShell host, modify the commands to use the correct syntax for that environment.
 >
 > If you're using Azure Cloud Shell, check that the environment drop-down on the left side of the shell window says **Bash**.

articles/iot-dps/tutorial-custom-allocation-policies.md

@@ -370,7 +370,7 @@ For the example in this tutorial, use the following two device registration IDs
 * **breakroom499-contoso-tstrsd-007**
 * **mainbuilding167-contoso-hpsd-088**
 
-The IoT extension for the Azure CLI provides the [`iot dps enrollment-group compute-device-key`](/cli/azure/iot/dps/enrollment-group#az-iot-dps-enrollment-group-compute-device-key) command for generating derived device keys. This command can be used on Windows-based or Linux systems, from PowerShell or a Bash shell.
+The IoT extension for the Azure CLI provides the [iot dps enrollment-group compute-device-key](/cli/azure/iot/dps/enrollment-group#az-iot-dps-enrollment-group-compute-device-key) command for generating derived device keys. This command can be used on Windows-based or Linux systems, from PowerShell or a Bash shell.
 
 Replace the value of `--key` argument with the **Primary Key** from your enrollment group.
 
@@ -379,7 +379,7 @@ az iot dps enrollment-group compute-device-key --key <ENROLLMENT_GROUP_KEY> --re
 ```
 
 ```azurecli
-az iot dps compute-device-key --key <ENROLLMENT_GROUP_KEY> --registration-id mainbuilding167-contoso-hpsd-088
+az iot dps enrollment-group compute-device-key --key <ENROLLMENT_GROUP_KEY> --registration-id mainbuilding167-contoso-hpsd-088
 ```
 
 > [!NOTE]

articles/iot-hub/tutorial-message-enrichments.md

@@ -145,29 +145,26 @@ Create a second endpoint and route for the enriched messages.
    routeName=ContosoStorageRouteEnriched
    ```
 
-1. Use the [az iot hub routing-endpoint create](/cli/azure/iot/hub/routing-endpoint#az-iot-hub-routing-endpoint-create) command to create a custom endpoint that points to the storage container you made in the previous section.
+1. Use the [az iot hub message-endpoint create](/cli/azure/iot/hub/message-endpoint#az-iot-hub-message-endpoint-create-storage-container) command to create a custom endpoint that points to the storage container you made in the previous section.
 
    ```azurecli-interactive
-   az iot hub routing-endpoint create \
+   az iot hub message-endpoint create \
      --connection-string $(az storage account show-connection-string --name $storageName --query connectionString -o tsv) \
      --endpoint-name $endpointName \
-     --endpoint-resource-group $resourceGroup \
-     --endpoint-subscription-id $(az account show --query id -o tsv) \
-     --endpoint-type azurestoragecontainer
      --hub-name $hubName \
      --container $containerName \
      --resource-group $resourceGroup \
      --encoding json
    ```
 
-1. Use the [az iot hub route create](/cli/azure/iot/hub/route#az-iot-hub-route-create) command to create a route that passes any message where `level=storage` to the storage container endpoint.
+1. Use the [az iot hub message-route create](/cli/azure/iot/hub/message-route#az-iot-hub-message-route-create) command to create a route that passes any message where `level=storage` to the storage container endpoint.
 
    ```azurecli-interactive
-   az iot hub route create \
-     --name $routeName \
+   az iot hub message-route create \
+     --route-name $routeName \
      --hub-name $hubName \
      --resource-group $resourceGroup \
-     --source devicemessages \
+     --source-type devicemessages \
      --endpoint-name $endpointName \
      --enabled true \
      --condition 'level="storage"'

articles/iot-hub/tutorial-routing.md

@@ -302,29 +302,26 @@ Now set up the routing for the storage account. In this section you define a new
    routeName=ROUTE_NAME
    ```
 
-1. Use the [az iot hub routing-endpoint create](/cli/azure/iot/hub/routing-endpoint#az-iot-hub-routing-endpoint-create) command to create a custom endpoint that points to the storage container you made in the previous section.
+1. Use the [az iot hub message-endpoint create](/cli/azure/iot/hub/message-endpoint/create#az-iot-hub-message-endpoint-create-storage-container) command to create a custom endpoint that points to the storage container you made in the previous section.
 
    ```azurecli-interactive
-   az iot hub routing-endpoint create \
+   az iot hub message-endpoint create storage-container \
      --connection-string $(az storage account show-connection-string --name $storageName --query connectionString -o tsv) \
      --endpoint-name $endpointName \
-     --endpoint-resource-group $resourceGroup \
-     --endpoint-subscription-id $(az account show --query id -o tsv) \
-     --endpoint-type azurestoragecontainer
      --hub-name $hubName \
      --container $containerName \
      --resource-group $resourceGroup \
      --encoding json
    ```
 
-1. Use the [az iot hub route create](/cli/azure/iot/hub/route#az-iot-hub-route-create) command to create a route that passes any message where `level=storage` to the storage container endpoint.
+1. Use the [az iot hub message-route create](/cli/azure/iot/hub/message-route#az-iot-hub-message-route-create) command to create a route that passes any message where `level=storage` to the storage container endpoint.
 
    ```azurecli-interactive
-   az iot hub route create \
-     --name $routeName \
+   az iot hub message-route create \
+     --route-name $routeName \
      --hub-name $hubName \
      --resource-group $resourceGroup \
-     --source devicemessages \
+     --source-type devicemessages \
      --endpoint-name $endpointName \
      --enabled true \
      --condition 'level="storage"'