What causes AADSTS50169?

The authority URL points to a tenant ID or domain that doesn't exist in Microsoft Entra ID (Azure AD), e.g. a typo in the tenant GUID or a renamed domain. The federated domain (realm) was removed or is no longer verified on the tenant, so WS-Federation/SAML token requests can't be resolved. A Power BI dataset, dataflow or gateway was published from a tenant that's been migrated, merged or deleted, leaving a stale tenant reference. The app registration uses /common or /organizations but the user's home tenant doesn't trust the requested resource. ADF / Databricks linked service or service principal was created against the wrong tenant ID (cross-tenant misconfiguration)

How do I fix AADSTS50169?

Capture the exact authority/tenant used in the failing request (login.microsoftonline.com/{tenant}) — compare it to the verified tenant ID in Entra ID > Overview. In Entra ID > Custom domain names, confirm the realm/domain is present and Verified; re-add or re-verify it if it was removed. For Power BI: re-bind the dataset/dataflow credentials in the Power BI Service (Settings > Datasets > Data source credentials) under the correct tenant account, or republish from the right tenant. For ADF / Fabric / Databricks linked services: update the tenant ID on the service principal / managed identity configuration and rotate the secret if needed. If using a multi-tenant app registration, switch the authority from /common to the explicit tenant ID of the resource owner to avoid realm-resolution ambiguity

Low severityauthentication

Power BI Error:
AADSTS50169, realm not configured

What does this error mean?

Sign-in failed because the specified realm (tenant/domain) is not configured in the current Microsoft Entra ID service namespace.

Common causes

1The authority URL points to a tenant ID or domain that doesn't exist in Microsoft Entra ID (Azure AD), e.g. a typo in the tenant GUID or a renamed domain
2The federated domain (realm) was removed or is no longer verified on the tenant, so WS-Federation/SAML token requests can't be resolved
3A Power BI dataset, dataflow or gateway was published from a tenant that's been migrated, merged or deleted, leaving a stale tenant reference
4The app registration uses /common or /organizations but the user's home tenant doesn't trust the requested resource
5ADF / Databricks linked service or service principal was created against the wrong tenant ID (cross-tenant misconfiguration)

How to fix it

1Capture the exact authority/tenant used in the failing request (login.microsoftonline.com/{tenant}) — compare it to the verified tenant ID in Entra ID > Overview
2In Entra ID > Custom domain names, confirm the realm/domain is present and Verified; re-add or re-verify it if it was removed
3For Power BI: re-bind the dataset/dataflow credentials in the Power BI Service (Settings > Datasets > Data source credentials) under the correct tenant account, or republish from the right tenant
4For ADF / Fabric / Databricks linked services: update the tenant ID on the service principal / managed identity configuration and rotate the secret if needed
5If using a multi-tenant app registration, switch the authority from /common to the explicit tenant ID of the resource owner to avoid realm-resolution ambiguity

Frequently asked questions

What does AADSTS50169 mean?

The realm isn't a configured realm of the current service namespace.

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