Fix screenshots

Author: dominicbetts

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

@@ -3,7 +3,7 @@ title: Migrate devices from Azure IoT Central to Azure IoT Hub | Microsoft Docs
 description: Describes how to use the migration tool to migrate devices that currently connect to an Azure IoT Central application to an Azure IoT hub.
 author: dominicbetts
 ms.author: dobett
-ms.date: 07/26/2022
+ms.date: 09/12/2022
 ms.topic: how-to
 ms.service: iot-central
 ---
@@ -22,6 +22,9 @@ The tool requires your connected devices to implement a **DeviceMove** command t
 - Provision itself with DPS by using the new ID scope in the command payload.
 - Use the provisioning result to connect to the destination IoT hub and start sending telemetry again.
 
+> [!TIP]
+> You can also use the migrator tool to migrate devices between IoT Cental applications, or from an IoT hub to an IoT Central application.
+
 ## Prerequisites
 
 You need the following prerequisites to complete the device migration steps:
@@ -32,7 +35,7 @@ You need the following prerequisites to complete the device migration steps:
 
 ## Device requirements
 
-The devices that you want to migrate must implement the **DeviceMove** command. 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.
+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.
 
 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.
 
@@ -50,18 +53,54 @@ The migrator tool requires an Azure Active Directory application registration to
 
 1. Enter a name such as "IoTC Migrator app".
 
-1. Select **Accounts in this organizational directory only ({your directory} only - Single tenant)**.
+1. Select **Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)**.
 
 1. Select **Single page application (SPA)**.
 
-1. Enter `http://localhost:3000` as the redirect URI.
+1. Enter `http://localhost:3000` as the redirect URI. You add this value to the migrator app configuration later.
 
 1. Select **Register**.
 
 1. Make a note of the **Application (client) ID** and **Directory (tenant) ID** values. You use these values later to configure the migrator app:
 
     :::image type="content" source="media/howto-migrate-to-iot-hub/azure-active-directory-app.png" alt-text="Screenshot that shows the Azure Active Directory application in the Azure portal." lightbox="media/howto-migrate-to-iot-hub/azure-active-directory-app.png":::
 
+1. Navigate to the **Manifest** page in the registration and replace the contents of the `requiredResourceAccess` with the following configuration:
+
+    ```json
+    [
+      {
+        "resourceAppId": "9edfcdd9-0bc5-4bd4-b287-c3afc716aac7",
+        "resourceAccess": [
+          {
+            "id": "73792908-5709-46da-9a68-098589599db6",
+            "type": "Scope"
+          }
+        ]
+      },
+      {
+        "resourceAppId": "797f4846-ba00-4fd7-ba43-dac1f8f63013",
+        "resourceAccess": [
+          {
+            "id": "41094075-9dad-400e-a0bd-54e686782033",
+            "type": "Scope"
+          }
+        ]
+      },
+      {
+        "resourceAppId": "00000003-0000-0000-c000-000000000000",
+        "resourceAccess": [
+          {
+            "id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d",
+            "type": "Scope"
+          }
+        ]
+      }
+    ]
+    ```
+
+    1. Save the changes.
+
 ### Add the device keys to DPS
 
 Add the shared access signature keys or X.509 certificates from your IoT Central application to your DPS allocation group.
@@ -93,20 +132,17 @@ Download or clone a copy of the migrator tool to your local machine:
 git clone https://github.com/Azure/iotc-migrator.git
 ```
 
-Open the *config.ts* file in a text editor. Update the `AADClientID` and `AADDIrectoryID` with the values from the Azure Active Directory application registration you created previously. Update the `applicationHost` to match the URL of your IoT Central application. Then save the changes:
+In the root of the downloaded repository, create a *.env* file. Update the `REACT_APP_AAD_APP_CLIENT_ID`, `REACT_APP_AAD_APP_TENANT_ID`, and `REACT_APP_AAD_APP_REDIRECT_URI` values with the values from the Azure Active Directory application registration you created previously. Then save the changes:
 
-```typescript
-{
-    AADLoginServer: 'https://login.microsoftonline.com',
-    AADClientID: '<your-AAD-Application-(client)-ID>',
-    AADDirectoryID: '<your-AAD-Directory-(tenant)-ID>',
-    AADRedirectURI: 'http://localhost:3000',
-    applicationHost: '<your-iot-central-app>.azureiotcentral.com'
-}
+```txt
+PORT=3000
+REACT_APP_AAD_APP_CLIENT_ID=<your-AAD-Application-(client)-ID>
+REACT_APP_AAD_APP_TENANT_ID=<your-AAD-Directory-(tenant)-ID>
+REACT_APP_AAD_APP_REDIRECT_URI=http://localhost:3000
 ```
 
 > [!TIP]
-> Make sure the `AADRedirectURI` matches the redirect URI you used in your Azure Active Directory application registration.
+> Make sure the `REACT_APP_AAD_APP_REDIRECT_URI` matches the redirect URI you used in your Azure Active Directory application registration.
 
 In your command-line environment, navigate to the root of the `iotc-migrator` repository. Then run the following commands to install the required node.js packages and then run the tool:
 
@@ -115,7 +151,7 @@ npm install
 npm start
 ```
 
-After the migrator app starts, navigate to `http://localhost:3000` to view the tool.
+After the migrator app starts, navigate to `http://localhost:3000` to view the tool. Sign in when you're prompted.
 
 ## Migrate devices
 
@@ -126,19 +162,17 @@ Use the tool to migrate your devices in batches. Enter the migration details on
 1. Select a device template that includes the **DeviceMove** command definition.
 1. Select **Move to your own Azure IoT Hub**.
 1. Select the DPS instance linked to your target IoT hub.
-1. Select **Migrate**.
+1. Select **Migrate**. The tool prompts you to copy the keys from your IoT Central application to the DPS enrollment group. You previously completed this step in the [Add the device keys to DPS](#add-the-device-keys-to-dps) step.
 
 :::image type="content" source="media/howto-migrate-to-iot-hub/migrator-tool.png" alt-text="Screenshot of migration tool." lightbox="media/howto-migrate-to-iot-hub/migrator-tool.png":::
 
 The tool now registers all the connected devices that matched the target device filter in the destination IoT hub. The tool then creates a job in your IoT Central application to call the **DeviceMove** method on all those devices. The command payload contains the ID scope of the destination DPS instance.
 
 ## Verify migration
 
-The **Migration status** page in the tool shows you when the migration is complete:
-
-:::image type="content" source="media/howto-migrate-to-iot-hub/migration-complete.png" alt-text="Screenshot showing completed migration status in tool." lightbox="media/howto-migrate-to-iot-hub/migration-complete.png":::
+Use the **Migration status** page in the migrator tool to monitor the progress.
 
-Select a job on this page to view the [job status](howto-manage-devices-in-bulk.md#view-job-status) in your IoT Central application. Use this page to view the status of the individual devices in the job:
+Select a job on the **Migration status** page to view the [job status](howto-manage-devices-in-bulk.md#view-job-status) in your IoT Central application. Use this page to view the status of the individual devices in the job:
 
 :::image type="content" source="media/howto-migrate-to-iot-hub/job-status.png" alt-text="Screenshot showing completed migration status for IoT Central job." lightbox="media/howto-migrate-to-iot-hub/job-status.png":::