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
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>"}}}
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!
How do I send a message to myself with PowerAutomate?
I am developing a PowerAutomate flow, I want to use the function "post message in chat or channel", I can send messages to anyone in "one to one" private chats but not on the private chat I have with myself. Has somebody found a way to message himself via power automate? I can't create it as a "new chat" in PA because it says users cannot be duplicate. Then I figured out I had to find the ID of the chat with myself. I tried using the microsoft graph api to retrieve the id from "me/chats" but the chat with myself is not shown. I tried many different filters and expansions with no success. I also tried analyzing the id itself and discovered that, in the case of "one to one" chats, it's made of {the sender id} and {the receiver id} I then tried constructing an id that contains 19:{myuserid}_{myuserid}@{domain} but it responds that there is no record. I tried many combinations, thanks for the help.
App Validation Issue - Bot must send a proactive welcome message in personal scope
I'm working on a bot application for MS Teams using the Python SDK and encountered a challenge with app validation and the proactive welcome message requirement. What Happened: Initially, our bot handled the welcome message through on_installation_update, but app validation failed with the error: "Bot must send a proactive welcome message in personal scope." To satisfy validation, we added on_members_added_activity to send the welcome message for personal scope, which resolved the validation error. However, this created a new problem: on_members_added_activity is being triggered when we call the Graph API to query chats or users: {graph_url}/me/chats $filter=chatType eq 'oneOnOne' and installedApps/any(a:a/teamsApp/id eq '{teams_app_id}') {graph_url}/users/{user_id}/chats $filter=chatType eq 'oneOnOne' and installedApps/any(a:a/teamsApp/id eq '{teams_app_id}') According to a Stack Overflow discussion (https://stackoverflow.com/questions/57496329/proactive-messaging-bot-in-teams-without-mentioning-the-bot-beforehand), this appears to be a known issue: calling this API triggers a conversation update event even though there were no actual updates, resulting in duplicate events and duplicate welcome messages. Questions: What is the official/recommended way to handle known issue: calling this API triggers a conversation update event? Whats the recommended way to read personal chat history of a user? Should we be using a different approach for this app validation requirement? Any guidance or pointers to official documentation would be greatly appreciated!
