Azure Migrate "Generate key" button permanently disabled - never activates

Question

Azure Migrate "Generate key" button permanently disabled - never activates

Akshat Singh 0

User's image

The core issue: the "Generate key" button itself never becomes clickable/enabled, regardless of the appliance name entered. The tooltip shown is "Appliance name not found" (see screenshot).

This happens on every attempt - fresh projects, different regions (East US, West Europe, Central US), different resource groups, fresh browser sessions, incognito mode, and after waiting for RBAC propagation (Azure Migrate Owner role assigned).

Confirmed via DevTools Console: MigrateV2-ApplianceListHelper-fetchApplianceNameToSiteIdList fails repeatedly in the background on page load, before any button click occurs - so this fails during page load/validation, not during actual key generation.

Also confirmed:

Microsoft.Migrate, Microsoft.OffAzure, and Microsoft.DependencyMap resource providers are all Registered
No active Azure service outages (checked via portal's own GetOnDemandData API: outages: [], whatsNew: [])
A previous project in the same tenant/subscription successfully generated an appliance key weeks ago, so this isn't a permanent account-level restriction

Since the button never activates, I'm unable to click Generate key to produce a fresh Activity Log entry or correlation ID the normal way. Is there another way to capture diagnostic data for this specific "frozen before click" symptom?

0 comments

2 answers

Your answer

Answer 1

Hi Akshat Singh & thx for join me at Q&A platform,

portal/backend validation failure rather than an actual key-generation failure. After entering a valid appliance name, Generate key should become available and start creation of the required Azure Migrate resources. In your case that stage is never reached. The repeated MigrateV2-ApplianceListHelper-fetchApplianceNameToSiteIdList failure is particularly relevant. If that lookup fails during page initialization, the portal can't validate the appliance name and leaves Generate key disabled with the misleading Appliance name not found message. Given that you've reproduced it across new projects, regions and browser sessions, I wouldn't keep recreating projects or changing RBAC.

You can still capture useful diagnostics even though no ARM operation is being created. While reproducing the issue, use Ctrl+Alt+A in the Azure portal to download PortalDiagnostics.json. Also capture a sanitized HAR from the browser DevTools Network tab and preserve the Console output showing the failed fetchApplianceNameToSiteIdList request.

I'd provide those files together with the exact UTC reproduction time, subscription/project details and screenshot to Azure Migrate support and ask them to investigate the backend call behind fetchApplianceNameToSiteIdList. There may be no Activity Log correlation ID because the failure occurs before Generate key initiates any resource operation. In this case, the failed network request and Portal session ID are more useful diagnostics than an ARM deployment correlation ID.

rgds,

Alex

Answer 2

Hi Akshat,

Since the Generate key button is disabled before you can submit anything, I would focus on the portal's appliance lookup rather than RBAC or the appliance name.

The MigrateV2-ApplianceListHelper-fetchApplianceNameToSiteIdList failure is happening during page initialization, so there is no deployment operation yet to generate an Activity Log correlation ID.

I would capture the failed request from Developer Tools > Network and check:

HTTP status code
Request URL
Response body
Any 403, 404, or 500 returned by the request

Also try signing out of Azure Portal completely and opening the project in an InPrivate window, then verify that the correct Azure Migrate tool and appliance type are selected.

Microsoft's documented appliance workflow does not provide a separate supported CLI command to bypass the portal and generate a key manually.

Given that you've reproduced this across multiple new projects, regions, and resource groups, while an older project in the same tenant worked, the failed ApplianceListHelper response is the most useful diagnostic evidence.

If that request is returning a service-side error, this will likely need Azure Migrate support/engineering rather than another RBAC or resource-provider change.