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
Review the Roadmap: Our upcoming features can be seen within the Microsoft 365 roadmap site at

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. Delete bot messages

    With the Polly bot, sometimes a member of one of my Teams will make an error while writing out a poll. Currently it is not possible to remove this poll, or, as far as I can tell, any message that is created by a bot.

    It would be great to be able to delete messages created by bots.

    1,647 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    297 comments  ·  Bots  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow on premise bots

    By allowing bots which are hosted "on premise" (behind a company firewall), one allow to access systems from that company.
    This is the situation for many companies where the infrastructure or services which need to be reachable by bots is not on the public internet.

    Some scenarios:
    - A bot is running behind a company firewall
    - The bot connects to MS teams, joins a channel, and "listens" to conversations (outbound connection to the internet)

    This enables interactions like:
    - @bot, list defects (from an in-house issue tracker)
    - @bot, add capacity to applicationx (after an authorization phase, on-prem application…

    388 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    53 comments  ·  Bots  ·  Flag idea as inappropriate…  ·  Admin →
  3. Remove Bot Mention Requirement

    It seems as though currently all bots only work if you @mention them, so my assumption is that this is a requirement of the api used to develop the bots.

    Many people from my organization are used to IRC/Slack style bots where an explicit @mention isn't required for bots to parse a message and respond.

    Sometimes there is fun functionality that can be added for a lot of bots and having to @mention a bot really detracts from the user experience of some bots.

    I can also see this getting out of hand when using a lot of bots, so…

    239 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    26 comments  ·  Bots  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This item is still on the backlog. I’ve received no further updates yet about this topic. I will continue to bring your feedback to the feature team.


  • Don't see your idea?

Feedback and Knowledge Base