This feature is still in the planning stage. No new updates are available at this time.
This is still being worked upon. I hope to have more details in the next couple months.
Please know the team is actively working on this feature.
This request has been declined by the feature team.
Private channels may help with items such as this request once they are released. The Private channel topic is tracked at http://microsoftteams.uservoice.com/forums/555103/suggestions/16911079
Please note the handling of “Guest Accounts” is a separate ask and can be found at: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16911109-guest-access
The request about “Guest Access at the Channel” level is being tracked by this request: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31374577-guest-access-should-be-implemented-at-the-channel
Thank you all for the feedback.
In our case we are multiple teams working on the same product. We have one private team for each one, and then one public for announcements etc.
As an example, we have a channel for voting on lunch places where most of my team participates. We also, however, have one or two people from another team that also joins from time to time. They can however not be assigned to participate in our discussions as they are not part of our team.
I don't want them to be part of our team (minimize amount of information), I don't want to have a cluttery channel in the announcement team (would like to keep it as clean as possible), and I don't want to create a public "Lunch team" (that's just ugly).
As such, the best solution imo is to be able to invite other teams' members to channels. Alternatively introduce ability to create "Public Channels" for each team. That would create semi-public teams, where the team existence is known to all but the content to others is limited.
Thanks to everyone who volunteered for testing the Office 365 group calendar. The TAP team will be reaching out as we are closer to being ready.