Medium severityauthentication
Power BI Error:
AADSTS700011, Application not found in tenant
What does this error mean?
The client application ID used during sign-in does not exist in the Microsoft Entra ID (Azure AD) tenant being signed into.
Common causes
- 1App registration only exists in the home tenant and is not configured as multi-tenant, while a guest or external user signs in from a different tenant
- 2Admin consent / service principal provisioning in the resource tenant has never been performed, so no enterprise application object exists there
- 3Wrong client_id used in the connection string, OAuth config or Power BI custom connector (typo, dev vs. prod app swapped)
- 4Sign-in goes to the wrong authority — using /common or the user's home tenant instead of the tenant where the app is registered (or vice versa)
- 5The app registration was deleted, soft-deleted or recreated with a new Application (client) ID after the integration was set up
How to fix it
- 1Verify the exact Application (client) ID in the error against App registrations in Microsoft Entra ID (portal.azure.com → Entra ID → App registrations → All applications) — confirm it exists and is not soft-deleted
- 2If users from other tenants must sign in (guests, customers, partners), set the app registration's 'Supported account types' to multi-tenant and re-consent
- 3In the resource/sign-in tenant, grant admin consent via https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={app-id} so the service principal is provisioned as an Enterprise Application
- 4Check the authority URL in your client (Power BI Service Principal, ADF Linked Service, Databricks SCIM/SP, custom app): use https://login.microsoftonline.com/{tenant-id} matching the tenant where the app lives, not /common or /organizations unless the app is multi-tenant
- 5If the app was recreated, update every consumer (Power BI dataset credentials, ADF linked services, Fabric connections, Key Vault secrets) with the new client ID and secret/certificate