Skip to content

Commit 3a3eb85

Browse files
committed
Kevin's feedback
1 parent 29b96f3 commit 3a3eb85

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
@@ -7,7 +7,7 @@ manager: lizross
77
ms.service: iot-hub
88
services: iot-hub
99
ms.topic: conceptual
10-
ms.date: 12/08/2022
10+
ms.date: 12/09/2022
1111
---
1212

1313
# Migrate IoT Hub resources to a new TLS certificate root
@@ -126,7 +126,7 @@ No, only the [global Azure cloud](https://azure.microsoft.com/global-infrastruct
126126

127127
### I use IoT Central. Do I need to update my devices?
128128

129-
Yes, IoT Central uses IoT Hub in the backend. The TLS migration will affect your solution, and you need to update your devices to maintain connection.
129+
Yes, IoT Central uses both IoT Hub and DPS in the backend. The TLS migration will affect your solution, and you need to update your devices to maintain connection.
130130

131131
### How long will it take my devices to reconnect?
132132

@@ -175,7 +175,7 @@ If your device disconnects but doesn't reconnect after the migration, try the fo
175175

176176
* Check that your DNS resolution and handshake request completed without any errors.
177177

178-
* Verify that the device has the DigiCert Global Root G2 certificate installed in the certificate store.
178+
* Verify that the device has both the DigiCert Global Root G2 certificate and the Baltimore certificate installed in the certificate store.
179179

180180
* Use the following Kusto query to identify connection activity for your devices. For more information, see [Kusto Query Language (KQL) overview](/azure/data-explorer/kusto/query/).
181181

0 commit comments

Comments
 (0)