What causes AADSTS700016?

Client ID in the Power BI / ADF / Fabric / Databricks connector config is mistyped or points to a deleted app registration. Authentication request is sent to the wrong tenant — e.g. `/common` or a tenant GUID that differs from where the app is actually registered. Multi-tenant app has never been consented to by an admin or user in the target tenant, so no service principal was provisioned. Service principal in the target tenant was deleted or disabled in Entra ID → Enterprise applications. Sign-in is attempted with a personal Microsoft account or B2B guest for an app that is not exposed to that account type

How do I fix AADSTS700016?

Open Microsoft Entra ID → App registrations and copy the Application (client) ID, then compare it character-for-character with the client ID configured in your Power BI dataset, ADF linked service, Fabric connection or Databricks SP. In the auth request / connection string, replace `/common` or any incorrect tenant GUID with the tenant ID where the app registration lives (Entra ID → Overview → Tenant ID). For a multi-tenant app used cross-tenant, have a Global Admin of the target tenant grant admin consent via `https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={client-id}` so a service principal is provisioned. In Entra ID → Enterprise applications of the target tenant, confirm the service principal for this client ID exists and is enabled — restore it from soft-delete or recreate it via consent if missing. If the app registration was recreated, update every consuming Power BI dataset, dataflow, ADF linked service and Databricks job with the new client ID and rotate the client secret

Low severityauthentication

Power BI Refresh Error:
AADSTS700016

What does this error mean?

The client ID in the auth request does not exist as a service principal in the target Microsoft Entra ID (Azure AD) tenant.

Common causes

1Client ID in the Power BI / ADF / Fabric / Databricks connector config is mistyped or points to a deleted app registration
2Authentication request is sent to the wrong tenant — e.g. `/common` or a tenant GUID that differs from where the app is actually registered
3Multi-tenant app has never been consented to by an admin or user in the target tenant, so no service principal was provisioned
4Service principal in the target tenant was deleted or disabled in Entra ID → Enterprise applications
5Sign-in is attempted with a personal Microsoft account or B2B guest for an app that is not exposed to that account type

How to fix it

1Open Microsoft Entra ID → App registrations and copy the Application (client) ID, then compare it character-for-character with the client ID configured in your Power BI dataset, ADF linked service, Fabric connection or Databricks SP
2In the auth request / connection string, replace `/common` or any incorrect tenant GUID with the tenant ID where the app registration lives (Entra ID → Overview → Tenant ID)
3For a multi-tenant app used cross-tenant, have a Global Admin of the target tenant grant admin consent via `https://login.microsoftonline.com/{tenant-id}/adminconsent?client_id={client-id}` so a service principal is provisioned
4In Entra ID → Enterprise applications of the target tenant, confirm the service principal for this client ID exists and is enabled — restore it from soft-delete or recreate it via consent if missing
5If the app registration was recreated, update every consuming Power BI dataset, dataflow, ADF linked service and Databricks job with the new client ID and rotate the client secret

Example log output

ActivityId: a3f8c21d-04bb-4e17-b9fc-2d6e0a1c5f38 | Status: Failed | Error: AADSTS700016: Application with identifier '9b3e4f2a-17dc-4c88-bd01-5f6a3e8c02d1' was not found in the directory 'contoso.onmicrosoft.com'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant.
RefreshType: Full | DatasetId: 8a1c3d9f-22ab-4f71-b604-3e5d7a0c9b12 | RefreshAttempt: 3/3 | FinalStatus: Disabled

Frequently asked questions

What does AADSTS700016 mean?

The application wasn't found in the directory/tenant. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might

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