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. Move a project (channel) from one team to another

    We would like to move a project (channel) between groups to keep the information.

    13,122 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1549 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to archive channels

    Would be nice if we had the ability to archive channels. For example: we created a channel for a specific project. Once the project is complete, we can archive that channel or at least move it out of the primary view. I could see the channel list getting large and clunky quickly with multiple projects many of which are complete.

    Also, when a conversation in the channel is complete it should be archived or hidden.

    10,757 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    686 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  3. Channel only members & guests

    Channel only members enable collaboration with people outside the team in a specific channel, without granting them access to the team itself.  The channel member could be someone in your organization, or external to your organization (guest).

    3,052 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    on the backlog  ·  187 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  4. Read Only channel

    Would like to create a Public/announcements Read Only channel so that only specified members can post. This allows for authorized personnel to make company announcements, but not everyone can post.

    (The request for a Public Announcement channel is complete, since the General channel can be controlled by admins and set to read only)

    3,047 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    98 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
    Hopefully this will move back up in the queue soon.

    -Warren

  5. Change which Tab is default landing page for a Team and/or Channel

    Right now the conversation tab is the default landing page for a Team and/or Channel.
    I want to be able to have a SharePoint site landing page in a tab and that tab be the default tab open when you navigate to a team or channel.

    Think of it like a landing page for that team. You may not want it to drop right into Conversations. If you can have a SharePoint page with a Microsoft Teams conversations web part, you get the best of both worlds.
    I can see a lot of scenarios where you'd want the chat window…

    2,041 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    279 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  6. Team Templates

    A team template!! Much like sharepoint document site or site templates that contain a specific layout and set of documents this would be amazing for a team template. We could deploy a team for each project we had that had a preset assignment of planner tasks and documents attached to it and a preset of channels that goes with that team. Could really make a big difference in the way we deploy and use teams.

    1,398 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    88 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This item is still queued up in the backlog. No additional details are available at this moment.

    -Warren

  7. When granting access a Security group or Distribution list to a Team. Changes to the security groups/DL does not apply.

    When granting access a Security group or Distribution list to a Team. Changes to the security groups/DL does not apply. If a user leaves the company or if we have new users, it is a manual process to add or remove them from a Team. Since we can select a Security group or Distribution list, changes to either should be reflected on the Team members.

    1,243 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    120 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This feature request is still working its way through the backlog queue.

    -Warren

  8. Shared channels within an organization

    Shared channels within an organization will allow people in different teams to collaborate on a shared project or v-team in the context of their own teams. A channel can be shared across teams in the same organization.

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

    We’ll send you updates on this idea

    on the backlog  ·  54 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  9. Shared Channels across organizations

    Shared channels across organizations will allow people in an organization other than yours to collaborate on a shared project or v-team.

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

    We’ll send you updates on this idea

    on the backlog  ·  14 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  10. Team directory

    There should be a quick way of viewing all the public teams in my organization outside of search.

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

    We’ll send you updates on this idea

    28 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This request is still working its way through the backlog. Nothing additional to report yet.
    -Warren

  11. Public Channels

    Public channels will provide an outbound communication window for a team to engage with everyone in their organization.  These channels are accessible to everyone within the org, without the need to join.

    For instance, we may have a team that is private and deals with network issues. They may want a public channel where they can provide updates to existing issues or answer questions users may have. Otherwise, you may end up with two teams in this instance: a private network team and a public network team.

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

    We’ll send you updates on this idea

    on the backlog  ·  20 comments  ·  Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base