Skip to content

Commit a0126a6

Browse files
authored
Update migrate-tls-certificate.md
1 parent 76c72b9 commit a0126a6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-hub/migrate-tls-certificate.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,9 +164,9 @@ You can migrate your application from the Baltimore CyberTrust Root to the DigiC
164164
2. **In addition** to the Baltimore Root, ensure the DigiCert Global G2 Root is added to your trusted root store.
165165
3. Make sure you aren’t pinning any intermediate or leaf certificates and are using the public roots to perform TLS server validation.
166166
4. In your IoT Central application you can find the Root Certification settings under **Settings** > **Application** > **Baltimore Cybertrust Migration**. 
167-
1. Select **DigiCert Global G2 Root** to migrate to the new certificate root.
168-
2. Click **Save** to initiate the migration.
169-
3. If needed, you can migrate back to the Baltimore root by selecting **Baltimore CyberTrust Root** and saving the changes. This option is available until 15 May 2023 and will then be disabled as Microsoft will start initiating the migration.
167+
1. Select **DigiCert Global G2 Root** to migrate to the new certificate root.
168+
2. Click **Save** to initiate the migration.
169+
3. If needed, you can migrate back to the Baltimore root by selecting **Baltimore CyberTrust Root** and saving the changes. This option is available until 15 May 2023 and will then be disabled as Microsoft will start initiating the migration.
170170

171171
### How long will it take my devices to reconnect?
172172

0 commit comments

Comments
 (0)