Assess servers by using imported data
This article explains how to assess on-premises servers with the Azure Migrate: Server Assessment tool, by importing server metadata in comma-separated values (CSV) format. This assessment method doesn't require you to set up the Azure Migrate appliance to create an assessment. It's useful if:
- You want to create a quick, initial assessment before you deploy the appliance.
- You can't deploy the Azure Migrate appliance in your organization.
- You can't share credentials that allow access to on-premises servers.
- Security constraints prevent you from gathering and sending data collected by the appliance to Azure. You can control the data you share in an imported file. Also, much of the data (for example, providing IP addresses) is optional.
Before you start
Be aware of these points:
- You can add up to a maximum of 20,000 servers in a single CSV file.
- You can add up to 20,000 servers in an Azure Migrate project by using CSV.
- You can upload server information to Server Assessment multiple times by using CSV.
- Gathering application information is useful in evaluating your on-premises environment for migration. However, Server Assessment doesn't currently perform application-level assessment or take applications into account when creating an assessment.
In this tutorial, you learn how to:
- Set up an Azure Migrate project.
- Fill in a CSV file with server information.
- Import the file to add server information into Server Assessment.
- Create and review an 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 guides.
If you don't have an Azure subscription, create a free account before you begin.
Set Azure permissions for Azure Migrate
Your Azure account needs permissions to create an Azure Migrate project.
- In the Azure portal, open the subscription, and select Access control (IAM).
- In Check access, find the relevant account, and then select it to view permissions.
- Make sure you have Contributor or Owner permissions.
- If you just created a free Azure account, you're the owner of your subscription.
- If you're not the subscription owner, work with the owner to assign the role.
Set up an Azure Migrate project
To set up a new Azure Migrate project:
In the Azure portal, in 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 tool(s).
In Migrate project, select your Azure subscription, and create a resource group if you don't have one.
In PROJECT DETAILS, specify the project name and the geography in which you want to create the project. For more information:
- Review supported geographies. The project geography is used only to store the metadata gathered from on-premises VMs.
- You can select any target region when you run a migration.
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 then select Add tools.
Wait a few minutes for the Azure Migrate project to deploy. You'll then be taken to the project page. If you don't see the project, you can access it from Servers in the Azure Migrate dashboard.
Prepare the CSV
Download the CSV template and add server information to it.
Download the template
In Migration Goals > Servers > Azure Migrate: Server Assessment, select Discover.
In Discover machines, select Import using CSV.
Select Download to download the CSV template. Alternatively, you can download it directly.
Add server information
Gather server data and add it to the CSV file.
- To gather data, you can export it from tools you use for on-premises server management, such as VMware vSphere or your configuration-management database (CMDB).
- To review sample data, download our example file.
The following table summarizes the file fields to fill in:
|Server name||Yes||We recommend specifying the fully qualified domain name (FQDN).|
|IP address||No||Server address.|
|Cores||Yes||Number of processor cores allocated to the server.|
|Memory||Yes||Total RAM, in MB, allocated to the server.|
|OS name||Yes||Server operating system.|
|OS version||No||Server operating system version.|
|Number of disks||No||Not needed if individual disk details are provided.|
|Disk 1 size||No||Maximum size of disk, in GB.
You can add details for more disks by adding columns in the template. You can add up to eight disks.
|Disk 1 read ops||No||Disk read operations per second.|
|Disk 1 write ops||No||Disk write operations per second.|
|Disk 1 read throughput||No||Data read from the disk per second, in MB per second.|
|Disk 1 write throughput||No||Data written to disk per second, in MB per second.|
|CPU utilization percentage||No||Percentage of CPU used.|
|Memory utilization percentage||No||Percentage of RAM used.|
|Total disks read ops||No||Disk-read operations per second.|
|Total disks write ops||No||Disk-write operations per second.|
|Total disks read throughput||No||Data read from the disk, in MB per second.|
|Total disks write throughput||No||Data written to disk, in MB per second.|
|Network In throughput||No||Data received by the server, in MB per second.|
|Network Out throughput||No||Data transmitted by the server, in MB per second.|
|Firmware type||No||Server firmware. Values can be "BIOS" or "UEFI".|
|Server type||No||Values can be "Physical" or "Virtual".|
|Hypervisor||No||Hypervisor on which a machine is running.
Values can be "VMware", "Hyper-V", "Xen", "AWS", "GCP", or "Other".
|Hypervisor version number||No||Hypervisor version.|
|Virtual machine ID||No||VM identifier. This is the InstanceUUid value for a VMware vCenter VM, or the Hyper-V VM ID for Hyper-V.|
|Virtual machine manager ID||No||This is the InstanceUUid value for VMWare vCenter. It isn't needed for Hyper-V.MAC address|
|No||Server MAC address.|
|BIOS ID||No||Server BIOS ID.|
|Custom server ID||No||Local, unique server ID on-premises.
Useful for tracking the imported server by local ID.
|Application 1 name||No||Name of workload running on the server.
You can add details for more apps by adding columns in the template. You can add up to five applications.
|Application 1 type||No||Type of workload running on the server|
|Application 1 version||No||Version of the workload running on the server.|
|Application 1 license expiry||No||License expiry of the workload (if applicable).|
|Business unit||No||Business unit that the server belongs to.|
|Business owner||No||Business unit owner.|
|Business application name||No||Name of the application to which the app belongs.|
|Location||No||Datacenter in which the server is located.|
|Server decommission date||No||Decommission date of physical server or of the underlying physical server of the virtual server.|
Add operating systems
Assessment recognizes specific operating system names. Any name you specify must exactly match one of the strings in the supported names list.
Add multiple disks
The template provides default fields for the first disk. You can add similar columns for up to eight disks.
For example, to specify all fields for a second disk, add these columns:
- Disk 2 size
- Disk 2 read ops
- Disk 2 write ops
- Disk 2 read throughput
- Disk 2 write throughput
Add multiple applications
The template provides fields for a single application. You can add similar columns for up to five apps.
For example, to specify all fields for a second app, add these columns:
- Application 2 name
- Application 2 type
- Application 2 version
- Application 2 license expiry
App information is useful in evaluating your on-premises environment for migration. However, Azure Migrate Server Assessment doesn't currently perform app-level assessment or take apps into account when creating an assessment.
Import the server information
After adding information to the CSV template, import the servers into Server Assessment.
- In Azure Migrate, in Discover machines, go to the completed template.
- Select Import.
- The import status is shown.
- If warnings appear in the status, you can either fix them or continue without addressing them.
- To improve assessment accuracy, improve the server information as suggested in warnings.
- To view and fix warnings, select Download warning details .CSV. This operation downloads the CSV with warnings included. Review the warnings and fix issues as needed.
- If errors appear in the status so that the import status is Failed, you must fix those errors before you can continue with the import:
- Download the CSV, which now includes error details.
- Review and address the errors as necessary.
- Upload the modified file again.
- When the import status is Completed, the server information has been imported.
Update server information
You can update the information for a server by importing the data for the server again with the same Server name. You can't modify the Server name field. Deleting servers is currently not supported.
Verify servers in the portal
To verify that the servers appear in the Azure portal after discovery:
- Open the Azure Migrate dashboard.
- On the Azure Migrate - Servers > Azure Migrate: Server Assessment page, select the icon that displays the count for Discovered servers.
- Select the Import based tab.
Set up and run an assessment
You can create two types of assessments by using Server Assessment.
|Performance-based||Assessments based on performance-data values specified.||Recommended VM size: Based on CPU and memory usage data.
Recommended disk type (standard or premium managed disk): Based on the input/output per second (IOPS) and throughput of the on-premises disks.
|As on-premises||Assessments based on on-premises sizing.||Recommended VM size: Based on the server size specified.
Recommended disk type: Based on the storage-type setting you select for the assessment.
To run an assessment:
Review the best practices for creating assessments.
In the Servers tab, in the Azure Migrate: Server Assessment tile, select Assess.
In Assess servers, specify a name for the assessment.
In Discovery source, select Machines added via import to Azure Migrate.
Select View all to 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 servers to add to the group.
Select Create assessment to create the group, and then run the assessment.
After the assessment is created, view it in Servers > Azure Migrate: Server Assessment > Assessments.
Select Export assessment to download it as a Microsoft Excel file.
Review an assessment
An assessment describes:
- Azure readiness: Whether servers are suitable for migration to Azure.
- Monthly cost estimation: Estimated monthly compute and storage costs for running the servers in Azure.
- Monthly storage cost estimation: Estimated costs for disk storage after migration.
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, determine whether the servers are ready for migration to Azure.
Review the status:
- Ready for Azure: Azure Migrate recommends a VM size and cost estimates for VMs in the assessment.
- Ready with conditions: Shows problems and suggested remediation.
- Not ready for Azure: Shows problems and suggested remediation.
- Readiness unknown: Azure Migrate can't assess readiness, due to data-availability issues.
Select an Azure readiness status. You can view server-readiness details and drill down to see server details, including compute, storage, and network settings.
Review cost details
This view shows the estimated compute and storage cost of running VMs in Azure. You can:
Review the monthly compute and storage costs. Costs are aggregated for all servers in the assessed group.
- Cost estimates are based on the size recommendations for a machine, and its disks and properties.
- Estimated monthly costs for compute and storage are shown.
- The cost estimate is for running the on-premises servers as infrastructure-as-a-service (IaaS) VMs. Server Assessment doesn't consider platform-as-a-service (PaaS) or software-as-a-service (SaaS) costs.
Review monthly storage-cost estimates. This view shows aggregated storage costs for the assessed group, split among different types of storage disks.
Drill down to see details for specific VMs.
Confidence ratings are not assigned to assessments of servers imported into Server Assessment by using CSV.
Supported operating system names
A - H
Apple Mac OS X 10
Debian GNU/Linux 4
Debian GNU/Linux 5
Debian GNU/Linux 6
Debian GNU/Linux 7
Debian GNU/Linux 8
I - R
Novell NetWare 5
Novell NetWare 6
Oracle Linux 4/5
Oracle Solaris 10
Oracle Solaris 11
Red Hat Enterprise Linux 2
Red Hat Enterprise Linux 3
Red Hat Enterprise Linux 4
Red Hat Enterprise Linux 5
Red Hat Enterprise Linux 6
Red Hat Enterprise Linux 7
Red Hat Fedora
S - T
SCO OpenServer 5
SCO OpenServer 6
SCO UnixWare 7
Serenity Systems eComStation 1
Serenity Systems eComStation 2
Sun Microsystems Solaris 8
Sun Microsystems Solaris 9
SUSE Linux Enterprise 10
SUSE Linux Enterprise 11
SUSE Linux Enterprise 12
SUSE Linux Enterprise 8/9
SUSE Linux Enterprise 11
U - Z
VMware ESXi 4
VMware ESXi 5
VMware ESXi 6
Windows Server (R) 2008
Windows Server 2003
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
Windows Server Threshold
Windows Web Server 2008 R2
Windows XP Professional
In this tutorial, you:
- Imported servers into Azure Migrate: Server Assessment by using CSV.
- Created and reviewed an assessment.