This request is still on the backlog.
I'd love to be able to tag entire teams this way so we could group project teams by application, etc.
We know many of you are waiting for a Teams client for Linux, and we’re pleased to confirm we’re actively working on it. Stay tuned for more information.
This is an absolute requirement for us. Several of our internal devs and many of our contract resources are exclusively on Linux desktops, and we can't take full advantage of Teams until there's a native client (or Teams makes use of browser-based integrations with common X notifications frameworks).
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Yikes, MS. Yikes. This seems like a pretty basic architectural flub.
Best I can tell, you don't _provide_ any tools for "moving content around," period. So we're essentially stuck with our past bad (or no longer optimal) decisions.
As another guy said, allowing us to override permissions at the channel-level could help in some cases, but it doesn't help us organize things better as we learn the product, team structures change, etc., etc.
Maybe if you share a little more about why the architecture makes this difficult we could provide suggestions.
As our organization is learning and trying to build best practices around Teams while incorporating it into our workflow, *not* being able to shift channels between teams is proving to be a real stumbling block. We need to be able to easily restructure things as we explore different organizational options. As it is, it seems we're stuck with the choice of either living with decisions we made in ignorance or losing history.
We are still considering this feature for future releases, and will continue to update the status when it changes.
This would be a reasonable, temporary plug for the hole the lack of a native Linux client leaves in Teams' offering.