Skip to content

Commit e26b190

Browse files
Mzamankhankgremban
andauthored
Update articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md
Co-authored-by: Kelly Gremban <[email protected]>
1 parent 04d456a commit e26b190

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-operations/deploy-iot-ops/howto-enable-secure-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Secrets Management for Azure IoT Operations uses Secret Store extension to sync
102102

103103
Secret Store extension requires a user-assigned managed identity with access to the Azure Key Vault where secrets are stored. To learn more, see [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview).
104104

105-
1. Create an [Azure Key Vault](https://learn.microsoft.com/en-us/azure/key-vault/secrets/quick-create-cli) which will be used to store secrets.
105+
1. Create an [Azure Key Vault](/azure/key-vault/secrets/quick-create-cli) which will be used to store secrets.
106106
2. Make sure you have `Key Vaults Secrets Officer` role on the Azure Key Vault.
107107
3. Create a [User Assigned Managed Identity](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview) for secret store extension.
108108
5. Use the [az iot ops secretsync enable](/cli/azure/iot/ops) command to set up the Azure IoT Operations instance for secret synchronization.

0 commit comments

Comments
 (0)