Azure Migrate

Verify the Target Subscription is not of type CSP

The target subscription is where the Dr Migrate solution will be deployed. This is usually the same subscription and resource group as Azure Migrate.

You can check if you’re subscription is managed by a CSP using the Azure Resource Graph Explorer. Run the following command:

resourcecontainers
| where type== "microsoft.resources/subscriptions" 
| project subscriptionId, name, properties.subscriptionPolicies.quotaId 

If the target subscription returns a quotaId of “CSP_2015-05-01” or contains the phrase , you will need to request that the Dr Migrate team (support@altra.cloud) make an alternative version of Dr Migrate available.

Deploy and Configure Azure Migrate

Azure Migrate is a mandatory prerequisite for Dr Migrate. Successful assessments have Azure Migrate installed, configured and collecting data prior to Dr Migrate deployment.

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.

Create Azure Migrate Project and Connect Appliances

Prerequisites for Azure Migrate Project:

• An active Azure subscription
• Appropriate permissions to create resources in your Azure subscription
• A resource group where the Azure Migrate project will be deployed

Create New Azure Migrate Project (If Required)

If you don’t already have an Azure Migrate project, follow these steps to create one:

resourcecontainers
| where type== "microsoft.resources/subscriptions" 
| project subscriptionId, name, properties.subscriptionPolicies.quotaId 

Verify Existing Azure Migrate Project (If Already Deployed)

If you already have Azure Migrate deployed, verify the following:

Verify Project Location

• Navigate to your existing Azure Migrate project in the Azure Portal
• Note the Subscription and Resource Group where it’s deployed
• Ensure Dr Migrate will be deployed in the same subscription/resource group

Verify Endpoint Settings

• Navigate to your Azure Migrate project
• Go to Properties in the left-hand menu
• Verify Connectivity method is set to Public endpoint
• If set to Private Endpoint, consider changing to Public Endpoint, for simplicity. If this is not possible see Private Endpoints ↗ for additional configuration

Connect Azure Migrate Appliances

After creating or verifying your Azure Migrate project, you must deploy and connect at least one Azure Migrate appliance to collect data from your infrastructure:

1. Deploy the appropriate appliance for your environment:

   • VMware: Deploy the VMware appliance
   • Hyper-V: Deploy the Hyper-V appliance
   • Physical servers: Deploy the physical server appliance

2. Configure the appliance with your Azure Migrate project details

3. Start discovery to collect data from your infrastructure

4. Verify data collection is working properly

Verify Appliance Status and Data Collection

• Check that at least one Azure Migrate appliance is connected to your project
• Verify the appliance is actively collecting data
• Ensure the appliance has discovered the infrastructure you want to assess
• Navigate to Servers, databases and web apps in your Azure Migrate project
• Confirm that servers are being discovered and data is being collected
• Ensure the data is recent and up-to-date

Azure Migrate Deployment Guides according to target infrastructure:

For detailed step-by-step instructions on deploying and configuring Azure Migrate appliances, see the deployment guides above or refer to the Microsoft Learn documentation.

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.

From the left hand side menu select Tenant Settings, you will be presented with a list of options, that need to be configured.

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

or specify the Dr M Security Group.

If the setting is already configured at the organizational level, it normally does not need to be updated.

Configure the following settings:

Workspace settings -> Create workspaces (new workspace experience)

• Developer settings -> Embed content in apps

• Developer settings -> Service principals can call Fabric public APls

• Developer settings -> Service principals can create workspaces, connections, and deployment pipelines

• 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

Power BI visuals -> Allow visuals created using the Power BI SDK.

Required Visuals Instaltion

The Network Navigator visual is required for advanced dependency mapping functionality within this report. To ensure full feature availability for all users, it must be installed into the Organizational Visuals section of Power BI.

1. Download the .pbiviz file from the Network Navigator GitHub repository.

2. As a Fabric Admin, access the Power BI Admin Portal.

3. Navigate to Organizational Visuals.

4. Select Add a custom visual, then choose Upload from file.

5. Browse to the downloaded .pbiviz file and upload it.

6. Once uploaded, the visual will be available for all users in your organization via the Organizational Visuals pane in Power BI.

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.