Skip to content

Commit 7872fb1

Browse files
asergazdominicbetts
authored andcommitted
adding more detail to bring your own issuer
1 parent ba4fb6f commit 7872fb1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Azure IoT Operations uses TLS to encrypt communication between all components. T
2222

2323
## Manage certificates for internal communications
2424

25-
All communication within Azure IoT Operations is encrypted using TLS. To help you get started, Azure IoT Operations is deployed with a default root CA and issuer for TLS server certificates. You can use the default setup for development and testing purposes. For a production deployment, we recommend using your own CA issuer and an enterprise PKI solution.
25+
All communication within Azure IoT Operations is encrypted using TLS. To help you get started, Azure IoT Operations is deployed with a default root CA and issuer for TLS server certificates. You can use the default setup for development and testing purposes. For a production deployment, we recommend [using your own CA issuer](#bring-your-own-issuer) and an enterprise PKI solution.
2626

2727
### Default self-signed issuer and root CA certificate for TLS server certificates
2828

@@ -134,9 +134,9 @@ You can delete synced certificates as well. When you delete a synced certificate
134134
135135
## Bring your own issuer
136136
137-
For production deployments, we recommend that you set up Azure IoT Operations with an enterprise PKI to manage certificates and that you bring your own issuer which works with your enterprise PKI instead of using the default self-signed issuer to issue TLS certificates for internal communication.
137+
For production deployments, we recommend that you set up Azure IoT Operations with an enterprise PKI to manage certificates and that you bring your own CA issuer which works with your enterprise PKI instead of using the default self-signed issuer to issue TLS certificates. You can use your own issuer for both internal communications, as explained in the below section, and external communications like explained in the [OPC UA server application instance certificates signed by a certificate authority](../discover-manage-assets/overview-opcua-broker-certificates-management.md#use-opc-ua-server-application-instance-certificates-signed-by-a-certificate-authority) scenario.
138138
139-
To set up Azure IoT Operations with your own issuer, use the following steps **before deploying an instance to your cluster**:
139+
To set up Azure IoT Operations with your own issuer for internal communication, use the following steps **before deploying an instance to your cluster**:
140140
141141
1. Follow the steps in [Prepare your cluster](../deploy-iot-ops/howto-prepare-cluster.md) to set up your cluster.
142142

0 commit comments

Comments
 (0)