Skip to content

Commit 7401e3d

Browse files
committed
Incorp feedback
1 parent 7d7e0de commit 7401e3d

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

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

Lines changed: 5 additions & 3 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/05/2026
8+
ms.date: 02/11/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
@@ -140,10 +140,12 @@ For example, to create a new broker listener with the `NodePort` service type, s
140140
To create a new broker listener with the `NodePort` service type, use the following Azure CLI command.
141141

142142
```azurecli
143-
az iot ops broker listener port add
143+
az iot ops broker listener port add --service-type NodePort --nodeport <static port value>
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).
146+
Optionally, for testing purposes only, you can use the `--add-insecure-listener` flag to create a listener without authentication and TLS. The `--add-insecure-listener` flag is only available on the instance deployment operation via the `az iot ops create` command. To add a port without authentication and TLS after deployment, you can use the `listener port add` operation as in the previous example, but omit the options for authentication or TLS.
147+
148+
For more information, see [az iot ops broker listener port add](/cli/azure/iot/ops/broker/listener/port).
147149

148150
# [Bicep](#tab/bicep)
149151

0 commit comments

Comments
 (0)