High severityauthentication
Power BI Error:
AADSTS50049, Unknown or invalid tenant instance
What does this error mean?
The authority URL points to a tenant or cloud instance that Microsoft Entra ID (Azure AD) does not recognize.
Common causes
- 1Typo or wrong tenant ID/domain in the authority URL (e.g. login.microsoftonline.com/<tenant>)
- 2Using the wrong sovereign cloud endpoint — e.g. login.microsoftonline.com for a tenant that lives in US Gov (login.microsoftonline.us), China (login.partner.microsoftonline.cn) or Germany
- 3Tenant has been deleted, renamed, or the verified domain was removed
- 4Hardcoded 'common' / 'organizations' / 'consumers' endpoint while the app or gateway requires a specific tenant GUID
- 5Power BI / ADF / Fabric data source configured with a stale tenant after a tenant migration or cross-tenant move
How to fix it
- 1Verify the tenant ID or primary domain in the Microsoft Entra admin center (entra.microsoft.com → Overview) and compare it character-for-character with the authority URL used by the client, gateway, or linked service
- 2Confirm you are hitting the correct cloud instance: commercial uses login.microsoftonline.com, US Gov uses login.microsoftonline.us, China (21Vianet) uses login.partner.microsoftonline.cn — update the authority accordingly
- 3In the failing component, replace any hardcoded /common, /organizations or /consumers authority with the explicit tenant GUID when the resource is single-tenant (Power BI Embedded, ADF linked services, Databricks SCIM, custom apps using MSAL)
- 4For Power BI on-premises data gateway or Fabric capacity issues, re-sign-in the data source owner so the gateway re-discovers the tenant; for ADF / Synapse, edit the linked service and re-enter credentials against the correct tenant
- 5If the tenant was recently migrated or merged, update the app registration's Supported account types and reply URLs, and have admins re-consent against the new tenant