MetricSign
Start free
Low severityauthentication

Power BI Error:
AADSTS90125, User Not Found in Tenant

What does this error mean?

Azure AD/Entra ID can't find the signed-in user account in the target tenant during a debug-mode enrollment flow.

Common causes

  • 1Typo in the User Principal Name (UPN) or email address entered at the login prompt
  • 2User exists in a different Entra ID (Azure AD) tenant than the one resolved by the sign-in (e.g. personal MSA vs. work account)
  • 3Guest/B2B user was never actually invited or accepted the invitation in the target tenant
  • 4Account was deleted or soft-deleted in Entra ID but the user still has cached credentials
  • 5Wrong tenant ID/domain in the authority URL of a Power BI, ADF or Fabric connection string

How to fix it

  1. 1Verify the exact UPN in the Entra admin center (entra.microsoft.com → Users) — match casing and domain suffix to what you typed at the prompt
  2. 2Confirm you're authenticating against the correct tenant: check the `tenantId` or `authority` in your Power BI dataset, ADF linked service, or Fabric connection — not the tenant the user actually lives in
  3. 3If it's a guest user, re-send the B2B invite from Entra ID → External Identities and have the user accept before retrying the sign-in
  4. 4Clear cached Microsoft credentials (Windows Credential Manager → Generic Credentials → remove `MicrosoftOffice*` / `OneDrive*` entries) and sign in fresh
  5. 5If a service principal or managed identity is failing with this code, recreate it in the target tenant — a deleted SPN won't auto-restore

Frequently asked questions

What does AADSTS90125 mean?

DebugModeEnrollTenantNotFou

How do I fix this error?

Check your application registration, token configuration, and user permissions in the Azure portal. Review Conditional Access policies if the error is policy-related.

Source · learn.microsoft.com/en-us/entra/identity-platform/reference-error-codes#aadsts-error-codes

Other authentication errors