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.  

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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,032 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    170 comments  ·  Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This feature request is now under review.

    I’ll update this topic as we move through the decision process. Thank you for the suggestion.

    -Warren

  2. Allow to post a reply to a conversation via REST

    Currently it is quite easy to start a conversation via the webhook of a channel.

    It would be great if the POST of this webhook would return an conversation id. This id could then be used in a subsequent request to reply to the initial conversation.

    230 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  18 comments  ·  Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
  3. provision

    It would be great if we could provision teams and channels with a template like Microsoft PNP. In the case of provsioning i would like to be able to add tabs bot connectors and compesed extentions in pre configured in a json or xml template. Rolled out with C#, JS or Powershell.

    hope we can get this uservoice request activated.

    35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base