Azure Migrate appliance download SHA256 hash does not match portal-published value

Admin-Avila, Dom 0 Reputation points
2026-06-23T21:21:11.5466667+00:00

We are deploying an Azure Migrate appliance for VMware discovery.

The appliance package downloaded from the Azure portal fails SHA256 integrity validation. The SHA256 value calculated locally does not match the SHA256 value currently published in the Azure portal for that same appliance download.

We have already:

  • Deleted the original package
  • Downloaded a fresh copy from the Azure portal
  • Recalculated the SHA256 hash with PowerShell
  • Confirmed we are validating the downloaded file shown by the Azure Migrate project

This blocks appliance deployment before installation and registration.

Can a Microsoft engineer confirm whether the published SHA256 value for the current Azure Migrate appliance package is correct, or whether there is a known issue with the appliance download/CDN distribution?

I can provide the expected and calculated hashes privately if needed.

Azure Migrate
Azure Migrate

A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.


2 answers

Sort by: Most helpful
  1. Admin-Avila, Dom 0 Reputation points
    2026-07-06T21:44:14.4633333+00:00

    It really seems as though the documentation is out of data. I do not have the ability to create a ticket no matter what I do, I am circled back to post on the QA again. I am hoping someone from Microsoft can actually either get me updated documentation, or get me a ticket opened, as for what ever reason, I can create one myself.

    Was this answer helpful?


  2. Alex Burlachenko 23,975 Reputation points MVP Volunteer Moderator
    2026-06-30T11:45:19.07+00:00

    i Admin-Avila, Dom,

    Thx for sharing urs issue here at Q&A portal. If a fresh download from Azure portal still doesn’t match the SHA256 shown for that same Azure Migrate appliance package, don’t install it. Hash mismatch should be treated as a failed integrity check, even if it may just be a portal/CDN metadata mismatch. I’d retry once from a different network/browser and make sure the file isn’t being altered by proxy/AV inspection. If the hash still differs, this needs Microsoft confirmation.

    Use PowerShell something like

    Get-FileHash .\AzureMigrateAppliance.zip -Algorithm SHA256

    Docs if u would like https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-vmware & https://learn.microsoft.com/en-us/azure/migrate/migrate-appliance

    Open an Azure Migrate support case and provide the project region, appliance type, download time in UTC, portal-published hash, calculated hash, file size, and download URL if visible. Ask MS to confirm whether the published SHA256 or the current CDN package is wrong.

    Rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

    and at my blog https://ctrlaltdel.blog/

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.