In Project Details, specify the project name and the geography where you want to create the project.

Hello Krushnakant Patel

Thank you for posting your query on Microsoft Q&A platform.

Thanks for sharing the screenshot. Creating the Azure Migrate project alone is not sufficient to enable VMware discovery. Until an appliance is generated and connected, the VMware / vSphere Hypervisor section will appear blank, exactly like in your screenshot.

When you select “Yes, with VMware vSphere Hypervisor”, the portal is supposed to show options to:

• Generate a project key
• Download the Azure Migrate appliance (OVA or ZIP)
• Register the appliance

If none of these appear, it means one of the following is true:

1. No Azure Migrate appliance has been created for this project
2. The Discovery and assessment tool is not added to the project
3. You are opening the project from an incorrect blade (common UI pitfall)
4. The project was created but inventory tools were never initialized

VMware discovery only starts after an appliance is deployed and connected.

Please have a look into below exact resolution steps:

Step 1: Open the project from the correct blade

1. Go to Azure Portal
2. Search for Azure Migrate
3. Click Servers, databases and web apps
4. Select your existing project (do not use “All resources”)

Opening the project from “All resources” often leads to missing discovery UI elements.

Step 2: Verify the Discovery tool is added

Inside the project:

1. Go to Overview
2. Under Tools, confirm Azure Migrate: Discovery and assessment is present

If it’s missing:

• Click Add tools
• Add Discovery and assessment

Azure Migrate does not auto‑add discovery tools in some project creation flows.

Step 3: Start discovery from the correct location

1. In the project, go to Inventory
2. Click Discover
3. Choose Using appliance
4. Select:
   • Are your servers virtualized? → Yes, with VMware vSphere Hypervisor

At this point, you should now see:

• Appliance name field
• Generate key button
• Download options (OVA / ZIP)

If the appliance section appears, the issue is resolved.

Step 4: Deploy and register the appliance (mandatory)

VMware discovery cannot work without this:

• Download the appliance
• Deploy it in vCenter
• Register it using the generated key
• Connect it to vCenter

Azure Migrate discovers nothing directly from the portal — discovery is 100% appliance‑driven.

If the page is still blank after the above followed steps then it is almost always one of these hard blockers:

1. Wrong geography vs subscription context.

The project geography only stores metadata, but:

• If your subscription is restricted by policy
• Or the project was created in a tenant with limited service availability

Discovery UI may fail to load correctly as it is seen in enterprise tenants with region‑restriction policies.

2. Permissions issue - You must have Below roles.

• Contributor or Owner on the subscription
• Application Developer (or higher) in Entra ID to register the appliance

Without this, appliance generation silently fails in the UI.

To validate, Open Manage → Appliances inside the project:

• If no appliances are listed, discovery has never been initialized
• This directly explains the blank VMware screen

Azure Migrate VMware discovery does not begin at project creation. The VMware discovery page remains empty until an Azure Migrate appliance is generated, deployed, and registered with the project. Once the Discovery and assessment tool is added and an appliance is created from Inventory → Discover, the VMware vSphere options become available and discovery can proceed.

Reference: https://learn.microsoft.com/en-us/azure/migrate/migrate-support-matrix-vmware?view=migrate&tabs=businesscase

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

Create and manage projects: https://learn.microsoft.com/en-us/azure/migrate/create-manage-projects?view=migrate#find-a-project

Thanks,
Suchitra.