Skip to content

Commit 2b1cb6c

Browse files
Learn Editor: Update device-update-rootkey.md
1 parent d12db50 commit 2b1cb6c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub-device-update/device-update-rootkey.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Before learning about the Device Update root key rotation process, learn about r
2121

2222
The Device Update for IoT Hub team was previously planning to rotate ADU.200702.R, the root key currently being used for validating signing keys associated with update manifests, on August 26, 2025. The rotation of that key would have meant that the Device Update service would stop signing imported content with a key that chains up to ADU.200702.R, and begin signing using a key that chains up to ADU.200703.R.
2323

24-
Based on feedback from many of our customers on the impact of the root key rotation, the Device Update for IoT Hub team reviewed the necessity of rotating the ADU.200702.R root key in the originally-planned August 2025 timeframe. After an internal review, the assessment is that it’s safe to postpone the August 2025 root key rotation to give customers more time to be ready for the rotation. Once a new date is available for this rotation event, it will be announced at least one year before the rotation will occur.
24+
Based on feedback from many of our customers on the impact of the root key rotation, the Device Update for IoT Hub team determined that it’s safe to postpone the August 2025 rotation to give customers more time to be ready for the rotation. Once a new date is available for this rotation event, it will be announced at least one year before the rotation will occur.
2525

2626
## How to validate if your devices are ready for a future rotation or revocation
2727

0 commit comments

Comments
 (0)