Public
Hi there, you’ve reached the user feedback site for Microsoft Teams. It’s managed by our Customer Advocacy Team inside Microsoft Teams Engineering led by Karuana Gatimu. Our entire team believes in representing your needs inside our engineering group and we appreciate the time you take to share them with us. Rest assured that a large team of dedicated people read and discuss your feedback!
Here’s how to get your voice heard:
1 — VOTE for existing ideas (this will also subscribe you to the idea’s status updates)
2 — SUBMIT new ideas (any duplications are merged together)
3 — RATE the product by clicking the little orange star on this page. This helps us understand our overall standing with users. It will collect your rating every six weeks.
4 — COMMENT in ideas’ threads, which we check regularly
For official product and feature updates we recommend three things:
Stay tuned here: We updated our work items monthly
Read our Blog: Official announcements come from our blog at https://aka.ms/TeamsBlog
Review the Roadmap: Our upcoming features can be seen within the Microsoft 365 roadmap site at https://aka.ms/M365Roadmap
The Fine Print: We have partnered with UserVoice, third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.
-
Close the Notification Loop
Notifications could be tightened up a bit.
1) Sometimes when I read messages that cause notifications, the red notification lingers on the channel until I click the channel on the lefthand side.
2) Sometimes after I read a notified message, the Teams icon continues to blink on my taskbar after I've read it.
3) When I acknowledge a notification on the desktop application, the notification remains on my phone and vice-versa.
18 votesIssue #3 described above has been fixed in the latest versions of Teams in the app stores. Please comment if you are still seeing #1 or #2.
Thanks!
-
Teams crashing about 40% of the time when in calls
Started doing this the last couple of weeks.Pretty erratic: sometimes it is when you share your camera or when you share both camera and screen. Hard to pinpoint what causes it exactly but straight up calls (without cams) seem to work fine.
15 votesIf you are experiencing these crashes, we would like to investigate. Logs will help us do so.
If you’d like to send logs, please:
- type (windows key) + R
- type “(percent) appdata (percent) \ Microsoft \ Teams \ logs.txt” into the open box (without the spaces, parenthesis, and quotes)
- save the file
- send the log file that you saved to teamsml@microsoft.comThanks!
-
some times after refering a person with @person, the editor continues to write in bold/strong
Hmm couldnd figure out where to file a bug? So, this "idea" is actually considered a bug!
some times after referering a person with @person, the editor continues to write in bold/strong
12 votesIs this still happening for you? Votes have dropped off so I hope this has resolved. Please let me know!
Please comment in this thread your response.
Warren
-
Windows 7 has a banner indicating "Quiet Hours is enabled" and you will not get any team messages..
Windows 7 has a banner indicating "Quiet Hours is enabled" so you won't get notifications for calls and messages in Teams. However, Windows 7 has no Quiet Hours settings to turn this off.
6 votesWe believe this is fixed… can you please comment with whether it’s resolved for you? Thanks!
- Don't see your idea?