Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
927 questions
Azure Migration from Hyper-V to Azure
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 41%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Shuvajit Roy
166
Reputation points
Hi,
I am working to migrate my VM from Hyper-V to Azure. However, I face issues in the step labeled in the screenshot. I incorporated the possible steps for resolution however, non of them worked.
Can anybody suggest any solution?
Azure Migrate
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
{count} votes
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator2023-06-26T16:01:53.52+00:00 Hello @Shuvajit Roy Thank you for reaching out to us on Microsoft Q&A platform. Sorry for the delayed response!
I see that you are planning to migrate your Hyper-V VMs to Azure. However, you were greeted with an error "validation failed" during discovery phase.
The error "Verify the credentials provided for discovery" typically occurs when the Azure Migrate appliance is unable to authenticate with the Hyper-V host or cluster. To resolve this issue, you can try the following steps**:**
- Verify that the credentials you provided for the Hyper-V host or cluster are correct. Make sure that you are using the correct username and password, and that the account has the necessary permissions to access the Hyper-V host or cluster.
- Check that the Hyper-V host or cluster is reachable from the Azure Migrate appliance. You can try pinging the host or cluster from the appliance to verify connectivity.
- Ensure that the Windows Remote Management (WinRM) service is running on the Hyper-V host or cluster. You can check this by running the command
Get-Service WinRMon the Hyper-V host or cluster. - Check that the firewall on the Hyper-V host or cluster is not blocking traffic on the WinRM port (default is 5985). You can try temporarily disabling the firewall to see if this resolves the issue.
- If you are using a self-signed certificate on the Hyper-V host or cluster, make sure that the certificate is trusted by the Azure Migrate appliance. You can try importing the certificate into the Trusted Root Certification Authorities store on the appliance.
If none of these steps resolve the issue, you may need to troubleshoot further or seek assistance from Azure technical support team.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-06-28T08:40:49.8933333+00:00 @Shuvajit Roy Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-07-03T06:14:12.43+00:00 @Shuvajit Roy We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
-
Shuvajit Roy 166 Reputation points
2023-07-03T07:12:35.66+00:00 Hi, Thank you for the suggestions. However, all the suggested recommendations were checked by me and found them to be fine from the machine. Nevertheless, i had issues with the hyperv host name. Once i resolved it i could successfully validate. Thank u
-
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator
2023-07-05T10:36:35.4533333+00:00 @Shuvajit Roy Thanks for the update. Glad to know the issue is resolved now.
-
Nikša Pirović 0 Reputation points2024-05-06T20:22:03.1066667+00:00 Hi @Shuvajit Roy , how did you resolve your hyper v host? with the hosts file or other method?
Sign in to comment
Sign in to answer