Low severityauthentication
Power BI Error:
AADSTS50160
What does this error mean?
Microsoft Entra ID (Azure AD) routed the sign-in to a tenant that doesn't match the one preferred for this account.
Common causes
- 1Personal Microsoft account (MSA) is signing in against a work/school-only authority (e.g. /organizations or a specific tenant ID)
- 2Work/school account is hitting a /consumers endpoint instead of /common or /organizations
- 3Application is configured with a hardcoded tenant ID in the authority URL that differs from the user's home tenant
- 4Guest/B2B user is being routed to the resource tenant while their home tenant is preferred for this flow
- 5Power BI / Fabric / ADF service principal or OAuth connection was registered in a different Entra ID tenant than the one being signed into
How to fix it
- 1Verify which authority endpoint the application uses: /common (any account), /organizations (work/school only), /consumers (MSA only), or /{tenantId} — and align it with the account type that needs to sign in
- 2If you're connecting Power BI / Fabric / ADF to a data source, sign out completely (Power BI Desktop: File → Account → Sign out; browser: clear login.microsoftonline.com cookies) and sign back in with the correct work account
- 3For Power BI Gateway or ADF linked services, re-authenticate the OAuth credential using an account that lives in the same tenant the connector was registered against
- 4If you administer the Entra ID app registration, check Authentication → Supported account types and confirm it matches the audience you actually want (single tenant vs multi-tenant vs personal accounts)
- 5If the user is a guest/B2B in your tenant, ask them to sign in via https://login.microsoftonline.com/{your-tenant-id} explicitly so Entra routes them to the correct tenant