This continues to be on our backlog due to prioritization of other work items. We will update when there is more to share.
Sure would like to see this happen very soon.
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.
This feature is on the backlog. I will update you when we have more details to share.
I'd love to be able to tag entire teams this way so we could group project teams by application, etc.
This item remains on the backlog.
This would be a reasonable, temporary plug for the hole the lack of a native Linux client leaves in Teams' offering.