Teams error authrequestfailed: SSO auth request failed after app install
Last verified against Microsoft Learn - Status codes from bot conversational APIs
Failed to handle SSO auth requestWhat error authrequestfailed means
Teams started SSO, but the auth request itself failed. The failure code table defines authrequestfailed as "The SSO auth request failed after app installation," and unlike most SSO codes it is not silent: it occurs in the group chat SSO flow, where the user is shown an install or auth card. The default SDK log reads authrequestfailed -- Failed to handle SSO auth request.
Microsoft ties it mainly to cross-tenant setups, where the Teams app is installed in one tenant and the Entra auth app lives in another. Two causes are named: no admin consent in the Teams app's tenant - "Even if the auth app is multi-tenant (AzureADMultipleOrgs), admin consent must be granted in the tenant where the Teams app is sideloaded/installed" - and a user identity mismatch, such as a dev-tenant Teams user hitting an auth app that expects production users.
When it happens, Teams falls back to the OAuth card sign-in flow. If the account that signs in through that popup differs from the Teams user, the popup shows a 6-digit magic code, which Microsoft describes as expected behavior rather than a bug.
What it looks like
// Default SDK log line
Sign-in failed for user "..." in conversation "...": authrequestfailed -- Failed to handle SSO auth requestWhy it happens
- Admin consent for the auth app hasn't been granted in the tenant where the Teams app is installed.
- The auth app's signInAudience isn't AzureADMultipleOrgs in a cross-tenant setup.
- The Teams user belongs to a different tenant than the auth app expects.
- Testing with a dev tenant against production auth configuration.
How to fix Teams error authrequestfailed
- 1Grant admin consent for the auth app in the tenant where the Teams app is installed.
- 2Or install the Teams app in the same tenant as the auth app registration.
- 3For cross-tenant use, set the auth app's signInAudience to AzureADMultipleOrgs.
- 4Test with an account from the expected tenant and confirm the signin event fires without falling back.
How to stop it recurring
Decide early whether your auth app serves one tenant or many, and build admin consent into onboarding for every customer tenant. Keep dev and production auth apps separate and test SSO in each with accounts from the matching tenant, so identity mismatches don't reach users as magic codes.
Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.
Related codes
- AADSTS65001: User or admin consent missingDelegationDoesNotExist - The user or administrator hasn't consented to use the…
- installedappnotfound: SSO failed because the bot app is not installedThe bot app is not installed for the user or group chat.
- tokenmissing: SSO failed because Entra token acquisition failedAAD token acquisition failed.
- 401 Unauthorized (tenant mismatch): Single-tenant vs multi-tenant mismatchAADSTS700016: The application wasn't found in the directory/tenant.
Error authrequestfailed - quick answers
What does Teams error authrequestfailed mean?
Teams started SSO, but the auth request itself failed. The failure code table defines authrequestfailed as "The SSO auth request failed after app installation," and unlike most SSO codes it is not silent: it occurs in the group chat SSO flow, where the user is shown an install or auth card. The default SDK log reads authrequestfailed -- Failed to handle SSO auth request .
How do I fix Teams error authrequestfailed?
1. Grant admin consent for the auth app in the tenant where the Teams app is installed. 2. Or install the Teams app in the same tenant as the auth app registration. 3. For cross-tenant use, set the auth app's signInAudience to AzureADMultipleOrgs. 4. Test with an account from the expected tenant and confirm the signin event fires without falling back.
Stop debugging Teams by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.