Skip to content

Commit 3b1bf70

Browse files
authored
Merge pull request #203730 from w-azure/winona-remove-workload
Removed 'workload', added 1.2 changes
2 parents d7e80c4 + d77e7c3 commit 3b1bf70

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/iot-edge/how-to-manage-device-certificates.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -218,8 +218,7 @@ IoT Edge automatically generates certificates on the device in several cases, in
218218

219219
<!-- 1.2 -->
220220
:::moniker range=">=iotedge-2020-11"
221-
* If you don't provide your own production certificates when you install and provision IoT Edge, the IoT Edge security manager automatically generates a **edge CA certificate**. This self-signed certificate is only meant for development and testing scenarios, not production. This certificate expires after 90 days.
222-
* The IoT Edge security manager also generates a **workload CA certificate** signed by the edge CA certificate
221+
If you don't provide your own production certificates when you install and provision IoT Edge, the IoT Edge security manager automatically generates an **edge CA certificate**. This self-signed certificate is only meant for development and testing scenarios, not production. This certificate expires after 90 days.
223222
:::moniker-end
224223
<!-- end 1.2 -->
225224

articles/iot-edge/iot-edge-certs.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ This article explains how IoT Edge certificates can work in production, developm
3232
* The **workload CA certificate** was deprecated. Now the IoT Edge security manager generates the IoT Edge hub server certificate directly from the edge CA certificate, without the intermediate workload CA certificate between them.
3333

3434
:::moniker-end
35+
<!-- end-1.2 -->
3536

3637
## IoT Edge certificates
3738

0 commit comments

Comments
 (0)