Azure Migrate Physical Discovery Checklist
Requirements Overview¶
| Requirement | Learn More | |
|---|---|---|
| A user with Contributor or Owner permissions over the Subscription | Learn More | |
| A user with Application Developer or Higher in Entra ID | Learn More | |
| Prepare Azure Migrate appliance, ensure RDP and authenticate. | Learn More | |
| All required Public or Private endpoint URLs are enabled. | Learn More | |
| All required Ports are allowed through required Firewalls/Proxies. | Learn More | |
| All required credentials are in place, validated and tested. | Learn More | |
| Environment scope is understood and agreed. | Learn More |
Data Collection Organizational Workflow¶
- Customer meets all requirements
- A meeting has been conducted to configure and review Azure Migrate
- Any troubleshooting sessions have been undertaken as necessary
- Data collection has been started
- Dr Migrate has been deployed
Physical Discovery Reference¶
Microsoft provides comprehensive documentation for deploying Azure Migrate against physical servers and other infrastructure:
- Tutorial: Discover physical servers
- Support Matrix: Support matrix for physical server discovery and assessment
The Physical appliance can be used to discover assessment data from any Windows or Linux device. This includes AWS, GCP and Azure hosted VMs.
Physical Discovery Checklist¶
Minimum Software Requirements¶
Microsoft provides detailed physical server requirements. Please review:
- Physical Server Requirements: Physical server requirements
- Software Inventory Requirements: Software inventory requirements
- SQL Server Discovery: SQL Server instance and database discovery requirements
The appliance can be deployed on to existing hypervisor infrastructure, alongside other discovery appliances.
Minimum Appliance System Requirements¶
Microsoft provides detailed appliance requirements. See Azure Migrate appliance requirements for physical servers.
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 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
If you are familiar with Azure Migrate and want to connect the discovery appliance in advance of the joint configuration meeting, be sure to:
- Choose defaults for the Azure Migrate project; make no changes in Advanced options.
- Connect all appliances to the same project.
Required URLs¶
Public Endpoint connectivity method is recommended for the smoothest experience.
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
For more information on deploying Azure Migrate with Private endpoints, see Discover and assess using private endpoints.
Minimum Port Requirements¶
For complete port requirements, see Port access.
Quick Reference:
| Source | Destination | Port |
|---|---|---|
| Appliance | Azure URLs | TCP 443 |
| Appliance | Windows Server targets | TCP 5985 (HTTP) or TCP 5986 (HTTPS) |
| Appliance | SQL Servers | TCP 1433 |
| Appliance | Linux Servers | TCP 22 |
Appliance Download Options¶
PowerShell Script¶
The Physical discovery stack is installed using a PowerShell Script on a VM that you provision.
If you are familiar with Azure Migrate, you are welcome to download the PowerShell script and run it choosing options 3,1,1,Y.
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
- SQL Server Access: SQL Server authentication requirements - sysadmin role or least-privileged account
Environment Considerations¶
Microsoft provides detailed information on discovery limits and considerations. See Limitations.
Key Limits:
- Azure Migrate appliance can discover up to 1,000 physical servers
- You can create multiple projects per Azure subscription
- A project can include physical servers, VMware servers, and Hyper-V servers, up to the assessment limits for each
Dependency Analysis Best Practice:
One Azure Migrate project can perform dependency data collection concurrently for 1,000 servers per appliance.
If you have more than 1,000 devices being discovered, it is recommended to evenly spread the discovery of the estate across additional appliances, ensuring that no more than 1,000 devices are being discovered by one appliance.
For more details, see Dependency analysis requirements (agentless).
Adjusting Discovery Scope¶
You can provide the appliance the FQDNs of the devices you want to discover.
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.