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?
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.
Copilot Studio bot in Teams occasionally sends duplicate responses
I’m using a Copilot Studio bot deployed in Microsoft Teams, and I’m experiencing an intermittent issue where a single user message occasionally triggers two identical responses. This does not happen consistently, and there is no intentional duplicate logic in my bot design. I’m not sure whether this is caused by duplicate message delivery from Teams (e.g., retries or at-least-once delivery behavior), or something within Copilot Studio itself. Is this a known behavior for the Teams channel or Copilot Studio? Are there any recommended ways to detect or prevent duplicate responses at the bot level? Any insights or best practices would be appreciated.Copilot Studio in Teams sometimes wraps user input with HTML tags (e.g., <div>)
I’m using Copilot Studio deployed to Microsoft Teams, and I noticed that user messages are occasionally received with HTML tags. For example, when a user sends "get me the onboarding status", sometimes it displays in the dialog box as "<div>get me the onboarding status</div>" This does not happen consistently. I’m not sure whether this is caused by how Teams renders or sends messages (e.g., HTML vs plain text), or if it is something specific to Copilot Studio. Is this expected behavior for the Teams channel? Any clarification or recommended handling would be appreciated.
Teams Customer Connect: Now available globally in 26 languages
We're excited to announce that Customer Connect web chat in Microsoft Teams (previously called Live Chat) is now available globally, supporting 26 languages and bringing seamless customer engagement to businesses worldwide. For small and medium-sized businesses, every customer interaction matters. Whether someone discovers your business through a Google search, a social media post, or a friend's recommendation, the moment they land on your website is critical. With Customer Connect in Teams, you can now connect with these potential customers instantly no matter where your business is based in the world. A better way to connect with customers Your website is often the first-place potential customers interact with your business. When they have questions, waiting hours or days for an email response isn't ideal – neither for them nor for you. Customer Connect let you respond instantly to website visitors directly within Teams. No more switching tools. What's new with global availability With support for 26 languages, businesses can now provide customer support no matter where you operate. Whether you are based in Tokyo, São Paulo, or Berlin, you can set up Customer Connect to interact with customers in your preferred language. Supported languages Czech, Danish, German, English (Canada), English (United Kingdom), English (United States), Spanish (Chile), Spanish (Spain), Spanish (Mexico), French (Canada), French (France), Hungarian, Indonesian, Italian, Japanese, Korean, Norwegian Bokmål, Dutch, Polish, Portuguese (Brazil), Portuguese (Portugal), Swedish, Thai, Vietnamese, Chinese Simplified (China), Chinese Traditional (Taiwan) Key capabilities Simple setup Add the Customer Connect chat widget to your website in minutes. Configure your welcome message, set your availability, and you're ready to start conversations. Native Teams integration Chats appear alongside your regular Teams conversations. All customer interactions are automatically tracked and organized in Teams channels and Microsoft Lists, giving your team full visibility into every conversation. Customers can also book appointments directly with members of your team, making it easy to schedule follow-ups or provide high touch support. Getting started If you're already using Microsoft 365 Business, Customer Connect is included - no additional licensing required. To enable Customer Connect: Open the Admin app in Teams Configure your Customer Connect chat widget settings Add the chat widget to your website Start receiving and responding to customer chats in Teams Learn more Set up Customer Connect for your business Start a discussion with us Microsoft Teams - Small Business Community
Bot not receiving message events in shared channels (RSC)
Hi folks, Running into an issue with a bot in Microsoft Teams shared channels. I've configured RSC permissions to listen for new messages. This works as expected in standard channels - I receive events for every new message. However, in shared channels, the behavior is different: I only receive events when the bot is explicitly tagged Regular messages in the channel don’t trigger any events Permissions currently granted: Channel.ReadBasic.All (Application) ChannelMember.Read.All (Application) ChannelMessage.Read.All (Application) Has anyone faced this with shared channels? Is this expected behavior or am I missing something in setup? Thanks!
Add Teams Chat Member API call inexplicably Failing
I have tried every possible permutation of this API call that I can imagine. Nothing works. I already started a thread on this, but now it appears to be glitched and I can no longer reply to message sin that thread for some reason. What can I do to contact Microsoft Support and speak directly to their API team? The responses I have gotten all appear to be AI generated and NONE ARE CORRECT. I really need help, from a human, that actually might understand what's going on here. Please help. "#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation." <- I am receiving this error despite the fact that we already have several users in this channel with that same type. This API call is intended to invite a user to an existing group chat. This should really be a very simple thing. 1. ALL users in the group chat already have type = '#microsoft.graph.aadUserConversationMember' so the error message doesn't even make sense. 2. This IS a Group chat. NOT a channel. NOT a one on one chat. 3. The Inviter has permission to invite users to this groupchat through the frontend. (and in fact can do so using the frontend.) Why is this API call failing? I have tried scrubbing the API call of special characters, I have tried using the beta endpoint, I have tried several different formats for the input. ERROR: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-02-10T19:11:28","request-id":"XXXXX","client-request-id":"XXXXXX"}}} POST URL: https://graph.microsoft.com/v1.0/chats/IDHERE/members BODY: { "chatType": "group", "\u0040odata.type": "#microsoft.graph.aadUserConversationMember", "user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/IDHERE", "roles": [] }Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing. Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember' To get the basic questions out of the way.... Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.) Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel. Yes, I have tried both the beta and stable channel; each gives the same error message. Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.) No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel. I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance. POST to URL: https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members BODY: { "@odXXX.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]" } ERROR MESSAGE: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
