Skip to content

Commit 4612371

Browse files
committed
Merge branch 'broken-link-fix-kgremban' of https://github.com/PhilKang0704/azure-docs-pr into broken-link-fix-kgremban
2 parents 5db50a1 + b08df56 commit 4612371

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
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
>
@@ -273,7 +273,7 @@ az iot hub message-endpoint delete --hub-name {iothub_name} --endpoint-type stor
273273
In IoT Hub, you can create a route to send messages or capture events. Each route has a data source and an endpoint. The data source is where messages or event logs originate. The endpoint is where the messages or event logs end up. You choose locations for the data source and endpoint when you create a new route in your IoT hub. Optionally, you can [Add queries to message routes](iot-hub-devguide-routing-query-syntax.md) to filter messages or events before they go to the endpoint.
274274

275275
> [!NOTE]
276-
> This article uses the [az iot hub message-route](/cli/azure/iot/hub/message-route) 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 route](/azure/iot-hub/how-to-routing-azure-cli?tabs=eventhubs) command group, which is similar and still supported.
276+
> This article uses the [az iot hub message-route](/cli/azure/iot/hub/message-route) 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 route` command group, which is no longer supported.
277277
>
278278
> Use the following command to update to the latest version of the azure-iot extension:
279279
>

0 commit comments

Comments
 (0)