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.
Custom App (Static Tab) with SharePoint URL stays blank on first load in Teams Desktop Client
Hello Teams Developer Community, We have deployed a custom Teams app (v1.25) that uses a Static Tab to display our company's SharePoint intranet portal. The contentUrl and websiteUrl point to our SharePoint site. [The Issue] When a user clicks the app for the very first time in the Teams Desktop Client (New Teams), the screen remains completely blank (white loading screen). However, if the user clicks away to another app (like Chat or Teams) and then clicks back to our custom app, the SharePoint page loads perfectly. [Observations] This issue does NOT happen on Teams Web Client (browser). It loads instantly there. Clearing the Teams Desktop cache does not solve the problem. It seems to be related to WebView2 authentication/SSO redirect loops inside the iframe. I tried adding "showLoadingIndicator": true in Developer Portal, but the schema automatically strips it out upon saving. [Question] Is there a specific parameter we need to append to the SharePoint URL, or specific domains we must add to "validDomains", to prevent this initial blank screen caused by auth delays in the Desktop Client? Any guidance on handling this WebView2 rendering delay would be greatly appreciated. Thank you.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.
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>"}}}
Web Notifications API from Personal Tab app doesn't work
I have a client-side web application that we're trying to get to run as a Teams personal tab app. I have the app working as a teams app, as long as we "open in new window" so that the app doesn't get put to sleep as it needs a permanently up session with something else. Our app uses Web Notifications API (https://developer.mozilla.org/en-US/docs/Web/API/Notification) to create desktop notificiations, but this does not seem to work when running as a Teams tab app popped out into a new window. No notifications are displayed. Permissions have been requested correctly and given and Windows is set to allow notifications, but these web notifications never make it out of teams to the desktop. There are no errors in the browser console to say the web notifications are not supported in Teams. Is this not supported as a teams app? The inbuilt activity feed is useless for our purpose (for a few reasons), so please don't suggest I use graph to make use of that instead.
[Adaptive Card] Issue with rendering images and ToggleVisibility
I am using a simple accordion style adaptive card with a collapsible section: { "type": "AdaptiveCard", "$schema": "https://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "Container", "items": [ { "type": "ColumnSet", "columns": [ { "type": "Column", "items": [ { "type": "TextBlock", "text": "Title", "wrap": true, "size": "Medium" } ], "width": "stretch" }, { "type": "Column", "id": "chevronDown", "spacing": "Small", "verticalContentAlignment": "Center", "items": [ { "type": "Image", "url": "https://adaptivecards.io/content/down.png", "width": "20px", "altText": "collapsed" } ], "width": "auto" }, { "type": "Column", "id": "chevronUp", "spacing": "Small", "verticalContentAlignment": "Center", "items": [ { "type": "Image", "url": "https://adaptivecards.io/content/up.png", "width": "20px", "altText": "expanded" } ], "width": "auto", "isVisible": false } ], "selectAction": { "type": "Action.ToggleVisibility", "targetElements": [ "cardContent", "chevronUp", "chevronDown" ] } }, { "type": "Container", "id": "cardContent", "isVisible": false, "items": [ { "type": "Container", "items": [ { "type": "TextBlock", "text": "Text" } ] } ] } ], "separator": true, "spacing": "Medium" } ] } On the initial load, the image (down arrow) gets rendered properly. If I click on it, the collapsed section opens (and the down arrow gets hidden and replaced by the up arrow). However, if I collapse the accordion again, the following happens: And it stays like this until I restart the Teams client. Looking at the devtools network tab for the web client the following behavior can be observed: During the initial load (1) the down.png gets fetched and stored in memory. You can also see the result on the right. If I extend the component (2), the up.png gets fetched and stored in memory. If I then collapse the section again (3), the call to memory for the down arrow fails with GET blob:https://teams.microsoft.com/51e89b2e-7da4-4c80-bf98-a6ee4d257052 net::ERR_FILE_NOT_FOUND It happens in both the standalone client and the web version. Also for multiple users (so it is not just some caching issue on my side). It seems to me that toggling the visibility somehow removes the images from memory. But it only happens for images that are initially visible (it doesn't happen for the up arrow in my case).
SSO for a Python Teams Bot (M365 Agents SDK + FastAPI) — Single-Tenant, Multi-Tenant, and UAMI
We're building, a Teams bot (Python / FastAPI) that uses the M365 Agents SDK (microsoft-agents-hosting-fastapi + microsoft-agents-authentication-msal, v0.8.0) with a CloudAdapter and MsalConnectionManager. The bot is currently scoped to personal only and runs behind an Azure Bot resource. We are trying to implement SSO to authenticate users, so far we are not successful. The main blocker is that we failed to authenticate users from tenant different than the Azure Bot resource of our app. If anyone has successfully managed to authenticate users on Teams using a setup similar than ours please do share your experience. We would love to learn from your experience. So far this was our main source of documentation: https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/authentication/bot-sso-overview Many thanks
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!
