Power Platform Community Forum Thread Details

Hi Everyone,

We recently completed a migration where our email domain was changed and user licenses were moved as part of the transition. Although the migration has been completed, we are currently still using our old domain accounts for day-to-day operations.

Since the migration, we have been unable to register machines in Power Automate Desktop across all environments. Whenever we attempt to register a machine, we receive an error and the registration fails.

We raised a support ticket with Microsoft, and after their investigation they advised that the issue is related to a tenant mismatch. Their response was:

"The issue is occurring due to a tenant mismatch between the Azure Active Directory (Microsoft Entra ID) tenant of the machine and the tenant associated with the Power Automate environment."

Microsoft suggested that we work with our migration/implementation partner; however, we have not received any response from them so far.

We would appreciate any guidance on the following:

How can we identify which Microsoft Entra ID (Azure AD) tenant the machine is currently associated with?
How can we verify the tenant associated with our Power Automate environments?
What steps are required to configure the correct Azure AD / Microsoft Entra ID tenant after a domain migration?
Has anyone encountered a similar issue where machine registration failed due to a tenant mismatch?
Are there any recommended steps to reconnect or re-register machines with the correct tenant?

Any suggestions or troubleshooting steps would be greatly appreciated.

Thank you.

MachineRegistrati...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Automate Desktop

Hi @PS-20080655-0,

Microsoft is right on the diagnosis. Here's how to check and fix it.

Check machine's current tenant: run dsregcmd /status in command prompt, look for TenantId.

Check your Power Automate environment tenant: PPAC > environment > Settings, tenant ID is in the URL.

Fix: unjoin the machine from the old tenant (Settings > Accounts > Access work or school > Disconnect), re-join to the new tenant, then reinstall PAD and re-register.

If your machines are hybrid-joined (on-prem AD + Entra), AD Connect needs to point to the new tenant first — that's why Microsoft sent you to the migration partner, it's their responsibility to sort the AD sync side.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube