Forum Widgets
Latest Discussions
MS Teams with FreeBSD
According to this URL: https://itsfoss.com/microsoft-teams-linux/, Microsoft provides .DEB installer files for Debian and Ubuntu based distributions and .RPM for Red Hat and Fedora based distributions for MS Teams. I would like to know if there are any plans to also include the FreeBSD operation system into this mix? I believe it would be a worthwhile venture. Since MS is already supporting some *nix systems, including FreeBSD should not prove a major problem. I would be happy to do some beta testing if required. Thanks!
CSS 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!Mgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured
I cannot upload custom app into organization because Mgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured. What I tried: I tried to upload same app to other tenant but got same error. I tried to upload other app but got same error. What happened?
Incoming 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?How are you keeping Teams Machine-Wide Installer updated?
Now that Message Center # MC245996 is going into effect, users with new-to-them PCs with older install dates of Office are starting to see the update screen with the Teams Upgrade button. Since Office updates don't appear to keep the Teams Machine-Wide Installer updated, I'm wondering what solution you've come up with to keep the installer up to date. The current method of relying on the user to update isn't very enterprise friendly for an organization that typically prohibits software downloads. Is anyone aware of anything on the roadmap for the Office updater to keep the Teams Machine-Wide Installer updated with a more recent version of Teams?
