Forum Discussion

YashikaAgrawal's avatar
YashikaAgrawal
Icon for Advocate V rankAdvocate V
13 hours ago

User migrated issue

Hi,

I have a user Anil, we are migrating from tenant Infy to TCS.

Migration done for the user Anil.

apps.powerbi.com - Anil is able to login to old tenant and do SWITCH tenant -- all is working fine.

But in Power BI desktop, he is able to login with old credentials, but with new credentials he is getting below error.

Error: "We couldn't sign in with passkey. Please try again" Learn more at aka.ms/passkeys

When we use passkeys its giving error "AADSTS50197- sorry we could not find user, please sign it again".

Any help please.

Thanks,

Need Help

3 Replies

  • MFelix's avatar
    MFelix
    Icon for Super User rankSuper User
    11 hours ago

    Hi YashikaAgrawal​ ,

     

    In Power BI desktop to Change to another tenant you need to select the others options button that appears velow the user name on the login pop up. Then insert the tenant name you want to login and after that user name and password.

    • YashikaAgrawal's avatar
      YashikaAgrawal
      Icon for Advocate V rankAdvocate V
      6 hours ago

      Thank you for reply, "sign in with different account", are you referring to this.

      • ShivekMaharaj's avatar
        ShivekMaharaj
        Icon for Memorable Member rankMemorable Member
        32 minutes ago

        Hi YashikaAgrawal​,

        Yes, the "Sign in with a different account" option in your screenshot is the option MFelix​ was referring to.

        However, I would also investigate the AADSTS50197 error itself before treating this as only a Power BI Desktop account-selection issue.

        Microsoft defines AADSTS50197 as ConflictingIdentities - essentially, Microsoft Entra could not resolve the user during that authentication attempt.

        Since this user has been migrated between tenants, I would first ask the Entra administrator to confirm that the new Anil account exists as the expected identity in the TCS tenant and that the required Power BI/Fabric license and permissions have been assigned to that new identity.

        This is particularly important with a cross-tenant migration because Microsoft documents that users in the source and target tenants have different object IDs, even when the usernames appear similar. The identities and permissions therefore need to be mapped to the target tenant rather than assuming the original identity carries across automatically. Microsoft's Power BI tenant migration guidance covers this distinction.

        I would then reproduce the Desktop sign-in failure and have the administrator check the corresponding Microsoft Entra sign-in log. In a cross-tenant scenario, that log shows both the home tenant and resource tenant, together with the application and actual failure reason.

        That should tell you whether Power BI Desktop is still attempting authentication using an old tenant/account context or whether the new target-tenant identity itself is not being resolved correctly.

        If the new identity is confirmed as correct in Entra, I would then sign out of Power BI Desktop completely, restart it, select "Sign in with a different account", and explicitly authenticate with the new work account.

        I would avoid changing or deleting the user's Windows work/school account configuration until the Entra sign-in log confirms where the failure is occurring, especially if this is a corporate-managed device.

        AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.