Azure Migrate HyperV Discovery Checklist

Requirements Overview

Data Collection Checkpoints

1. Customer meets all pre-requisites
2. A meeting has been conducted to configure and review Azure Migrate and there are no outstanding technical issues
3. Data collection has been initiated
4. Dr Migrate has been deployed

Hyper-V Discovery Reference

Microsoft provides comprehensive documentation for deploying Azure Migrate against your Hyper-V estate:

• Tutorial: Discover servers running on Hyper-V
• Support Matrix: Support matrix for Hyper-V assessment

Hyper-V Discovery Checklist

Minimum Software Requirements

Microsoft provides detailed software requirements for Hyper-V discovery. Please review:

• Server Requirements: Server requirements for Hyper-V assessment
• Hyper-V Host Requirements: Hyper-V host requirements
• Software Inventory Requirements: Software inventory requirements
• SQL Server Discovery: SQL Server instance and database discovery requirements

Minimum Appliance System Requirements

Microsoft provides detailed appliance requirements. See Azure Migrate appliance requirements for Hyper-V.

Quick Reference:

• 16-GB RAM
• 8 vCPUs
• 80 GB disk
• Windows Server 2019 or later
• Static or dynamic IP address with internet access (direct or via proxy)

Minimum Hyper-V Host Requirements

For complete Hyper-V host requirements, see Hyper-V host requirements.

Quick Reference:

• Windows Server 2022, 2019, 2016, or 2012 R2
• WinRM port 5985 (HTTP) for inbound connections
• PowerShell version 4.0 or later
• Administrator permissions OR membership in: Remote Management Users, Hyper-V Administrators, and Performance Monitor Users

Validation: Microsoft provides a script to validate these settings. Learn how to run the validation script.

Minimum Azure Permissions

In order to successfully deploy Azure Migrate, you will need:

• At the Subscription level: Contributor or Owner permissions
• Entra ID: Application Developer role or higher to register applications

Required URLs

Microsoft provides comprehensive URL requirements based on your deployment method:

• Public Endpoint: Public cloud URLs using TCP 443 with SSL bypass enabled
• Private Endpoint: Private endpoint URLs using TCP 443 with SSL bypass enabled

Minimum Port Requirements

For complete port requirements, see Port access.

Quick Reference:

Appliance Download Options

Option 1 – Hyper-V Virtual Hard Disk (VHD)

The VHD can be prepared in advance of our configuration meeting; ensure you can RDP and authenticate.

Option 2 – PowerShell Script

The Hyper-V discovery stack can also be installed using a PowerShell Script on a VM that you provision.

Credentials

Required Server Credentials

Microsoft provides detailed credential requirements for different scenarios. Please review:

• Windows Servers: Windows server credentials for software inventory
• Linux Servers: Linux server credentials with sudo privileges or least-privileged access
• Hyper-V Hosts: See Hyper-V host requirements above
• SQL Server Access: SQL Server authentication requirements - requires sysadmin role or least-privileged account

Environment Considerations

Microsoft provides detailed information on discovery limits and considerations. See Limitations.

Key Limits:

• Azure Migrate Hyper-V appliance can discover up to 5,000 servers
• Azure Migrate Hyper-V appliance can connect to up to 300 Hyper-V hosts
• You can create multiple projects per Azure subscription
• If using Hyper-V Replica, assessments may not be accurate for replicated servers

Adjusting Discovery Scope

While Azure Migrate supports scoping discovery, it is recommended to perform a complete discovery of your device estate. Assessment scope can be decided using Dr Migrate, as part of a Rapid or Advanced Assessment.

For information on limiting discovery scope, see Prepare Hyper-V for assessment.