Jake Moore

My feedback

  1. 28 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  2. 9,745 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1005 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  3. 11,578 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    933 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.

    Full multi-tenant, multi-user support will be added after fast tenant switching.

    ~Alex

    Jake Moore supported this idea  · 
  4. 9,642 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1112 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  5. 18 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore shared this idea  · 
  6. 4,193 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    140 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.

    Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.

    Suphatra

    Jake Moore supported this idea  · 
  7. 4,725 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    289 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This feature request is still on in the backlog. No new updates available at this time.

    -Warren

    Jake Moore supported this idea  · 
  8. 1,430 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    179 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  9. 1,646 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    76 comments  ·  Public » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  10. 2,604 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    77 comments  ·  Public » 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

    Jake Moore supported this idea  · 
  11. 5,131 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    389 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    The feature team is still reviewing, there is lots of discussion about this item and I hope to have a decision soon.

    -Warren

    Jake Moore supported this idea  · 
  12. 6,362 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    working on it  ·  405 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  13. 10,790 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1213 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  14. 1,010 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    146 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Warren responded

    Mute a channel is still being worked upon. The team is still hard at work on this item. No updates at this time.

    -Warren

    Jake Moore supported this idea  · 
  15. 23,784 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1942 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    We acknowledge the customer demand for Private Channels and have been hard at work on it. Private Channels is currently in preview with a select group of customers. We expect to release the feature to the public later this Fall, and will update here when we are starting to roll out to all customers. We appreciate all the feedback you have provided to us on this forum and thank you for your patience.

    ~Alex

    Jake Moore commented  · 

    Great, this will really help me achieve what I need to! Thanks for sharing the intention

    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel this would solve my problem. Nested teams with the ability to set permissions for each nested team could work too.

    Jake Moore supported this idea  · 
  16. 8,751 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    564 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  17. 287 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    Thank you all very much for the great response. The survey is now closed. The feature team will be reviewing all the data that was gathered and responded based on the findings.
    Again, thank you for helping us make Microsoft Teams the best it can be.
    -Warren

    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel then this would solve my problem.

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

    We’ll send you updates on this idea

    188 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Warren responded

    This request has been reviewed and declined by the feature team.

    You can continue to up vote this topic as well as leave comments. Depending on the ongoing feedback, there is always a chance a topic will be revisited based on user demand.

    -Warren

    Jake Moore supported this idea  · 
    Jake Moore commented  · 

    100% agree. I have far too many top-level teams here. If I could nest teams that would be helpful. My main requirement is to keep 'channel' permissions separate to 'team' permissions but currently the only way to do this is to create a new top-level team which becomes overwhelmingly large when a new channel is created for each incident. If I could somehow either assign separate permissions (user access control lists?) to each channel then this could be an option too however, greater nesting would indeed be super helpful.

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

    We’ll send you updates on this idea

    declined  ·  148 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore supported this idea  · 
  20. 5,134 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    475 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Jake Moore commented  · 

    It seems that threads get posted in the incorrect channel because people dont know where to post at times or forget that a channel exists. It would be beneficial to the overall tidiness of teams to be able to move a thread from one channel to another if someone posts it in the incorrect place.

    Jake Moore supported this idea  · 

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.