This feature is released now, please try it out and provide feedback. For details, please see the documentation below:
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 feature request is working its way through the backlog queue. No new details are available yet.
For me it is Scenario A with Q1 functionality as an option for the user to select.
Q2 = 9 we do not want a proliferation of Group sites when our business teams already have existing SharePoint sites they have been using and simply want to add Teams functionality on top of them.
Q3 = No.
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.
I agree that there is still a need for the ability to control access to a channel to a subset of those who are in the parent team. We may wish to have a private Team but within that large team there are sub teams who collaborate in scenarios where they need to keep their activity private from the wider team. Please consider implementing this instead of simply suggesting we create multiple Teams and increase the proliferation of groups/sites within our O365 environment.
Wiki now supports text markdown and styling from the toolbar! We are continually improving our compose experience in Wiki, look out for new improvements coming soon!
This item is still in the works. I’m waiting for additional details from the feature team and hope to be able to share something more detailed soon.
This item is still queued up in the backlog. No additional details are available at this moment.
The ability to define and provision a Team as well as channels, connectors etc. within it are a critical aspect of making this useful for team based engagements such as bids, projects and support teams. In organisations where the engagements are starting up regularly and follow the same management or methodology users shouldn't have to repeatedly do the same configuration activities before they can start working effectively. Support for template based provisioning is essential in these scenarios.