Prerequisites

Deploy and Configure Azure Migrate

Dr Migrate leverages the data collection capability of Azure Migrate. Ensure that you have:

1. Deployed an Azure Migrate Project.
2. Deployed an Azure Migrate Appliance.
3. Connected the Azure Migrate Project and Appliance.
4. Provided all necessary permissions to collect data.

Microsoft has robust and detailed guides on how to deploy and configure Azure Migrate here, or refer to the deployment checklists above.

Review Azure Migrate Project Connectivity Method

If Private Endpoint must be used then additional configuration steps are required, see here for more information.

Microsoft also has documentation for those seeking further information, see here.

Create Service Principal

Dr Migrate requires a Service Principal be created to allow the Dr Migrate server to communicate with Azure Migrate and Power BI.

When creating the SPN please 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 here

Configure SPN Access

Assign your Service Principal, the following permissions

Learn More about how to assign RBAC roles here

Create a Security Group for the Service Principal

Create a security group to house the Service Principal and Assign the Power BI permissions.

• Group Name - It is recommended to name the Security Group “drmigrate-powerbi”. All other settings can be left as default

• Group Membership - The Service Principal should be added as a member of the security group.

To learn more about how to assign access to Entra ID Security Groups, see here.

Audit Azure Policy

When Dr Migrate installs, it deploys Azure resources to a managed Resource Group, these resources may be subject to Azure policy. Dr Migrate allows certain policy enforcement during its installation, such as the inheritance of tags. However, it is possible Azure Policy may attempt to enforce an action on Dr Migrate resources during deployment that may be blocked. When this scenario occurs the application deployment will fail.

To mitigate this risk it’s recommended that some policies be temporarily exempted at the Subscription level, prior to and for the duration of the Dr Migrate installation.

Different Azure policies have different effects:

Azure Policy Effects

Temporarily exempt policies that are applied to the subscription that have the following effects.

• Append
• DeployIfNotExists
• Deny
• Modify

To learn how to exempt Azure Policy from resources, please see here

Configure settings in the Power BI tenant

Head to Power BI Admin Portal to configure access to the Power BI settings for the Security Group containing the Service Principal.

Configure the following settings:

Workspace settings -> Create workspaces (new workspace experience)

• Developer settings -> Embed content in apps

• Developer settings -> Service principals to use Fabric APIs

• Developer settings -> Allow service principals to create and use profiles

• Export and sharing settings -> Export to Excel

• Export and sharing settings -> Export to .csv

• Export and sharing settings -> Export reports as PowerPoint presentations or PDF documents

All these settings need to be enabled. You can either have this at the organizational level

or specify the Dr M Security Group.

Finally, check, Power BI visuals -> Add and use certified visuals only

This setting governs if certain required visuals are allowed to run within your Fabric Environment.

This setting should be Disabled, this ensures that all required visuals can be used.

If this setting is Enabled in your environment please see enabling Power BI visuals.

Gateway Administration

Dr Migrate uses an On-Premises data gateway as part of the solution.

Within the Power BI Admin Center, navigate to “On-Premises data gateways” in the central panel

Enable the Tenant Administration Settings, using the switch on the right hand side.

Enabling this, will show the “Manage Gateway Installers” option.

Ensure that the “Restrict users in your organization from installing gateways” setting is set to Off.

If the restriction is set to “On” it is recommended:

• Turn this setting to “Off” while the Dr. Migrate product is installing
• Turn the setting back “On” 60 minutes post installation.

Deploy Azure Migrate

Dr Migrate leverages the data collection capability of Azure Migrate. Ensure that you have:

1. Deployed an Azure Migrate Project.
2. Deployed an Azure Migrate Appliance.
3. Connected the Azure Migrate Project and Appliance.
4. Provided all necessary permissions to collect data.

Microsoft has robust and detailed guides on how to deploy and configure Azure Migrate here.

Review Azure Migrate Project Connectivity Method

Create Service Principal

Dr Migrate requires a Service Principal be created to allow the Dr Migrate server to communicate with Azure Migrate.

When creating the SPN please 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 here

Configure Access

Assign your Service Principal, the following permissions:

Learn More about how to assign RBAC roles here