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.
@Suphrata please change the status to Working on it and for Christmas give us at least a status update. Pretty please!
I agree completely with @bas
Like everybody the features in the survey might be nice to have but not as essential as private channel. Working on the features of the survey should not be a priority as far as I'm concerned. The feature that people want by a WIDE margin is private channel. You would have made my day if the survey had been about features related to private channel. No objection to being of help in orienting product development, Teams is a tool I believe in. In return can we get some news about where is the development team on private channel ;-)
Glad to see you back Suphatra! We missed you.
Would like to have a hint on how it will be implemented. Do the participant in a private channel need to be already part of the teams ? Will we be able to choose if the existence of a private channel is visible to non member of the private channel.
Really hope you will get that clearance soon!
Thank you so much Robert. This put it all in perspective.
Hello Warren, could we expect more than a "working on it" this month.
Thanks for the update Suphatra but the comment about the effect of guest access on this request and the fact that this is still under review mean that Microsoft is still not convinced that private channel are needed.
It is sad. I don't know what we need to do to convince Microsoft that we need this. The success of Slack should give you a clue.
And I agree with the last post. Does not need to be perfect on the first take.
I can already control document access via sharepoint. I just need to control chat access on a channel level.
Teams is the first product that got me and my organisation exited in a long time. It is simple, flexible, user friendly. Microsoft seem to be serious about O365 Groups and Teams. I think this comination can push adoption rate enough so an organisation like mine (1500 users) reap the benefits of implementing a collaboration suite such as O365. Private channel is essential unless you want to multiply teams. In mid to large organisation it is a must. If I need to get Slack over O365 it will offset my ROI enough to change the decision to go with 365. Many consultant in O365 deployment consider TEAMs a game changer and essential tools. Please Microsoft dont let us down on this one.
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.
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.
This should be working via the web client.
Can users confirm if you are still having this issue? Please let me know in the comments below.
If Microsoft can make it work with Edge why not with Chrome!
Everything work with Edge on win10.
On Chrome in the chat tab, video is grey'd out. You can click on audio and a message will say that the functionality is unavailable. In the team tab, you can start a "adhoc" meeting. Video is still grey'd out but audio seem to be working.
It would be nice to know what is supported on wich browser on wich OS. On a Mac or a Chromebook Edge is not an option, and BTW, I am not going to change browser because it work on Edge. Teams is a tool to unite people and make them productive on whatever platform they use. It is placed to replace Skype and bring people to O365. So make it work on everything, particularly WEB base.
Support for audio, video and screen sharing is now supported on Google Chrome.
Teams is a good product, in fact one one of the best since a long time from Micfosoft.
Adoption is linked to the number of plateform supported. And Browser base is a pretty BIG plaform. And Chrome is the dominant browser.
I can't control wich tools my customers use but IF I can use Teams to communicate with them it seem to me that Microsoft is winning.
So make teams work on every browser and you have a universal chat and communication tool. Something that Microsoft never achieved with Skype.
I’m switching the status to Partially Done.
The request for a Preview Team is still in the works. No new information is available at this time.
Team Discoverability is still being worked upon, no details are available at this time. If you support this idea please navigate over to the main topic and vote for it! https://microsoftteams.uservoice.com/forums/555103/
Change Prompt: this has been completed
Teams and O365 Groups are going to be a corner stone of O365 deployment. Many of them (departements) will be created by the implementation team. But one of the strongest point of Teams is how easy it is to create a Team. So we will probably end up with a lot of them. And having public Teams (inside the organisation) mean people need to be able to find rapidly what is relevant.
You already have Delve which do a wonderful job of finding what is relevant to me. Can't you do a similar thing for suggesting public Teams that are relevant to me.
Sure I would also like to have the search option or browse option.
In our pilot project with O365 though we find that people dont tend to explore or search. Inviting them get better result to bring their participation. Is it because the tool is new. Can't say for now.