Skip to content

Commit 2c6de2e

Browse files
Update howto-manage-secrets.md
appears the parameter set for az iot ops init has changed with the name field being removed and the cluster name being required.
1 parent 5384649 commit 2c6de2e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ When following the guide [Deploy Azure IoT Operations extensions](./howto-deploy
125125
The following example shows how to prepare the cluster for Azure IoT Operations without fully deploying it by using `--no-deploy` flag. You can also run the command without this argument for a default Azure IoT Operations deployment.
126126

127127
```bash
128-
az iot ops init --name "<your unique key vault name>" --resource-group "<the name of the resource group>" \
128+
az iot ops init --cluster "<your cluster name>" --resource-group "<the name of the resource group>" \
129129
--kv-id <Key Vault Resource ID> \
130130
--sp-app-id <Application registration App ID (client ID) from Microsoft Entra ID> \
131131
--sp-object-id <Object ID copied from Enterprise Application in Microsoft Entra ID> \

0 commit comments

Comments
 (0)