Configure Private Endpoint

If you are using a Private Endpoint configured Azure Migrate, certain changes are needed to ensure that data can be captured from the environment.

Configure Azure Migrate Project Settings

The way Azure Migrate has designed it’s APIs means that no 3rd Party ISV (including Dr Migrate) can work with the base Private Endpoint configuration - Azure Migrate specifies that in their documentation here.

This leads to an inability to ingest any performance data for your machines, which is important for right-sizing and accurate costing network dependency data for your machines, which is important for application dependency mapping, application complexity & wave planning

There are 2 options for ensuring this connectivity:

• Enable public network access on Azure Migrate, then for to the Storage Account connected to Azure Migrate and set access to Public Network Access
• Enable public network access on Azure Migrate, then for the Storage Account connected to Azure Migrate enable the Storage Service Endpoint, and bind it to the deployed Dr Migrate vNet

When using Private Endpoints Dr Migrate can not fully utilise the data within an Azure Migrate project if the public network access is disabled.

The Azure Migrate project should be configured to allow traffic from all networks to receive data from Dr Migrate.

Additional Configuration Steps

Option 1: Allow Public Network Access on Azure Migrate Storage Account

The simpliest and quickest option for enabling Dr Migrate to sucsessfully connect to an Azure Migrate Project is to allow Public Network access to the storage account that is connected to your Azure Migrate Project.

Option 2: Add Network Service Endpoint to Dr Migrate vNet

Service endpoints routes traffic from the virtual network through an optimal path to the Azure Storage service. This allows Dr Migrate to extract the data from the Azure Migrate project while maintaining private endpoint connectivity.

To learn more about Network Service Endpoints, please see here.