Forum Discussion
jortizflores
Microsoft
Sep 02, 2026Teams 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:
- What is the authoritative source for the personal bot chat roster/header/sender display name?
No RepliesBe the first to reply