Create a migration target

Follow these steps to create a target reference for migrating data to with LiveData Migrator. Before you start, ensure that you have the following prerequisites:

• An Azure resource group.
• ADLS Gen2 Storage account and container.
• Network connectivity from your LiveData Migrator host.

Create a target using access key authentication

Create a target with the Azure Portal

1. In the Azure Portal, navigate to the LiveData Migrator resource page.
2. From the LiveData Migrator menu on the left, select Targets.
3. Select Create.
4. Complete the details under the Basics section:
   • Target Name: the name of the target as you want it to appear in your list of resources.
   • Storage Account: your ADLS Gen2 Storage account name.
   • Storage Container: your ADLS Gen2 Storage container name.
5. Optionally, select the Use custom storage endpoint option.
   1. In the Custom Storage Endpoint field, add your storage endpoint.
6. In the Authentication Type dropdown, keep Access key selected as the default.
7. Select Review and create.
8. Select Create.

Create a target with the CLI

Run the following command to set your ADLS Gen2 storage as the target:

Using an Access Key

az livedata migrator target create -g <resource_group> --migrator-name <migrator_name> --migrator-target-name <target_name> --storage-account <storage_account_name> --storage-container <container_name> --storage-access-key <storage_key>

See the Azure CLI LiveData Extension - Migrator Target page for help with these parameters.

Create a target using OAuth 2 / managed identity authentication

Create a target with the Azure Portal

1. In the Azure Portal, navigate to the LiveData Migrator resource page.

2. From the LiveData Migrator menu on the left, select Targets.

3. Select Create.

4. Complete the details under the Basics section:

   • Target Name: the name of the target as you want it to appear in your list of resources.
   • Storage Account: your ADLS Gen2 Storage account name.
   • Storage Container: your ADLS Gen2 Storage container name.

5. Optionally, select the Use custom storage endpoint option.

   1. In the Custom Storage Endpoint field, add your storage endpoint.

6. In the Authentication Type dropdown, select Service Principal (OAuth2).

7. In the Service Principal Type section, select a new or existing service principal as appropriate. You must hold permission to register a new application in your Azure subscription to create a new service principal.

   Create a new service principal

   1. Keep the Create new radio button selected and select Change selection under (New) default App Id. The Register an application pane opens.
   2. Select an application name and account type, and select Register.
   3. In the application overview page that opens, add a client secret, and then copy the displayed secret value (you'll need it later to authenticate).
   4. When you're done, select the Close button in the upper corner to return to the Create target page.

   Use an existing service principal

   1. Select the Select existing radio button and select Make selection to open the Select an application pane.
   2. Select the application then Select.

8. In the Create Target page, add the service principal Client Secret.

   • If you created a new service principal, the Client ID field shows the new service principal. Paste the secret you copied earlier into the Client Secret field.
   • If you're using an existing service principal, fill in the field.

9. Optionally, select the Use custom endpoint (advanced) option.

   1. In the Client Endpoint field, add the path to the service principal OAuth2 token endpoint.

10. Select Review and create.

note

The service principal must have at least Storage Blob Data Owner role permissions on the storage account.

Create a target with the CLI

Run the following command to set your ADLS Gen2 storage as the target:

Using a Managed Identity

az livedata migrator target create -g <resource_group> --migrator-name <migrator_name> --migrator-target-name <target_name> --storage-account <storage_account_name> --storage-container <container_name> --oauth-endpoint <service_principal_endpoint> --oauth-id <service_principal_id> --oauth-secret <service_principal_secret>

See the Azure CLI LiveData Extension - Migrator Target section for help with these parameters.

note

To change a target, create a new one using the instructions above and remove the old target.

Update authentication settings

LiveData Migrator for Azure lets you update the authentication settings for your migration and metadata targets. See Update authentication settings for information.

Next steps

Once you've successfully installed LiveData Migrator and set up your target, create path mappings.

Troubleshooting

If you are having problems adding a target, you can find solutions in the troubleshooting guide.