Skip to content

Commit 7d7e0de

Browse files
committed
Fix
1 parent 2cdb9bd commit 7d7e0de

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/iot-operations/manage-mqtt-broker/howto-test-connection.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sethmanheim
55
ms.author: sethm
66
ms.subservice: azure-mqtt-broker
77
ms.topic: how-to
8-
ms.date: 02/03/2026
8+
ms.date: 02/05/2026
99

1010
#CustomerIntent: As an operator or developer, I want to test MQTT connectivity with tools that I'm already familiar with to know that I set up my MQTT broker correctly.
1111
ms.service: azure-iot-operations
@@ -143,7 +143,7 @@ To create a new broker listener with the `NodePort` service type, use the follow
143143
az iot ops broker listener port add
144144
```
145145

146-
Optionally, you can use the `--add-insecure-listener` flag to create a listener without authentication and TLS for testing purposes only. For more information, see [az iot ops broker listener port add](/cli/azure/iot/ops/broker/listener/port?view=azure-cli-latest).
146+
Optionally, you can use the `--add-insecure-listener` flag to create a listener without authentication and TLS for testing purposes only. For more information, see [az iot ops broker listener port add](/cli/azure/iot/ops/broker/listener/port).
147147

148148
# [Bicep](#tab/bicep)
149149

0 commit comments

Comments
 (0)