Linux has many desktop environments each of them has different kind of windows managers that provides window borders and window header with close,minimize buttons, etc.

Teams ignore window manager at all ant provides its own window controls for main application window.

This is looks ugly because it does no comply with system look and feel. Also there is no window borders so it is hard to resize main window.
No shadows and other effects, because most of them related to default windows manager.
Look into attachment how teams window looks that in placed over web page.

VS Code for Linux allows to use native window borders, Teams should add such option to.

Please add support for using a virtual background on Linux.

Suggested initial level of support:
* Support using a green/blue screen to determine where to replace the background (i.e., simple overlay).
* Support using a user provided PNG or JPEG image for the virtual background.

Future level of support:
* Support blur or replace of the background without needing a green/blue screen (this would understandably require either a GPU for acceleration or a very high performance CPU).
* Support using a MPEG or OGG video for the virtual background.

Using V4L2 hardware acceleration (when available) would be preferred to doing everything on the CPU. If using the CPU, running the video processing on a separate thread would be preferable to doing the processing in an existing thread.

This issue is related to the one asking for native notifications....

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/39279040-introduce-freedesktop-dbus-notifications-for-linux

I think this deserves its own issue though. Yes, an option for native notifications would definitely fix this issue for me, since I'd immediately switch to the native notifications. But if the developers of the Teams client leave the non-native notifications as a toggleable option for example, then I think they should ultimately fix this for the non-native notifications any users who prefer that.

On my system (Arch Linux, i3wm), notifications from Microsoft Teams seem to grab focus and cause a very noticeable freeze for about a half second in any X11 app. My colleague runs Ubuntu and notices the same issue.

So, I followed the advice given here: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Where-is-the-best-place-to-report-bugs/td-p/32183

I posted a bug report here: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Bug-report-Link-missing-when-hiding-large-text-body-in-Teams/m-p/169272#M12158

Apparently, it has been marked as spam, so Ill try posting the same report here:

I have been looking for the documentation for Teams Webhook Connectors. I did a Bing-search for 'MS teams webhook connector documentation' and found soemthing [1]. The documentation doesn't fully explain the purpose of all fields that can be included in the POST request. I hope there's a better resource out there, somewhere, but I highly doubt it.

To the point: An example webhook POST [2] specifies that the body of your message goes in the text-field.

While this is great, too much data in the text-field results in this message appearing the Teams-chat:
> This message is too long to display here. Please visit the link to read the content.

This is fine, if the link was actually included in the message, but alas, it is not. It should be there, but it isn't. This is now a bug report.

If you have any questions about how to reproduce, please just ask away.

Disclaimer; I am a long time Linux user, and I haven't used Microsoft products for many many years. Usage of MS Teams is being forced upon me, so please please please give me a great experience. I would love to have something good to remember from my newest experience with Microsoft.

Regards, Asbjørn

[1] https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/connectors

[2] https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/connectors#post-a-message-to-the-webhook-using-curl