Discover and Assess Your Workloads Before Migrating to Azure with Azure Migrate

End to End Pattern to migrate simple to complex application workloads.

Version 1.0 Public Endpoint

[HEADING=1]Scenario 01: Migrate VMware Guest VM’s to Azure Native VMs using Azure Migrate Appliance[/HEADING]

[HEADING=1]Part 1: What we have hosted in on-premises environment <source>[/HEADING]

• Before you can migrate your applications to Azure, you need to understand your current on-premises environment, including the connectivity, dependencies, performance, and configuration of your servers and applications.
  

Details about on-premises environment:

1. Guests hosted on VMware Hypervisor
   
   1. 
      
   2. Domain Controller
      
   3. Servers (assume we have minimum CMDB information about server owner and no information about connectivity and apps/DB hosted on each workload and why we hosted the servers and what’s running on it)
      

[*]vSphere Datacenter

[ATTACH=full]61270[/ATTACH]

1. CMDB:
   

    

   [ATTACH=full]61271[/ATTACH]

    

    

    

   4. Website URL and DB (assume no idea about this app do – functionality and so on), we will further delve in Discovery and assess phase to connect the dots and migrate the workloads successfully.

    

    

    

   [HEADING=1]Part 2: Deploying Azure Migrate appliance for Discovery and Assessment[/HEADING]

    

   All about Azure Migrate appliance à Azure Migrate documentation | Microsoft Learn

    

   CAF Migrate à Migrate overview - Cloud Adoption Framework | Microsoft Learn

    

   How to decide which Azure Migrate appliance is right for your environment? - Microsoft Community Hub

    

    

    

   Scenario: Discovery using appliance – agentless. Read more about it here on prerequisites

    

   Once you have created the Azure Migrate Project and configured your appliance as outlined here, you will see the following resources provisioned for Azure Migrate –

    

   Azure Migrate Appliance Status (non-domain joined, and selected password never expires for default administrator user, you can domain join and disable default local admin user to be compliant with your company policies):

    

   1. Azure Migrate Appliance Status:

    

   [ATTACH=full]61272[/ATTACH]

    

    

    

    

    

    

    

   2. Select Resource Group à ‘show hidden types’

    

    

    

   [ATTACH=full]61273[/ATTACH]

    

    

    

   3. Go to your Entra à

    

   [ATTACH=full]61274[/ATTACH]

    

    

    

    

    

    

    

   4. Azure Key Vault à Certificates

    

   [ATTACH=full]61275[/ATTACH]

    

    

    

    

    

   Appliance Registered successfully and discovery in progress.

    

   [ATTACH=full]61276[/ATTACH]

    

    

    

   Once the discovery is completed, will start deep diving in Discovery, Assess and Planning in the upcoming series.

    

   Scenario 2: Discover same source estate and modernize to Azure PaaS than Azure Native VMs

    

   Scenario 3: Discover Linux Workloads and migrate to Azure Native VMs / PaaS / AKS

    

   Scenario 4: Azure Migrate deployment using Private Endpoints

    

    

    

   If you have any questions or feedback, please leave a comment below. I would love to hear from you and help you with any topic that you want to learn more about and to make your migrations successful.

    

   Continue reading...