Teams Personal Bot Identity Cache issue

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.