Skip to content

Commit fa81812

Browse files
asergazdominicbetts
authored andcommitted
typo
1 parent d3f7db8 commit fa81812

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-operations/secure-iot-ops/howto-manage-certificates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ To set up Azure IoT Operations with your own issuer, use the following steps **b
149149

150150
## Manage certificates for external communications
151151

152-
The certificate management experience for external communications uses Azure Key vault as the managed vault solution on the cloud. Certificates are added to Azure Key Vault as secrets and synchronized to the edge as Kubernetes secrets via [Azure Key Vault Secret Store extension](/azure/azure-arc/kubernetes/secret-store-extension).
152+
The certificate management experience for external communications uses Azure Key vault as the managed vault solution on the cloud. Certificates are added to the key vault as secrets and synchronized to the edge as Kubernetes secrets via [Azure Key Vault Secret Store extension](/azure/azure-arc/kubernetes/secret-store-extension).
153153

154154
The OPC UA client application authentication, leverages the current certificate management experience for external communications. When you [deploy Azure IoT Operations with secure settings](../deploy-iot-ops/overview-deploy.md#secure-settings-deployment), you can start adding certificates to Azure Key Vault, and sync them to the edge to be used in the *Trust list* and *Issuer list* stores for OPC UA connections:
155155

0 commit comments

Comments
 (0)