This feature request is working its way through the backlog queue. No new details are available yet.
Teams is not covering new ground. It is going to be adopted primarily at the start by people who are curious but mostly by Microsoft customers. They are likely to be using sharepoint for their existing team collaboration. Now, Teams creates a new, separate sharepoint sandbox and attachments in Teams go there, not the original sharepoint, fracturing the knowledgebase and files. Files (storage, cost) will be duplicated between the two, and then you have a problem knowing which version (teams sharepoint version or original sharepoint version is the latest, or which 'should' be used now. Confusion, friction, resistance, slow adoption, etc.
We would much prefer the ability to, from SharePoint, enable Teams for an existing SharePoint which is already in use. Or even an offline tool which could Teams-enable a sharepoint.
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.
Thanks!Jeff West supported this idea ·
Yes this is important. In addition, the ability to configure a notification when specific words are used is also very valuable. This is available in Slack.
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.
We need private channels. This is not a good alternative. The app already gets slow when you have more than one Team.