Skip to content

Commit 493de38

Browse files
Update articles/iot-hub/how-to-routing-azure-cli.md
Co-authored-by: Kelly Gremban <[email protected]>
1 parent 5fc231a commit 493de38

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub/how-to-routing-azure-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ Create a Cosmos DB account for SQL API and a Cosmos DB container. For more infor
8989
All IoT Hub routes point to an endpoint, which will receive the routed device and event data. More than one route can point to the same endpoint. Currently, IoT Hub supports endpoints for Event hubs, Service Bus queues or topics, Storage, and Cosmos DB. An instance of the service that you use for your endpoint must exist in your Azure subscription before you create the endpoint.
9090

9191
> [!NOTE]
92-
> This article uses the [az iot hub message-endpoint](/cli/azure/iot/hub/message-endpoint) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the [az iot hub routing-endpoint](/azure/iot-hub/how-to-routing-azure-cli) command group, which is similar and still supported but does not support creating Cosmos DB endpoints.
92+
> This article uses the [az iot hub message-endpoint](/cli/azure/iot/hub/message-endpoint) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the `az iot hub routing-endpoint` command group, which is no longer supported.
9393
>
9494
> Use the following command to update to the latest version of the azure-iot extension:
9595
>

0 commit comments

Comments
 (0)