Connecting Azure Migrate for Migration
This guide explains how to connect an existing DMC instance of Dr Migrate to Azure Migrate to enable migration functionality. This connection enables real-time data synchronization between Azure Migrate and Dr Migrate, enriching your migration activities with continuous insights.
Prerequisites
Before connecting Azure Migrate to your Dr Migrate instance, ensure you have:
| Requirement | Learn More | |
|---|---|---|
| ✅ | An existing DMC Dr Migrate instance. | Learn More |
| ✅ | A user with needed Entra & Azure permissions. | Learn More |
| ✅ | An Azure Migrate Project deployed and configured. | Learn More |
| ✅ | A Service Principal with a client secret created. | Learn More |
| ✅ | Necessary roles assigned to the Service Principal. | Learn More |
Existing DMC Instance
This guide assumes you have an existing Dr Migrate instance that was activated using DMC (Dr Migrate Collector) data collection. Your instance should already be operational and have completed initial data ingestion from DMC scans.
Permissions Required
Ideally, the user performing the following steps should have the Global Administrator role.
If this is not possible, the least privileged approach requires the following permissions:
- Application Admin
- Subscription Owner
More information about least privileged role assignment can be found on the Microsoft Learn Portal.
Azure Migrate Project
Ensure that you have an Azure Migrate Project deployed and configured. The Azure Migrate project should be actively collecting data from your infrastructure.
For detailed information on deploying and configuring Azure Migrate, see the Microsoft Learn documentation.
Create Service Principal
Dr Migrate requires a Service Principal to communicate with Azure Migrate. This enables secure authentication and data synchronization.
When creating the Service Principal, observe the following:
- SPN Name - It is recommended to name the App Registration “drmigrate-spn”. All other settings can be left as default.
- Client Secret Creation - Dr Migrate requires a client secret to be created. It is recommended to set the expiry to 12 months.
For Microsoft documentation on creating a Service Principal in Entra ID, see the Microsoft Learn portal.
Configure Access
Assign your Service Principal the following permissions:
| Role | Scope | Requirement |
|---|---|---|
| Contributor | Subscription or Resource Group where the Azure Migrate project is located (may be in a different tenant than Dr Migrate) | Mandatory |
Learn more about how to assign RBAC roles on the Microsoft Learn portal.
Connect to Azure Migrate
Navigate to the Migrate section in your Dr Migrate instance and select Azure Migrate.
Enter Connection Details
Fill in the following details to connect your Azure Migrate project:
| Item | Where to Find |
|---|---|
| Azure AD Tenant ID | Search “Tenant Properties” in the Azure portal |
| Azure Subscription ID | Go to the Azure Migrate Resource Group > Properties |
| Azure Migrate Resource Group Name | Go to the Azure Migrate Resource Group > Properties |
| Service Principal - Application (Client) ID | Azure Portal > App Registrations > Select your SPN > Overview |
| Service Principal - Client Secret Value | Retrieve from your secure store (set during the Service Principal creation step) |
If any value is missing or invalid (e.g., malformed secret), an alert will guide you to resolve the issue.
Sync Data
Once the connection information is entered, click Sync data to establish the connection and start the synchronization process.
What This Enables
Once connected, Azure Migrate data sync enables:
- Real-time data collection that enriches migration activities with up-to-date performance and infrastructure metadata
- Continuous insights during migration execution, providing near real-time updates to your assessment and migration planning
- Enhanced migration planning with current data from Azure Migrate combined with your existing DMC-collected data
Next Steps
After successfully connecting Azure Migrate: