Skip to content

Commit 01e37f3

Browse files
authored
Merge pull request #221132 from dominicbetts/central-migration-screenshots
IoT Central: update migration details
2 parents 249a097 + df9b81f commit 01e37f3

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

articles/iot-central/core/howto-migrate-to-iot-hub.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,10 @@ You need the following prerequisites to complete the device migration steps:
3737

3838
The devices that you want to migrate must implement the **DeviceMove** command in a component called **migration**. The command payload contains the *ID scope* of the destination DPS instance. The migrator tool repository includes an example [DTDL component model](https://raw.githubusercontent.com/Azure/iotc-migrator/main/assets/deviceMigrationComponent.json) that that defines the **DeviceMove** command. You can add this component to your existing device templates.
3939

40+
The tool assumes that the component name is `migration` and that the interface ID is `dtmi:azureiot:DeviceMigration;1`:
41+
42+
:::image type="content" source="media/howto-migrate-to-iot-hub/component-name.png" alt-text="Screenshot that highlights the component name and interface ID.":::
43+
4044
The tool repository also includes [sample code](https://github.com/Azure/iotc-migrator/tree/main/device_samples) that shows you how a device should implement the **DeviceMove** command.
4145

4246
## Tool setup
@@ -99,7 +103,7 @@ The migrator tool requires an Azure Active Directory application registration to
99103
]
100104
```
101105

102-
1. Save the changes.
106+
1. Save the changes.
103107

104108
### Add the device keys to DPS
105109

83.4 KB
Loading

0 commit comments

Comments
 (0)