Microsoft Teams Bot Framework · error code

Teams error installedappnotfound: SSO failed because the bot app is not installed

ConfigurationAuthentication & identity

Last verified against Microsoft Learn - Status codes from bot conversational APIs

What Teams returns
The bot app is not installed for the user or group chat.

What error installedappnotfound means

Teams couldn't run SSO for your bot because, from its point of view, the app isn't installed where the sign-in is happening. Microsoft's SSO failure code table lists installedappnotfound as "The bot app is not installed for the user or group chat," marks it silent, and calls it the most common SSO failure.

Silent failures produce no feedback in the Teams client - sign-in simply doesn't complete - so you only learn about it from the signin/failure invoke your bot receives. The installation context matters: SSO runs in the context of where the app is installed, and a bot that is reachable in one place (say, a team) isn't automatically installed for the individual user or the group chat where it is asking them to sign in. The group chat SSO flow even has a separate failure code, installappfailed, for the case where Teams tries to install the app in the user's personal scope and can't.

This code is about installation, not about Entra configuration. If the identifiers were wrong you would see resourcematchfailed instead.

What it looks like

{
  "type": "invoke",
  "name": "signin/failure",
  "value": {
    "code": "installedappnotfound",
    "message": "..."
  }
}

Why it happens

  • The user signs in from a context where the app hasn't been installed for them.
  • The app was uninstalled or blocked for the user or chat after the conversation started.
  • A sideloaded development build is installed under a different app ID than the one the bot's manifest uses in production.
  • Policy prevents the app from being installed for this user.

How to fix Teams error installedappnotfound

  1. 1Log the signin/failure activity's code, conversation type, and conversation ID to see where it happens.
  2. 2Install the app for the user (personal scope) or in the group chat, then retry sign-in.
  3. 3Check that the app ID in the installed package matches the bot you are running.
  4. 4If an admin blocked the app, resolve that first - sends will also fail with BotDisabledByAdmin.

How to stop it recurring

Ask for sign-in only in contexts where you know the app is installed for that user, and track installs with installationUpdate events. Keep one app ID per environment and don't mix dev and production packages in the same tenant. Logging every signin/failure turns this silent failure into a metric you can watch.

Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.

Related codes

Error installedappnotfound - quick answers

What does Teams error installedappnotfound mean?

Teams couldn't run SSO for your bot because, from its point of view, the app isn't installed where the sign-in is happening. Microsoft's SSO failure code table lists installedappnotfound as "The bot app is not installed for the user or group chat," marks it silent, and calls it the most common SSO failure.

How do I fix Teams error installedappnotfound?

1. Log the signin/failure activity's code, conversation type, and conversation ID to see where it happens. 2. Install the app for the user (personal scope) or in the group chat, then retry sign-in. 3. Check that the app ID in the installed package matches the bot you are running. 4. If an admin blocked the app, resolve that first - sends will also fail with BotDisabledByAdmin.

Stop debugging Teams by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.