Teams error tokenmissing: SSO failed because Entra token acquisition failed
Last verified against Microsoft Learn - Status codes from bot conversational APIs
AAD token acquisition failed.What error tokenmissing means
Teams tried to get a Microsoft Entra token for your bot's SSO and didn't get one. The failure code table documents tokenmissing as "AAD token acquisition failed" and marks it silent, so the user sees no error and sign-in quietly doesn't complete.
The documentation stops at that one line, so treat this code as "the token step failed" and check the inputs Teams needs to acquire it. Microsoft's cross-tenant notes explain the mechanism: "SSO requires the Teams client to silently acquire a token for the resource URI configured in webApplicationInfo.resource," in the context of the tenant where the app is installed. Anything that prevents that silent acquisition - a resource URI that doesn't resolve to your app registration, a missing scope or pre-authorization, or a tenant that can't reach a single-tenant auth app - is a reasonable suspect.
Microsoft notes separately that consent problems (userconsentrequired, interactionrequired) are handled by the Teams client through the OAuth card fallback and don't usually reach the bot, so tokenmissing points more at configuration than at a user who hasn't consented.
What it looks like
{
"type": "invoke",
"name": "signin/failure",
"value": {
"code": "tokenmissing",
"message": "..."
}
}Why it happens
- webApplicationInfo.resource in the manifest doesn't point at a valid Application ID URI.
- Expose an API lacks the access_as_user scope, or the Teams desktop and web clients aren't pre-authorized.
- The auth app is single-tenant but the Teams app is installed in another tenant.
- The manifest's webApplicationInfo.id doesn't match the app registration.
How to fix Teams error tokenmissing
- 1Register a signin/failure handler and log code, message, tenant, and conversation type.
- 2Walk the SSO checklist: Application ID URI, access_as_user scope, pre-authorized Teams clients, Token Exchange URL, webApplicationInfo.
- 3For cross-tenant installs, make the auth app multi-tenant and grant admin consent in the installing tenant.
- 4Re-upload the manifest after changes and retest with a fresh sign-in.
How to stop it recurring
Script your Entra and manifest SSO settings from one source of truth so they can't drift apart, and keep a test account in each tenant type you support. Because most SSO codes are silent, alert on any rise in signin/failure activities rather than waiting for users to report that sign-in "does nothing."
Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.
Related codes
- resourcematchfailed: SSO token exchange resource does not match the app ID URIResource match failed
- authrequestfailed: SSO auth request failed after app installFailed to handle SSO auth request
- installedappnotfound: SSO failed because the bot app is not installedThe bot app is not installed for the user or group chat.
- AADSTS65001: User or admin consent missingDelegationDoesNotExist - The user or administrator hasn't consented to use the…
Error tokenmissing - quick answers
What does Teams error tokenmissing mean?
Teams tried to get a Microsoft Entra token for your bot's SSO and didn't get one. The failure code table documents tokenmissing as "AAD token acquisition failed" and marks it silent, so the user sees no error and sign-in quietly doesn't complete. The documentation stops at that one line, so treat this code as "the token step failed" and check the inputs Teams needs to acquire it.
How do I fix Teams error tokenmissing?
1. Register a signin/failure handler and log code, message, tenant, and conversation type. 2. Walk the SSO checklist: Application ID URI, access_as_user scope, pre-authorized Teams clients, Token Exchange URL, webApplicationInfo. 3. For cross-tenant installs, make the auth app multi-tenant and grant admin consent in the installing tenant. 4. Re-upload the manifest after changes and retest with a fresh sign-in.
Stop debugging Teams by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.