Welcome to the February 2024 edition of What’s New in Microsoft Teams! This month we are showcasing 37 new features and enhancements for Microsoft Teams. These updates will help you collaborate more ...
Updated Mar 04, 2024
Version 8.0
Blog Post
Hi Steve_Stein
Few time in past I have asked, if you could let us to write multiple lines of the monospace text on the chat, in case if I would like to copy text from command prompt. As by default that has not been working very well. Using the "code" bloc is not so good idea. Can I see correctly, that you have fixed the problem now by:
...removing completely the option to having different fonts at all 😄
Have you thought about bringing an possibility to share multiple apps at once? Try it by yourself and see how do you feel when you need to jump between apps using one screen and sharing app only.
About the support logs. there could be tiny help for us. When you are collecting the logs using the Four-Finger-Pray (Shift+Ctrl+Alt+1) and if you have also selected Teams client to be asking where the files are downloaded every time. Then these support logs are split to the two parts: "Web Logs" (in where you saved) and "Support Logs" (in Downloads folder). Will it be possible to get these into the same location in future?
Will there be some log management in future, or how shall the following folder should be cleaned?
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\\Microsoft\MSTeams\Logs
Will there be "developer tools" on Teams V2, or was that for Teams Classic only?
Have you verified from your statistics how many of the Teams V2 calls are in these days without DCSP marking (QoS)? If your customers has done the marking by the GPOs and following your guidelines, they have done that for the process name: "teams.exe". If they have not made any changes since then, on your statistics you should see decreases of the calls with DCSP marking. Perhaps this could be good to share them. Especially when you are forcing the Teams V2 for them, that there should be extra policy where the process name should be: ms-teams.exe.
Has anybody asked from you if you should improve the mute feature:
on Teams client so that we could "mute for 60min", "mute for 180min"? Sometimes you like to get silence for next hour, wouldn't it be great if you could mute all chats for the next 60mins?