Create Team from existing SharePoint site, and other requests
#1 User Request on SharePoint:
Enable integration of Microsoft Teams to an existing SharePoint site rather than to always create a new site collection
There have been a few ideas raised on integrating lists, OneNote, document libraries, etc. from an existing SharePoint site with Microsoft Teams, but in summary, it will be best if we could create a team upon on existing site, so that the "Files" and "Notes" tabs would directly reference the existing document library and OneNote in SharePoint. It does not make sense to have two separate sites: one for all the usual SharePoint stuff, and another just for Microsoft Teams.
#2: Link to Existing SharePoint Sites
Trying to link my Team up to an existing SharePoint site - only seem to be able to link to individual folders rather than the whole document library, meaning that if i want all folders on the Team i need to create multiple tabs to get this. Would be good to link to a whole document library rather than one folder.
#3: Other Asks
Post Team chat to SP microfeed
Connect team sites onenote if available (replace default notes)
Add links to existing document libraries (replace default files)
Add links to existing lists
Add support for SharePoint taxonomy and managed metadata, SharePoint views etc :D
This feature request is working its way through the backlog queue. No new details are available yet.
It should be as simple as adding a link to an existing Sharepoint document - it doesn't need to be in a Tab or whatever.
I get the impression that Teams, despite the links to other products, is seen as a standalone product.
How it should work: a new Channel is set up to complete a new coding Document Project/Task. Apart from identifying the team, this would involve completion of various setup docs and forms (e.g. budget, quote, approval, functional specification, technical design, etc.). These are already completed stored in Sharepoint and should not be copied into Teams. Instead, a link to a folder and/or links to individual documents hould be included in the conversation.
The Upload/attach icon in the Conversation window should allow a link to an existing Sharepoint document.
We encourage our users to place customer/project documents in defined folders within Sharepoint. Sharing of documents is always done by sharing a link to the document in the defined Sharepoint folder. This ensures that all users refer to the master version of a document and not an out of date copy.
Creating a copy of a document in each channel to which it is uploaded is valid in certain circumstances but will also lead to document sprawl.
In teams i should be able to discuss Files in Document Libraries other than the default doc library.
Daniel Schell commented
"Connect team sites onenote if available" is key. Embedding an existing project OneNote located in an existing sharepoint project is highly requested
Daniel Schell commented
Much like everyone else, this hasn't actually met the requirements of the original request
Custom columns, metadata and views would be very welcome!
Rick de Vries commented
"Post Team chat to SP microfeed." I'd rather **embed** the Teams chat feed than integrate it with an old microfeed from SharePoint. It would be the perfect successor to add a feed.
Bud Ratliff commented
I agree that it would be beneficial to be able to connect/share MS Teams with existing Team Sites.
Sarah Gaunt commented
Agreed that this does not satisfy the requirements of the original request.
Add Integrate teams' chat-log to Sharepoint, plz.
Support for meta-data is critical!
@Angela: also please note that adding a Sharepoint library the way you suggested doesn't allow you to create new folder/document (New button missing, there is only the Upload one) and doesn't allow you to Delete file/folder or the option "view in Sharepoint" is also missing.
When creating a new channel it would be great if you could have it use an existing SharePoint site in O365 for posting files and Onenote. This would be preferred to simply adding a link to a site. When creating a team, if you use the same name as an existing SharePoint site, you could use that site. THis would be simiar to how you can create a Team based on a Outlook Group already.
David McKnight commented
This is one reason I have been very slow to really roll anything out to our users. I have been watching O365 Groups continue to grow, and I think that's where I want to be -- so I introduce Planner to some select users, only to have Teams come out with a hobbled version of Planner built into that, but not available from Groups or the Planner Hub.
I agree with many others, this is not completed as requested. Adding a SharePoint library is not the same as having the Teams part of an existing site; rather it creates another site. This should be an option: Create new site or be part of an existing site.
I believe most of the people who voted for this, wanted to leverage existing SharePoint rather then creating and maintain new one for Teams
Sane Nobles commented
This needs to be reopened as the feature that this request is about is not actually available. Like Isaac mentioned below, this request is to link a MS team to an EXISTING sharepoint site not just import/link specific files or SharePoint libraries.
Isaac Chua commented
Hi Microsoft, you've mistaken what this request is about. Yes, you can add a SharePoint library and I am aware of that feature. But this is about creating a Team on an existing SharePoint site. The current behaviour creates a new SharePoint site collection with its own OneNote and its own Document Library. I am asking to create a new Team upon an existing site that has its own OneNote and Document Library, so that we won't have two library sections (Files and the other one using what you had described), and two OneNote sections (Notes and the other one with the OneNote tab).
Can this be reopened?
Add Sharepoint tasks like you added documents
It's good that you can link with an existing sharepoint site. But still when you share files in your team channel it gets stored in the separate Teams Sharepoint site. Would be much better to let the user choose on which Sharepoint site files should be stored. Either in an existing sharepoint site or in a new one that Teams may create. Why would you want to have 2 sharepoint sites...