Assess the digital estate

In an ideal migration, every asset (infrastructure, app, or data) would be compatible with a cloud platform and ready for migration. In reality, not everything should be migrated to the cloud. Furthermore, not every asset is compatible with cloud platforms. Before migrating a workload to the cloud, it is important to assess the workload and each related asset (infrastructure, apps, and data).

The resources in this section will help you assess of your environment to determine its suitability for migration and which methods to consider.

The following tools help you assess your environment to determine the suitability of migration and best approach to use. For helpful information on choosing the right tools to support your migration efforts, see the Cloud Adoption Framework's migration tools decision guide.

Azure Migrate

The Azure Migrate service assesses on-premises VMware or Hyper-V servers and their dependencies for migration to Azure. The service assesses the migration suitability of on-premises machines, performs performance-based sizing, and provides cost estimates for running on-premises machines in Azure. If you're considering "lift and shift" migrations, or are in the early assessment stages of migration, this service is for you. After the assessment, you can use other services like Azure Site Recovery and Azure Database Migration Service to migrate the machines to Azure.

Azure Migrate overview

Create a new migration project

To get started with Azure Migrate follow these steps:

  1. Select Azure Migrate.
  2. Create a new migration project.
  3. Select Discover and Assess.
  4. Follow the Discover machines wizard.
    1. Download, create, configure the collector appliance for on-premises.
  5. Follow the Create assessment wizard.


Azure Migrate v2, currently in preview, provides improved capabilities, we recommend signing up for the preview and using these updated capabilities in your migration projects.

Service Map

Service Map automatically discovers application components on Windows and Linux systems and maps the communication between services. With Service Map, you can view your servers in the way that you think of them: as interconnected systems that deliver critical services. Service Map shows connections between servers, processes, inbound and outbound connection latency, and ports across any TCP-connected architecture, with no configuration required other than the installation of an agent.

Azure Migrate and Azure Migrate v2 (currently in preview) use Service Map to enhance the reporting capabilities and dependencies across the environment. Full details of this integration are outlined in Dependency visualization. If you use the Azure Migration service then there are no additional steps required to configure and obtain the benefits of Service Map. The following instructions are provided for your reference should your wish to use Service Map for other purposes or projects.

Enable dependency visualization using Service Map

To use dependency visualization, you need to download and install agents on each on-premises machine that you want to analyze.

  • Microsoft Monitoring agent (MMA) needs to be installed on each machine.
  • The dependency agent needs to be installed on each machine.
  • In addition, if you have machines with no internet connectivity, you need to download and install Log Analytics gateway on them.

Read more