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 (Please include only one suggestion per post. Duplicates 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 update 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.
-
Webhook needs to support forced notification a la "@channel", "@team", "@person"
Webhooks should have a property to force notification a la "@channel", "@team", "@person". I have been using Slack webhooks for notifications out of our monitoring platform and can use "@" tags to make sure that the correct channels get the data and if the condition is severe, notify "@channel".
1,762 votesWe’ve added this to the backlog. Please check back here for updates on this feature request.
- Don't see your idea?