Skip to content

Commit aab1d2d

Browse files
authored
Merge pull request #188106 from chrisjlin/main
fixing url, hopefully for the last time
2 parents efbb110 + c18fdd0 commit aab1d2d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-hub-device-update/migration-pp-to-ppr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: iot-hub-device-update
1010

1111
# Migrate devices and groups from Public Preview to Public Preview Refresh
1212

13-
As the Device Update for IoT Hub service releases new versions, you'll want to update your devices for the latest features and security improvements. This article provides information about how to migrate from the [Public Preview release](/previous-versions/azure/iot-hub-device-update) to the current, [Public Preview Refresh (PPR) release](understand-device-update.md). This article also explains the group and UX behavior across these releases. If you do not have devices, groups, and deployments that use the Public Preview release, you can ignore this page.
13+
As the Device Update for IoT Hub service releases new versions, you'll want to update your devices for the latest features and security improvements. This article provides information about how to migrate from the [Public Preview release](/previous-versions/azure/iot-hub-device-update/understand-device-update) to the current, [Public Preview Refresh (PPR) release](understand-device-update.md). This article also explains the group and UX behavior across these releases. If you do not have devices, groups, and deployments that use the Public Preview release, you can ignore this page.
1414

1515
To migrate successfully, you will have to upgrade the DU agent running on your devices. You will also have to create new device groups to deploy and manage updates. Note that as there are major changes with the PPR release, we recommend that you follow the instructions closely to avoid errors.
1616

0 commit comments

Comments
 (0)