Teams error AADSTS65001: User or admin consent missing
Last verified against Microsoft Learn - Status codes from bot conversational APIs
DelegationDoesNotExist - The user or administrator hasn't consented to use the application with ID X. Send an interactive authorization request for this user and resource.What error AADSTS65001 means
This one belongs to user authentication, not to the bot's own credentials. When a Teams bot signs users in - through an OAuth connection on the Azure Bot resource or through single sign-on - it asks Entra for delegated permissions such as reading the user's profile. AADSTS65001 says nobody has agreed to that yet: "DelegationDoesNotExist - The user or administrator hasn't consented to use the application with ID X. Send an interactive authorization request for this user and resource."
The fix the message suggests is interactive consent: show the user a sign-in experience where they can approve the permissions. For SSO in Teams, Microsoft's troubleshooting guidance notes that consent-related failures are normally handled by the Teams client falling back to the OAuth card sign-in flow, so users get a sign-in button rather than an error.
Where users can't consent themselves, an administrator must. That happens when a scope requires admin consent, when tenant policy blocks user consent, or in cross-tenant setups: the Teams SDK SSO guide states that admin consent must be granted "in the tenant where the Teams app is installed, not just in the tenant where the app registration lives."
What it looks like
{
"error_description": "AADSTS65001: The user or administrator has not consented to use the application with ID '...' ...",
"error_codes": [65001]
}Why it happens
- The first sign-in for a user who has never approved the app's delegated permissions, with no interactive fallback.
- A permission that requires admin consent was added to the app registration but not granted.
- Tenant policy disables user consent for third-party apps.
- A multi-tenant auth app used in another tenant where no admin has consented.
How to fix Teams error AADSTS65001
- 1Make sure your bot sends an OAuth card (sign-in button) when silent token acquisition fails, so users can consent interactively.
- 2In the app registration, check API permissions and the Status column for each permission.
- 3Have an administrator grant admin consent for those permissions in the customer's own tenant (the one that installed the Teams app).
- 4Retry sign-in with the same user after consent is recorded.
How to stop it recurring
Request the fewest delegated scopes you need, and avoid admin-only scopes unless the feature depends on them. Publish an admin consent link and a list of permissions in your installation docs for customer tenants. Always keep the OAuth card fallback in your sign-in flow, since silent SSO can't show a consent prompt on its own.
Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.
Related codes
- authrequestfailed: SSO auth request failed after app installFailed to handle SSO auth request
- tokenmissing: SSO failed because Entra token acquisition failedAAD token acquisition failed.
- AADSTS50011: Redirect URI mismatch in bot sign-inInvalidReplyTo - The reply address is missing, misconfigured, or doesn't match…
- 403 NotEnoughPermissions: NotEnoughPermissions - operation requires rights the bot lacks*scenario specific
Error AADSTS65001 - quick answers
What does Teams error AADSTS65001 mean?
This one belongs to user authentication, not to the bot's own credentials. When a Teams bot signs users in - through an OAuth connection on the Azure Bot resource or through single sign-on - it asks Entra for delegated permissions such as reading the user's profile. AADSTS65001 says nobody has agreed to that yet: "DelegationDoesNotExist - The user or administrator hasn't consented to use the application with ID X.
How do I fix Teams error AADSTS65001?
1. Make sure your bot sends an OAuth card (sign-in button) when silent token acquisition fails, so users can consent interactively. 2. In the app registration, check API permissions and the Status column for each permission. 3. Have an administrator grant admin consent for those permissions in the customer's own tenant (the one that installed the Teams app). 4. Retry sign-in with the same user after consent is recorded.
Stop debugging Teams by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.