Skip to content

Commit fbfd3e2

Browse files
konichi3kgremban
andauthored
Update articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md
Co-authored-by: Kelly Gremban <[email protected]>
1 parent d1abf80 commit fbfd3e2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,7 @@ To view your cluster on the Azure portal, use the following steps:
142142
There's also an extension called **akvsecretsprovider**. This extension is the secrets provider that you configured and installed on your cluster with the `az iot ops init` command. You might delete and reinstall the Azure IoT Operations components during testing, but keep the secrets provider extension on your cluster.
143143

144144
> [!TIP]
145-
> You can run `az iot ops check` to assess health and configurations of deployed AIO workloads. By default, MQ including cloud connectors are assessed and you can [specifiy the service](https://learn.microsoft.com/en-us/cli/azure/iot/ops?view=azure-cli-latest#az-iot-ops-check-examples) with `--ops-service --svc`.
145+
> You can run `az iot ops check` to assess health and configurations of deployed AIO workloads. By default, MQ including cloud connectors are assessed and you can [specifiy the service](/cli/azure/iot/ops#az-iot-ops-check-examples) with `--ops-service --svc`.
146146
147147
## Update a deployment
148148

0 commit comments

Comments
 (0)