Azure Migrate Project with Public Endpoint .Appliance not showing Dicovry Agent not showingup rest all showing up connected

We have reinstalled the azuremogration powershell script multiple times and all the time its giving same error and Internet open for this host

Yes we are trying to discover Hyper-v Virtual machines and we are using the appliance for physical machine discovery as we afced issue with Software dependency after discovery with Hyper-V machines.So currently we are treating VM's are physical and trying to discover.

Below are the error messages and there is no firewall and Internet connectvity open fro tha appliance/server

Appliance after the initial powershell script implementation it updated auto to its latest version

Hello Gopakumar Sivaraman, Thanks for the update, you’re trying to discover Hyper‑V VMs using the Azure Migrate appliance but, due to Hyper‑V dependency issues, you switched to Physical machine discovery. The Discovery Agent is not appearing; other agents show “Connected”. Connectivity check fails with 400 Bad Request on the Discovery Service URL for the UAE North endpoint (uaen), despite “no firewall” and “internet connectivity open”. 

Here is the few common cause that the above issue occurs:

• The appliance registered with an Azure Migrate Project created in a region other than UAE North. The appliance is hardcoded to call the UAE North endpoint (uaen.prod.migration.windowsazure.com), but the Project Key/registration token is for a different region, causing the Azure service to reject the request as unauthorized or invalid.
• If the host's system time (or BIOS time) is significantly out of sync with the network time (Azure's time), the TLS certificate validation and the token signatures used during the initial service calls become invalid. This causes the Azure service to reject the request outright.
• The Project Key is tied to the Azure Migrate Project's Identity and Access Management (IAM) context. If the key is expired, belongs to a different project, or if the underlying Microsoft Entra ID (Azure AD) application created during registration is deleted or blocked, the appliance cannot authenticate.
• You must whitelist all required Azure Migrate URLs (not just the one shown). Missing endpoints can cause partial connectivity failures.

You can follow the below steps to resolve this: 

• Verify the Azure Migrate Project region. If the appliance is connecting to an endpoint like uaen.prod..., the corresponding Azure Migrate Project must also be in the UAE North region. If not, re-register the appliance using a new key from a project created in the correct region.
• Synchronize the Windows Server 2025 host time with an accurate external NTP source (like time.windows.com or a local domain controller). Ensure the time is correct and the timezone is set appropriately. Troubleshoot the Azure Migrate appliance - Azure Migrate | Microsoft Learn
• Generate a new Project Key in the Azure Migrate Project and re-register the appliance. If the issue persists, check the health of the associated Azure AD application (use the Diagnose and solve feature in the appliance configuration manager). Troubleshoot the Azure Migrate appliance - Azure Migrate | Microsoft Learn
• Whitelist Required URLs: Ensure outbound HTTPS (TCP 443) access and DNS resolution for:

    *.migration.windowsazure.com – Appliance service endpoints
    login.microsoftonline.com – Authentication and token exchange
    *.azureedge.net – CDN for content delivery
  

  You can follow this document to created an allowlist: Troubleshoot the Azure Migrate appliance - Azure Migrate | Microsoft Learn https://learn.microsoft.com/en-us/azure/migrate/migrate-appliance?view=migrate#url-access
• Run Diagnostics Again: From the appliance portal, rerun Service Endpoint Connectivity. If it still fails, download the diagnostic logs and check for malformed request headers.

Reference documents you can follow: https://learn.microsoft.com/en-us/azure/migrate/troubleshoot-appliance?view=migrate&tabs=windows

https://learn.microsoft.com/en-us/azure/migrate/tutorial-discover-hyper-v?view=migrate

Hope this helps. If you still encounter any issue, please do let us know. thanks

Hello Gopakumar Sivaraman, Could you please let us know if the solution shared in the comment addressed your query. If you have any other questions or need further support, please feel free to contact us.

Thanks,

Suchitra.