Assess VMware VMs with Server Assessment
This article shows you how to assess on-premises VMware virtual machines (VMs), using the Azure Migrate:Server Assessment tool.
This tutorial is the second in a series that demonstrates how to assess and migrate VMware VMs to Azure. In this tutorial, you learn how to:
- Set up an Azure Migrate project.
- Set up an Azure Migrate appliance that runs on-premises to assess VMs.
- Start continuous discovery of on-premises VMs. The appliance sends configuration and performance data for discovered VMs to Azure.
- Group discovered VMs, and assess the VM group.
- Review the assessment.
Tutorials show you the simplest deployment path for a scenario so that you can quickly set up a proof-of-concept. Tutorials use default options where possible, and don't show all possible settings and paths. For detailed instructions, review the how-to articles.
If you don't have an Azure subscription, create a free account before you begin.
- Complete the first tutorial in this series. If you don't, the instructions in this tutorial won't work.
- Here's what you should have done in the first tutorial:
Set up an Azure Migrate project
Set up a new Azure Migrate project as follows:
In the Azure portal > All services, search for Azure Migrate.
Under Services, select Azure Migrate.
In Overview, under Discover, assess and migrate servers, select Assess and migrate servers.
In Getting started, select Add tools.
In Migrate project, select your Azure subscription, and create a resource group if you don't have one.
In Select assessment tool, select Azure Migrate: Server Assessment > Next.
In Select migration tool, select Skip adding a migration tool for now > Next.
In Review + add tools, review the settings, and select Add tools.
Wait a few minutes for the Azure Migrate project to deploy. You'll be taken to the project page. If you don't see the project, you can access it from Servers in the Azure Migrate dashboard.
Set up the Azure Migrate appliance
Azure Migrate:Server Assessment uses a lightweight Azure Migrate appliance. The appliance performs VM discovery and sends VM metadata and performance data to Azure Migrate. The appliance can be set up in a number of ways.
- Set up on a VMware VM using a downloaded OVA template. This is the method used in this tutorial.
- Set up on a VMware VM or physical machine with a PowerShell installer script. This method should be used if you can't set up a VM using an OVA template, or if you're in Azure Government.
After creating the appliance, you check that it can connect to Azure Migrate:Server Assessment, configure it for the first time, and register it with the Azure Migrate project.
Download the OVA template
In Migration Goals > Servers > Azure Migrate: Server Assessment, select Discover.
In Discover machines > Are your machines virtualized?, select Yes, with VMWare vSphere hypervisor.
Select Download to download the OVA template file.
Check that the OVA file is secure, before you deploy it:
On the machine to which you downloaded the file, open an administrator command window.
Run the following command to generate the hash for the OVA file:
C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]
C:\>CertUtil -HashFile C:\AzureMigrate\AzureMigrate.ova SHA256
For version 2.19.07.30, the generated hash should match these values:
Create the appliance VM
Import the downloaded file, and create a VM:
In the vSphere Client console, select File > Deploy OVF Template.
In the Deploy OVF Template Wizard > Source, specify the location of the OVA file.
In Name and Location, specify a friendly name for the VM. Select the inventory object in which the VM will be hosted.
In Host/Cluster, specify the host or cluster on which the VM will run.
In Storage, specify the storage destination for the VM.
In Disk Format, specify the disk type and size.
In Network Mapping, specify the network to which the VM will connect. The network needs internet connectivity to send metadata to Azure Migrate Server Assessment.
Review and confirm the settings, and then select Finish.
Verify appliance access to Azure
Configure the appliance
Set up the appliance for the first time.
If you set up the appliance using a PowerShell script instead of the downloaded OVA, the first two steps in this procedure aren't relevant.
In the vSphere Client console, right-click the VM, and then select Open Console.
Provide the language, time zone, and password for the appliance.
Open a browser on any machine that can connect to the VM, and open the URL of the appliance web app: https://appliance name or IP address: 44368.
Alternately, you can open the app from the appliance desktop by selecting the app shortcut.
In the web app > Set up prerequisites, do the following:
License: Accept the license terms, and read the third-party information.
Connectivity: The app checks that the VM has internet access. If the VM uses a proxy:
- Select Proxy settings, and specify the proxy address and listening port in the form http://ProxyIPAddress or http://ProxyFQDN.
- Specify credentials if the proxy needs authentication.
- Only HTTP proxy is supported.
Time sync: The time on the appliance should be in sync with internet time for discovery to work properly.
Install updates: The appliance ensures that the latest updates are installed.
Install VDDK: The appliance checks that VMWare vSphere Virtual Disk Development Kit (VDDK) is installed. If it isn't installed, download VDDK 6.7 from VMware, and extract the downloaded zip contents to the specified location on the appliance.
Azure Migrate Server Migration uses the VDDK to replicate machines during migration to Azure.
Register the appliance with Azure Migrate
Select Log In. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
On the new tab, sign in by using your Azure username and password.
Sign-in with a PIN isn't supported.
After you successfully sign in, go back to the web app.
Select the subscription in which the Azure Migrate project was created, and then select the project.
Specify a name for the appliance. The name should be alphanumeric with 14 characters or fewer.
Start continuous discovery
The appliance needs to connect to vCenter Server to discover the configuration and performance data of the VMs.
Specify vCenter Server details
In Specify vCenter Server details, specify the name (FQDN) or IP address of the vCenter Server instance. You can leave the default port or specify a custom port on which vCenter Server listens.
In User name and Password, specify the vCenter Server account credentials that the appliance will use to discover VMs on the vCenter Server instance.
- You should have set up an account with the required permissions in the previous tutorial.
- If you want to scope discovery to specific VMware objects (vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual VMs.), review the instructions in this article to restrict the account used by Azure Migrate.
Select Validate connection to make sure that the appliance can connect to vCenter Server.
In Discover applications and dependencies on VMs, optionally click Add credentials, and specify the operating system for which the credentials are relevant, and the credentials username and password. Then click Add.
Save and start discovery, to kick off VM discovery.
Discovery works as follows:
- It takes around 15 minutes for discovered VM metadata to appear in the portal.
- Discovery of installed applications, roles, and features takes some time. The duration depends on the number of VMs being discovered. For 500 VMs, it takes approximately one hour for the application inventory to appear in the Azure Migrate portal.
Verify VMs in the portal
After discovery, you can verify that the VMs appear in the Azure portal:
- Open the Azure Migrate dashboard.
- In Azure Migrate - Servers > Azure Migrate: Server Assessment, select the icon that displays the count for Discovered servers.
Set up an assessment
You can create two types of assessments by using Azure Migrate Server Assessment:
|Performance-based||Assessments based on collected performance data||Recommended VM size: Based on CPU and memory utilization data.
Recommended disk type (standard or premium managed disk): Based on the IOPS and throughput of the on-premises disks.
|As on-premises||Assessments based on on-premises sizing||Recommended VM size: Based on the on-premises VM size.
Recommended disk type: Based on the storage type setting that you select for the assessment.
Run an assessment
Run an assessment as follows:
Review the best practices for creating assessments.
On the Servers tab, in the Azure Migrate: Server Assessment tile, select Assess.
In Assess servers, specify a name for the assessment.
Select View all, and then review the assessment properties.
In Select or create a group, select Create New, and specify a group name. A group gathers one or more VMs together for assessment.
In Add machines to the group, select VMs to add to the group.
Select Create Assessment to create the group and run the assessment.
After the assessment is created, view it in Servers > Azure Migrate: Server Assessment > Assessments.
Select Export assessment to download it as an Excel file.
Review an assessment
An assessment describes:
- Azure readiness: Whether VMs are suitable for migration to Azure.
- Monthly cost estimation: The estimated monthly compute and storage costs for running the VMs in Azure.
- Monthly storage cost estimation: Estimated costs for disk storage after migration.
To view an assessment:
In Migration goals > Servers, select Assessments in Azure Migrate: Server Assessment.
In Assessments, select an assessment to open it.
Review Azure readiness
In Azure readiness, verify whether VMs are ready for migration to Azure.
Review the VM status:
- Ready for Azure: Used when Azure Migrate recommends a VM size and cost estimates for VMs in the assessment.
- Ready with conditions: Shows issues and suggested remediation.
- Not ready for Azure: Shows issues and suggested remediation.
- Readiness unknown: Used when Azure Migrate can't assess readiness because of data availability issues.
Select an Azure readiness status. You can view VM readiness details. You can also drill down to see VM details, including compute, storage, and network settings.
Review cost details
The assessment summary shows the estimated compute and storage cost of running VMs in Azure. Costs are aggregated for all VMs in the assessed group. You can drill down to see cost details for specific VMs.
Cost estimates are based on the size recommendations for a machine, its disks, and its properties. Estimates are for running the on-premises VMs as IaaS VMs. Azure Migrate Server Assessment doesn't consider PaaS or SaaS costs.
The aggregated storage costs for the assessed group are split over different types of storage disks.
Review confidence rating
Azure Migrate Server Assessment assigns a confidence rating to a performance-based assessment, from one star (lowest) to five stars (highest).
The confidence rating helps you estimate the reliability of the assessment's size recommendations. The rating is based on the availability of data points needed to compute the assessment:
|Data point availability||Confidence rating|
Learn about best practices for confidence ratings.
In this tutorial, you set up an Azure Migrate appliance. You also created and reviewed an assessment.
To learn how to migrate VMware VMs to Azure by using Azure Migrate Server Migration, continue to the third tutorial in the series: