How to Fix AADSTS700016: Application not found in the directory
Error message
AADSTS700016: Application with identifier '<id>' was not found in the directory '<tenant>'.
If you're seeing "AADSTS700016: Application not found in the directory", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
The token endpoint cannot find the app registration matching the client ID you sent in the tenant you're authenticating against.
Why this happens
Wrong client ID, the app exists in a different tenant, the app was deleted, or a multi-tenant app hasn't been provisioned (consented) into the user's home tenant yet.
Step-by-step fix
Confirm the client ID matches the App registration's Application (client) ID exactly.
Confirm you're hitting the correct tenant in the authority URL (the tenant where the app is registered, or `common` for multi-tenant apps).
For multi-tenant apps, an admin in the customer tenant must consent once so the service principal is created there.
Affected products
Entra ID
Still broken? Try these
- Search Entra → App registrations and Enterprise applications for the ID — they're separate objects.
- If you recently rotated the app, check that no automation is still using the old client ID.
- If using B2C, confirm you're using the B2C-specific authority and policy.
Related errors
Frequently asked questions
What does "AADSTS700016: Application not found in the directory" mean?
The token endpoint cannot find the app registration matching the client ID you sent in the tenant you're authenticating against.
What causes "AADSTS700016: Application not found in the directory"?
Wrong client ID, the app exists in a different tenant, the app was deleted, or a multi-tenant app hasn't been provisioned (consented) into the user's home tenant yet.
How do I fix "AADSTS700016: Application not found in the directory"?
1. Confirm the client ID matches the App registration's Application (client) ID exactly. 2. Confirm you're hitting the correct tenant in the authority URL (the tenant where the app is registered, or `common` for multi-tenant apps). 3. For multi-tenant apps, an admin in the customer tenant must consent once so the service principal is created there. Always test changes in a non-production environment first.
Browse more errors in Entra ID: Fix Microsoft Entra ID (Azure AD) errors. AADSTS error codes, admin consent, app role assignment, Conditional Access, and user lookup problems. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.