You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-hub/migrate-tls-certificate.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,9 +164,9 @@ You can migrate your application from the Baltimore CyberTrust Root to the DigiC
164
164
2.**In addition** to the Baltimore Root, ensure the DigiCert Global G2 Root is added to your trusted root store.
165
165
3. Make sure you aren’t pinning any intermediate or leaf certificates and are using the public roots to perform TLS server validation.
166
166
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.
170
170
171
171
### How long will it take my devices to reconnect?
0 commit comments