Skip to content

Commit 44f851c

Browse files
committed
Updated note location per call with Ramit
1 parent 88b1caf commit 44f851c

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
@@ -19,9 +19,6 @@ You should start planning now for the effects of migrating your IoT hubs to the
1919
* Any device that doesn't have the DigiCert Global Root G2 in its certificate store won't be able to connect to Azure.
2020
* The IP address of the IoT hub will change.
2121

22-
> [!NOTE]
23-
> We are collecting this information to help with the Baltimore migration. We will hold onto this information until October 15th, 2023, when this migration is slated to complete. If you would like us to delete this information, please [email us](mailto:[email protected]) and we can assist you. For any additional questions about the Microsoft privacy policy, see the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839).
24-
2522
## Timeline
2623

2724
The IoT Hub team will begin migrating IoT hubs by region on **February 15, 2023** and completing by October 15, 2023. After all IoT hubs have migrated, then DPS will perform its migration between January 15 and February 15, 2024.
@@ -30,6 +27,9 @@ The IoT Hub team will begin migrating IoT hubs by region on **February 15, 2023*
3027

3128
This TLS certificate migration is critical for the security of our customers and Microsoft's infrastructure, and is time-bound by the expiration of the Baltimore CyberTrust Root certificate. Therefore, there's little extra time that we can provide for customers that don't think their devices will be ready by February 15, 2023. If you absolutely can't meet the February 2023 target date, [fill out this form](https://aka.ms/BaltimoreAllow) with the details of your extension request, and then [email us](mailto:[email protected]?subject=Requesting%20extension%20for%20Baltimore%20migration) with a message that indicates you've completed the form, along with your company name. We can flag the specific hubs to be migrated later in the rollout window.
3229

30+
> [!NOTE]
31+
> We are collecting this information to help with the Baltimore migration. We will hold onto this information until October 15th, 2023, when this migration is slated to complete. If you would like us to delete this information, please [email us](mailto:[email protected]) and we can assist you. For any additional questions about the Microsoft privacy policy, see the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839).
32+
3333
## Required steps
3434

3535
To prepare for the migration, take the following steps before February 2023:

0 commit comments

Comments
 (0)