teams
53 TopicsCSS Properties being stripped from Teams Chat messages from Bot
Hi Team, We've noticed that certain CSS properties are no longer appearing in HTML messages when sent to Teams Chat. Previously, our bot styled messages using display and border properties, but now these properties are missing from the HTML when we inspect the page. Steps to Reproduce: Start the Echo bot from the sample templates (I used Teams Toolkit to deploy it to Teams or run it in the Test tool). In the TeamsBot.ts file, modify the onMessage function by replacing await context.sendActivity(...) with the following code. This example adds styling to an echo message. const a: Partial<Activity> = { text: `<span style="display: block; color: red; border-radius: 4px; padding: 4px; border: 1px solid red; ">Echoo:</span> <span style="display: block;">${txt}</span>`, textFormat: TextFormatTypes.Xml }; await context.sendActivity(a); Note: I also tried sending the HTML directly with context.sendActivity(...) without setting the textFormat property in the Activity, and observed the same result. Run the bot in the Test tool and Teams to compare behavior. Observed behavior: In the Test tool: All styles are applied as expected. In Teams: Only the color property is applied, while display, padding, and border properties are ignored (stripped out of the HTML). Here’s an example of the HTML output in Teams: <div dir="auto" id="content-1730973548675" aria-label="Echoo: test styles properties" class="fui-Primitive ___16zla5h f1oy3dpc fqtknz5 fyvcxda"> <span style="color: red;">Echoo:</span> <span>test styles properties</span> </div> Could you provide insights on whether this change is intended, and if there are any workarounds for preserving these CSS properties in Teams messages? Thank you!79Views8likes0CommentsSend personal messages to Teams from daemon service.
Hello, I need to send notifications to my colleagues using Teams in case of emergency which is detected by monitoring system. These messages must be sent on behalf of background service which cannot follow interactive user authentication flow and therefore cannot get Authorization Code to authenticate on behalf of user. I can connect to Azure AD using Graph SDK for Golang and get all users of my organization. But I cannot use Chat API because it's not allowed in "application only context". Is there a way to send personal user messages from daemon service?Solved3.7KViews1like7CommentsHow to resolve "Failed to submit this app" error?
Hi Team, Just from Today, while submitting teams custom app via Developer Portal, error "Failed to submit this app." started to occur. I have tried with below condition but this error always occurs. Error also occurs on the app which we can submit update till yesterday. What is happening and how can we resolve it? (from this error message, we couldn't guess anything about the reason..) Checked: ・Publish from outside Developer Portal (apps > manage apps > send app to organization) succeeded so seems Developer Portal related Issue. ・For all apps, no validation error in "Publish to store" is found. Manifest itself seems to be fine. ・Create new custom app with minimum configuration and publish but failed with same error. ・Tried publish from both Teams client and Browser but failed with same error. ・Try same operation with different tenant but failed with same error.13KViews0likes24CommentsPublish teams bot only to some customers
We have a teams bot that we would like to be installable only by our customers. Is it possible to publish a bot to the teams store and only allow a set of organization / people install it ? As far as I know, bots published to teams store are public and installable by anyone.433Views0likes1CommentCannot interact with screen while Teams Annotation is on.
Hey, so in the past I've taken a lot of advantage of other apps' screen-share annotation features. Unfortunately, Teams implements it in a way that isn't very useful for us. The presenter needs to be able to still operate/ navigate their machine while participants annotate. The "cursor tool" in annotation mode is a little puzzling to me, but if there could be an additional cursor that return the pc to "normal mode" for the sharer, and does not interact with the overlay, it would be an extremely useful feature. Thanks, Tom.613Views0likes1CommentMentioning of a user is split in first and lastname
I just discovered that from somewhere in December I do not get a mentioned user in a message as one mention any longer but splitted into two mentions with first and lastname. Is this a bug or is it by intention? This is how the JSON message to the bot for the message: @bot Sarah Johnson mentioning looked like until December: { "text": "<at>bot</at> <at>Sara Johnson</at> mentioning", "textFormat": "plain", ... "recipient": { "id": "...", "name": "bot" }, "entities": [ { "mentioned": { "id": "xxx", "name": "bot" }, "text": "<at>bot</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Sarah Johnson" }, "text": "<at>Sarah Johnson</at>", "type": "mention" }, ... ], ... } And this is how it looks today. { "text": "<at>bot</at> <at>Sara</at> <at>Johnson</at> mentioning", "textFormat": "plain", ... "recipient": { "id": "...", "name": "bot" }, "entities": [ { "mentioned": { "id": "xxx", "name": "bot" }, "text": "<at>bot</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Sarah" }, "text": "<at>Sarah</at>", "type": "mention" }, { "mentioned": { "id": "123", "name": "Johnson" }, "text": "<at>Johnson</at>", "type": "mention" }, ... ], ... } The mentioning is split in first and lastname with the same userid. Is that the intended behaviour?473Views0likes3CommentsIncoming Webhooks Emojis stopped working
Edit: It seems that emojis are working again since 28.04.2023 --- Until 25th of April 2023 I was able to send AdaptiveCards to the Teams Incoming Webhook that contained (unicode) emojis in TextBlock text. E.g.: { "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": "TextBlock", "wrap": true, "text": "🕵️ Hello" } ] } } ] } However this stopped working and the Webhook-endpoint responds with status code 200 and following text: Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 400 with ContextId MS-CV=6VuKZ6LzJEy0rlogGwBLyg.0.. When sending the same message without the emoji it works as before... What has changed? How can I fix it?5.2KViews5likes9CommentsIs it possible to call a Teams contact from a SIP client, like Linphone?
There is a commercial solution, Cybergate (https://www.cybertwice.com/), that allows to call a Teams contact from a SIP client. I was not able to find any other free or even commercial alternatives. I had a look at MS Graph API and chat bots, but this can programmatically trigger a call only between a bot (which is already a Teams account) and a user, so no luck there. Is there a way to call a Teams contacts from a SIP client? Can somebody point me into the right direction?3.6KViews0likes7CommentsHow do I allow a user to trigger a task module from an adaptive card in the compose area?
I have a teams bot which responds to search queries via a messaging extensions and allows the user to embed card responses in messages and teams. I have reworked it from making use of thumbnail cards to make use of adaptive cards to leverage the ability to trigger Task modules from them so that I can make a popup web view appear when the user clicks the button. This all works fine while the user is clicking the button on the card after it has been posted as a chat or channel reply. The issue is that while the card is still in either the command bar or the compose window, prior to the user copying it or posting their message, the button which triggers the task module does not work. It is also worth noting that the other buttons present on the card which are AdaptiveOpenUrlActions work as expected in both the compose window and the posted message. This is the C# code I am using to add the button to my Adaptive Card: actions.Add(new AdaptiveSubmitAction() { Title = "View", Data = new PreviewTaskModel() { DocumentId = result.Metadata.Id, ContentSourceId = result.Metadata.ContentSourceId } }); My question is: Is this intended functionality? If so does making use of DeepLinking work around this issue?Solved2.5KViews0likes11Comments