Azuremigrate appliance

Hello ELAKER Abderrazak

Thank you for reaching out to the Microsoft Q&A forum.

It looks like your Azure Migrate appliance is tripping over the “Set up prerequisites” connectivity check—specifically it can’t reach https://developer.microsoft.com/graph and is getting a 504 gateway timeout. That URL is used by the appliance to call Microsoft Graph, so if it can’t get there you’ll hit that error.

Here’s what to try next:

Give it a few minutes and retry • Sometimes it’s just a transient hiccup on the Microsoft side.

Validate your network/firewall/proxy settings • Make sure developer.microsoft.com and graph.microsoft.com (or *.graph.microsoft.com) are allowed through your corporate firewall or proxy. • If you’re using a proxy, double-check the proxy URL, credentials and the “bypass proxy for local addresses” toggle in the appliance config manager.

1. Test connectivity from the appliance itself • RDP into the appliance VM and, for example, run: – In PowerShell: Test-NetConnection developer.microsoft.com -Port 443 – Or just open a browser on the appliance VM and browse to https://developer.microsoft.com/graph.
2. Check DNS resolution • Ensure the appliance can resolve developer.microsoft.com and graph.microsoft.com to the correct IPs.
3. Review appliance logs if it still fails • Logs are under C:\ProgramData\AzureAppliance\Logs\ – check the auto-update and Graph-related entries around the time you re-ran the check.

If you still can’t get past that step, can you share a bit more info?

• Are you behind a corporate proxy or firewall that recently changed? • Have you successfully run discovery on this appliance before, or is it a fresh deploy? • Screenshot of your proxy/network settings in the Appliance Configuration Manager • Any errors in the appliance event logs under C:\ProgramData\AzureAppliance\Logs\

Reference docs: • Azure Migrate appliance requirements (network & hardware): https://learn.microsoft.com/azure/migrate/migrate-appliance?view=migrate#appliance---vmware • How to use Azure Migrate with private endpoints: https://learn.microsoft.com/azure/migrate/how-to-use-azure-migrate-with-private-endpoints • General troubleshooting for Azure Migrate: https://learn.microsoft.com/azure/migrate/troubleshoot-general

Hope this helps you unblock the appliance setup!

The issue is a connectivity failure in the Azure Migrate appliance prerequisite checks. Treat it as a network/connectivity problem between the appliance and required service endpoints.

Perform these steps on one appliance and then on the others:

1. Validate internet/proxy access
   • From the appliance server, verify that outbound internet access is available either directly or via the configured proxy.
   • If a proxy is used, in the appliance configuration manager go to Step 1: Set up prerequisites → Setup proxy and confirm the proxy address, port, and credentials are correct.
   • Ensure no corporate firewall or proxy rule started blocking Microsoft URLs today.
2. Confirm required URLs are allowed
   • Ensure that all required Azure Migrate URLs are reachable from the appliance and are allowlisted on any firewall or proxy. If any URL is blocked, the connectivity check will fail.
   • If using private endpoints, also confirm that the appliance still has network connectivity to the Azure Migrate private endpoint FQDNs and that DNS resolves them to the expected private IPs.
3. Rerun the connectivity and auto‑update checks
   • In the appliance configuration manager, on Setup prerequisites, rerun the Connectivity checks and Auto update check.
   • If any component update fails, either rerun prerequisites again or manually update the appliance services as documented.
4. Check for private endpoint–specific issues (if applicable)
   • If the project uses private endpoints, on the Azure Migrate project Properties page select Download DNS settings and verify DNS mappings are correctly configured on-premises.
   • From the appliance server, run DNS lookups for the Azure Migrate service FQDNs listed in the DNS settings file and confirm they resolve to private IPs.
5. If the problem persists across all appliances
   • After confirming local network, proxy, and DNS are correct and rerunning prerequisites, open a Microsoft support case as indicated in the prerequisite check dialog so the service endpoint issue can be investigated.

References:

• Troubleshoot the Azure Migrate appliance
• Diagnose and solve issues with Azure Migrate appliance
• Troubleshoot network connectivity