Forum Widgets
Latest Discussions
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: What is the authoritative source for the personal bot chat roster/header/sender display name?
Unable to submit Teams app update
Hello, We have been attempting to submit an update to our Teams app, but we’re experiencing an issue with the submission process. When we click “+ Submit app update,” the loader appears for a few seconds, but then nothing happens. No error message is displayed, and the app update is not submitted. I’ve attached a short video demonstrating the issue. Could you please advise on how we can resolve this? Thank you for your help.
Workflows - Posting a Card
I'm in the process of migrating our Jira integration with teams from using the soon to be deprecated Connectors, to Workflows. I have two problems that I can't see to overcome. 1. All the messages are posted as '[My Name] via Workflows posted a new message'. Is there any way the message can come from another user or no user? 2. The preview for the messages (in the notification popup and Activity screen) is 'Card', instead of anything useful. Together this makes the notifications not very useful. What I have done: The workflow is set up And what is being posted to the webhook is (for example). { "type": "message", "attachments": [{ "contentType": "application/vnd.microsoft.card.adaptive", "contentUrl": null, "content": { "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [{ "type": "ColumnSet", "columns": [{ "type": "Column", "width": "auto", "items": [{ "type": "Image", "url": "https://i.imgur.com/FrVumxY.png", "size": "Medium" } ] }, { "type": "Column", "width": "stretch", "verticalContentAlignment": "Center", "items": [{ "type": "TextBlock", "size": "Medium", "weight": "Bolder", "text": "Component Missing [ADP-xxx]" } ] } ] }, { "type": "TextBlock", "text": "Initiator: ", "wrap": true }, { "type": "TextBlock", "text": "ADP-xxx: Fixing reset password validation", "wrap": true, "weight": "Bolder", "color": "Accent", }, { "type": "TextBlock", "text": "Status: QA Ready", "wrap": true }, { "type": "TextBlock", "text": "Type: Bug", "wrap": true }, { "type": "TextBlock", "text": "Assignee: ", "wrap": true } ], "actions": [{ "type": "Action.OpenUrl", "title": "Open in Jira", "url": "https://xxx.atlassian.net/browse/ADP-xxx" } ], "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4" } } ] } I have tried posting various different combinations of summary attributes with no effect. Is there a whole better way of doing this, or is there a few tweaks I can make?
Make an alert icon of new messages from other accounts/Orgs on top right in TEAMs
The icon of activity in other accounts and orgs moved to bottom left sucks, user would easily miss noticing new messages from other accounts/org. It's better to keep an alert icon next to user icon on top right for easier notification.
App Validation failing for no clear reason
We're trying to get our (very simple) Teams App listed on the app store, but during the App Validation we keep getting the same error: "Unable to upload the manifest.zip file in MS Teams." as seen below: Downloading the report doesn't give any more information, it only lists the only successful validation step ("BotID should be registered") and the error doesn't appear there. I've validated the manifest.json file against the schema, tried reuploading the same manifest to a different org (creating a new app and bot) - validation fails there too. Does anyone have any pointers? Here is my (anonymized) manifest file: { "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json", "manifestVersion": "1.19", "version": "1.1.1", "id": "[redacted]", "developer": { "name": "[redacted]", "websiteUrl": "https://www.[redacted].com", "privacyUrl": "[redacted]", "termsOfUseUrl": "[redacted]" }, "icons": { "color": "color.png", "outline": "outline.png" }, "name": { "short": "[redacted]", "full": "[redacted]" }, "description": { "short": "[redacted]", "full": "[redacted]" }, "accentColor": "#4A3AFF", "bots": [ { "botId": "[redacted]", "scopes": ["personal"], "supportsFiles": false, "isNotificationOnly": false, "commandLists": [ { "scopes": ["personal"], "commands": [ { "title": "help", "description": "Show what this bot does and how to connect your account" }, { "title": "connect", "description": "Get a fresh link to (re-)connect your account" } ] } ] } ], "staticTabs": [ { "entityId": "conversations", "scopes": ["personal"] }, { "entityId": "about", "scopes": ["personal"] } ], "permissions": ["identity", "messageTeamMembers"], "validDomains": ["app.[redacted].com", "auth.[redacted].com"] }TeamsTab.ReadWriteSelfForTeam: deleting a tab fails with 400 "appId cannot be null or whitespace"
We have a published Teams app that pins a configurable tab into a team channel via Microsoft Graph and removes it again when the user uninstalls our app from that channel. Creating the tab works. Deleting it always fails with a 400 that looks like an unhandled null-argument exception inside the Graph Teams service rather than a permission problem. I reported this in October 2025 as https://github.com/MicrosoftDocs/msteams-docs/issues/13432, but that is a documentation repository and the issue has had no response, so I am reposting here, as we can still reproduce the issue. We're using a delegated token for the operation. The only tab-related scopes are `TeamsTab.Read.All` (read-only) and `TeamsTab.ReadWriteSelfForTeam`. According to the docs (https://learn.microsoft.com/en-us/graph/api/channel-delete-tabs), `TeamsTab.ReadWriteSelfForTeam` is the **least privileged** delegated permission for the delete, so the token should be ok. What works Creating the tab, with the same delegated user token: POST https://graph.microsoft.com/v1.0/teams/«teamId»/channels/«channelId»/tabs Content-Type: application/json { "displayName": "«AppName»", "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/«teamsAppId»", "configuration": { "entityId": "«entityId»", "contentUrl": "https://«ourhost»/teams/tabs/channel/«entityId»", "websiteUrl": "https://«ourhost»/app/tickets?channel=«entityId»", "removeUrl": "https://«ourhost»/teams/remove-tab/«entityId»" } } → `201 Created`. The tab appears in the channel and renders correctly. Listing the tabs afterwards also works and returns our tab together with its `id`: GET https://graph.microsoft.com/v1.0/teams/«teamId»/channels/«channelId»/tabs?$expand=teamsApp Works as well and lists our tab. Might be served by the TeamsTab.Read.All permission. What fails DELETE https://graph.microsoft.com/v1.0/teams/«teamId»/channels/«channelId»/tabs/«tabId» → `400 Bad Request` { "error":{ "code":"BadRequest", "message":"appId cannot be null or whitespace. (Parameter 'appId')", "innerError":{ "date":"2026-07-27T13:45:31", "request-id":"f930c847-0b48-4a46-b17e-f0ee10ff8177", "client-request-id":"f930c847-0b48-4a46-b17e-f0ee10ff8177" } } } (leaving in the error details, maybe that helps diagnosing the issue) appID is not even part of the request, it's probably resolved against the TeamsTab.ReadWriteSelfForTeam permission on your side. Let me know if you need any more details.CS agent OK in M365 Copilot; Teams chat silent / no Studio session
We are troubleshooting a Copilot Studio agent that works correctly in Microsoft 365 Copilot and in the Copilot Studio test surface, but does not receive inbound activities from Microsoft Teams personal chat. Environment and evidence: - Agent: Copilot Studio agent (custom business assistant) - Copilot Studio agent ID: 88901b10-… (truncated) - Teams/Entra app ID: 7e4a53cc-… (truncated) - Manifest version: 1.0.8 - Channel configuration: Microsoft 365 Copilot + Microsoft Teams - Publish: Succeeded / Channel state: Synchronized - Agent Registry: Available - Authentication: Integrated / Tool credentials: Maker-provided - MCP/custom connector runtime: working (Studio tool test HTTP 200) - Microsoft 365 Copilot routing: working Failure specific to Teams: - Messages in Teams web and desktop appear delivered in the agent personal chat - Agent never replies - Studio monitor has M365 Copilot sessions, but no Teams session for those timestamps - Teams Admin Center Manage apps returns 0 results by name or exact app ID despite Agent Registry Available - Intentionally not republishing / reconnecting OAuth / rewiring connectors because M365 Copilot path proves the same agent+connection works Classification: FAIL — Teams inbound activity is not reaching the Copilot Studio agent. Questions focused on Teams delivery: 1. Why would Teams personal 1:1 messages never create a Studio conversation while M365 Copilot does? 2. Is a missing TAC Manage apps row expected under Unified App Management when Registry shows Available? 3. Known gaps: Agent Registry Available + channel Synchronized, but Teams client chat bound to a non-runtime endpoint? 4. Best diagnostic if Monitor shows 0 Teams sessions after a confirmed client send? Looking for production experience / documented workaround. Redacted evidence available; no tokens/secrets.
