Support matrix for Hyper-V assessment
This article summarizes prerequisites and support requirements when you discover and assess on-premises servers running in a Hyper-V environment for migration to Azure, using the Azure Migrate: Discovery and assessment tool. If you want to migrate servers running on Hyper-V to Azure, review the migration support matrix.
To set up discovery and assessment of servers running on Hyper-V, you create a project, and add the Azure Migrate: Discovery and assessment tool to the project. After the tool is added, you deploy the Azure Migrate appliance. The appliance continuously discovers on-premises servers, and sends server metadata and performance data to Azure. After discovery is complete, you gather discovered servers into groups, and run an assessment for a group.
|Assessment limits||You can discover and assess up to 35,000 servers in a single project.|
|Project limits||You can create multiple projects in an Azure subscription. In addition to servers on Hyper-V, a project can include servers on VMware and physical servers, up to the assessment limits for each.|
|Discovery||The Azure Migrate appliance can discover up to 5000 servers running on Hyper-V.
The appliance can connect to up to 300 Hyper-V hosts.
|Assessment||You can add up to 35,000 servers in a single group.
You can assess up to 35,000 servers in a single assessment for a group.
Learn more about assessments.
Hyper-V host requirements
|Hyper-V host||The Hyper-V host can be standalone, or deployed in a cluster.
The Hyper-V host can run Windows Server 2019, Windows Server 2016, or Windows Server 2012 R2. Server core installations of these operating systems are also supported.
You can't assess servers located on Hyper-V hosts running Windows Server 2012.
|Permissions||You need Administrator permissions on the Hyper-V host.
If you don't want to assign Administrator permissions, create a local or domain user account, and add the user account to these groups- Remote Management Users, Hyper-V Administrators, and Performance Monitor Users.
|PowerShell remoting||PowerShell remoting must be enabled on each Hyper-V host.|
|Hyper-V Replica||If you use Hyper-V Replica (or you have multiple servers with the same server identifiers), and you discover both the original and replicated servers using Azure Migrate, the assessment generated by Azure Migrate might not be accurate.|
|Operating system||All operating systems can be assessed for migration.|
|Integration Services||Hyper-V Integration Services must be running on servers that you assess, in order to capture operating system information.|
|Storage||Local Disk, DAS, JBOD, Storage Spaces, CSV, SMB. These Hyper-V Host storages on which VHD/VHDX are stored are supported.
IDE and SCSI virtual controllers are supported
Azure Migrate appliance requirements
Azure Migrate uses the Azure Migrate appliance for discovery and assessment. You can deploy the appliance using a compressed Hyper-V VHD that you download from the portal, or using a PowerShell script.
- Learn about appliance requirements for Hyper-V.
- Learn about URLs that the appliance needs to access in public and government clouds.
- In Azure Government, you must deploy the appliance using the script.
The following table summarizes port requirements for assessment.
|Appliance||Inbound connections on TCP port 3389 to allow remote desktop connections to the appliance.
Inbound connections on port 44368 to remotely access the appliance management app using the URL:
Outbound connections on ports 443 (HTTPS), to send discovery and performance metadata to Azure Migrate.
|Hyper-V host/cluster||Inbound connection on WinRM port 5985 (HTTP) or 5986 (HTTPS) to pull metadata and performance data for servers on Hyper-V, using a Common Information Model (CIM) session.|
Agent-based dependency analysis requirements
Dependency analysis helps you to identify dependencies between on-premises servers that you want to assess and migrate to Azure. The table summarizes the requirements for setting up agent-based dependency analysis. Hyper-V currently only supports agent-based dependency visualization.
|Before deployment||You should have a project in place, with the Azure Migrate: Discovery and assessment tool added to the project.
You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises servers.
Learn how to create a project for the first time.
Learn how to add Azure Migrate: Discovery and assessment tool to an existing project.
Learn how to set up the appliance for discovery and assessment of servers on Hyper-V.
|Azure Government||Dependency visualization isn't available in Azure Government.|
|Log Analytics||Azure Migrate uses the Service Map solution in Azure Monitor logs for dependency visualization.
You associate a new or existing Log Analytics workspace with a project. The workspace for a project can't be modified after it's added.
The workspace must be in the same subscription as the project.
The workspace must reside in the East US, Southeast Asia, or West Europe regions. Workspaces in other regions can't be associated with a project.
The workspace must be in a region in which Service Map is supported.
In Log Analytics, the workspace associated with Azure Migrate is tagged with the Migration Project key, and the project name.
|Required agents||On each server you want to analyze, install the following agents:
The Microsoft Monitoring agent (MMA).
The Dependency agent.
If on-premises servers aren't connected to the internet, you need to download and install Log Analytics gateway on them.
Learn more about installing the Dependency agent and MMA.
|Log Analytics workspace||The workspace must be in the same subscription as the project.
Azure Migrate supports workspaces residing in the East US, Southeast Asia, and West Europe regions.
The workspace must be in a region in which Service Map is supported.
The workspace for a project can't be modified after it's added.
|Costs||The Service Map solution doesn't incur any charges for the first 180 days (from the day that you associate the Log Analytics workspace with the project)/
After 180 days, standard Log Analytics charges will apply.
Using any solution other than Service Map in the associated Log Analytics workspace will incur standard charges for Log Analytics.
When the project is deleted, the workspace is not deleted along with it. After deleting the project, Service Map usage isn't free, and each node will be charged as per the paid tier of Log Analytics workspace/
If you have projects that you created before Azure Migrate general availability (GA- 28 February 2018), you might have incurred additional Service Map charges. To ensure payment after 180 days only, we recommend that you create a new project, since existing workspaces before GA are still chargeable.
|Management||When you register agents to the workspace, you use the ID and key provided by the project.
You can use the Log Analytics workspace outside Azure Migrate.
If you delete the associated project, the workspace isn't deleted automatically. Delete it manually.
Don't delete the workspace created by Azure Migrate, unless you delete the project. If you do, the dependency visualization functionality will not work as expected.
|Internet connectivity||If servers aren't connected to the internet, you need to install the Log Analytics gateway on them.|
|Azure Government||Agent-based dependency analysis isn't supported.|