A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Hello Ashwin Nayak, it sounds like you’re trying to do agentless discovery of physical servers, but physical-server migrations in Azure Migrate only work with the agent-based model. Here are a few things to check:
- Make sure you’re using the agent-based approach for physical/bare-metal servers
- Agentless (WMI/SSH) discovery only applies to VMware VMs.
- For physical servers you need to download and install the Azure Migrate agent on each machine.
- Verify the agent can talk to your Azure Migrate appliance
- On Windows servers: • WinRM service must be running and reachable (ports 5985/5986 or 443, depending on your setup). • Windows Firewall rules should allow Remote Event Log Management, WMI, RPC/DCOM • Provide a local or domain admin account in the appliance’s Credentials list
- On Linux servers: • SSH must be enabled and reachable (port 22 by default) • Supply the correct SSH key or username/password in the appliance
- Check the appliance logs for specific errors
- In the appliance VM, open the Configuration Manager and go to Logs → Discovery to see any credential failures, connectivity issues, or timeouts.
- Review the prerequisites and support matrix
- Are your servers running a supported OS release?
- Do they meet the hardware/OS requirements listed in the physical-server support matrix?
Reference docs
- Migrate physical servers to Azure (agent-based)
- Support matrix for physical server migration
- Troubleshoot discovery issues
- Troubleshoot the appliance setup
- General troubleshooting for Azure Migrate
Hope this helps! Thanks