Forum Discussion

jortizflores's avatar
jortizflores
Icon for Microsoft rankMicrosoft
Sep 02, 2026

Teams Personal Bot Identity Cache issue

Hi all — looking for guidance on a Teams custom app + bot naming issue.

We have a custom Teams app with a bot. The app catalog/admin/dev portal surfaces show the correct app name, and the manifest + Azure Bot configuration appear correctly aligned, but the Teams personal chat surfaces still show the old/wrong bot name.

What looks correct:

  • Teams app manifest name.short / name.full have the correct app name
  • Manifest bots[0].botId points to the expected bot ID
  • Azure Bot resource → Configuration → Microsoft App ID matches that bot ID
  • Azure Bot resource → Bot profile display name has the correct name
  • Teams Developer Portal basic information shows the correct name
  • Teams Admin Center shows the correct app short name

What is still wrong:

  • Teams left sidebar chat name shows the old/wrong name
  • Chat top header shows the old/wrong name
  • Inline bot sender/name in the conversation shows the old/wrong name
  • The issue reproduces for multiple users
  • It persists after sign out/sign in, uninstall/reinstall, republish, and retesting

We may also be seeing a package/version propagation issue: after publishing an updated app package with a newer manifest version, Teams Admin Center still appears to show the previous version.

Has anyone seen this before with personal bot apps? Specifically trying to understand:

  1. What is the authoritative source for the personal bot chat roster/header/sender display name?
Chat
microsoft teams

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Sep 04, 2026

    The correct manifest but old personal-chat name suggests Teams has an old app definition or cached installation; Bot Framework identity does not control every label. Microsoft documents manifest short name as the app name shown to users; bot and Teams app definition are separate objects. First, download the exact package shown in Teams Admin Center and verify its manifest version, app ID, bot ID, and name values before republishing; do not rely only on the local build folder. Confirm the newer package is approved and available in the target tenant. Then remove the personal installation for one test user, install the published package again, and compare with a fresh test account. If the old name remains across clean installations, collect the app ID, bot Microsoft App ID, package version, tenant, timestamps, and screenshots, then open a Microsoft support case. There is no documented switch guaranteeing immediate replacement of cached personal-chat labels.