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.
Our team has a SharePoint site with multiple lists and libraries. I'd like to be able to at least have a link to our site within the Team application. Currently you can add a tab for a library, but that is not sufficient. I'd just like all of the teams resources to be assessable in one place.
Lasse Thomsen commented
We have over 15000 SharePoint Sub-Sites, each site holds information for 1 project. We also have a long data retention period of 33 years (IP data). Having 15000 teams would properly not be good, but being able to link a "working" team or channel to a project SharePoint site would be brilliant. It would also be very useful for legal reasons to be able to store the persistent chat in the SharePoint project site.
Pieter Snyman commented
The status says 'On the Backlog' but when I was testing Teams in Feb 2018 it allowed me to create new Teams from existing SharePoint sites. Is this not the request?
Please note: this type of functionality is out of the box with tools such as M-Files. Teams has great potential but lack of easy taxonomy searching and organization put it at a disadvantage when up against other tools.
Maybe I'm not understand the tasks above but my need is to be able to add a Specific folder when "dding folder" like
Sharepoint site\document Library\Specificfolder (not the highest level in the Three)
This feature is the only thing holding us back from using Teams
Christian Gustafson commented
Vernon Jones commented
The key function I need is the option NOT to create a new SharePoint site collection for each Team/Group/Plan, etc. Even creating just a new subsite within an existing site collection would be a step in the right direction.
Patrick Otzenberger commented
An update with a realistic timeline would be much appreciated. There are dependency decisions to be made to move all SharePoint Files to a new Teams site vs creating a new team and use the web-link to access files on existing sharepoint sites.
Jeff Messer commented
Any more recent updates on this? We have a SharePoint 2013 Foundation server set up for our small team, and while it's extremely important to us as our main process and document library, it's also a little wasteful to have two dedicated servers for us to manage (Prod and QA). If there was a clear path to migrate that site to a O365 Sharepoint or Teams site, I think we'd do it in a heartbeat.
As far as I understand this is possible to do for SharePoint online site when you create a new team. There is a link called "Looks like you're an admin of a group. You can add Microsoft Teams functionality without changing the existing group. Yes, add Microsoft Teams functionality" and when you click it you will see the list of existing SharePoint groups.
In this case Teams doesn't create a new ShP site, but attaches to the one associated with the group.
I tried adding only one folder from existing SharePoint group but end up with the whole library... Help!
Any updates on this? My SharePoint sites and Teams sites sprawl is getting out of hand. I'm almost about to boycott O365 all together because there are so many disconnects now.
Any news on this topic. We are don't like the idea to have out file repositorys split between SharePoint and Teams. Makes no sense
Jose Carlos Garcia Sogo commented
We also need to bring in our existing infrastructure (Sharepoint sites) into Teams for this to work in our organization. Creating new Teams with its own site works only for a limited amount of cases.
What's the latest on this "Upgrade"? This would be a HUGE help to my organization!
Bob McKeating commented
Its now a month since the last post is there an update or reference to the sharepoint uservoice planner item?
John, I think she means 'modern site' and 'O365 group', she just mixed it up a bit. When you create a O365 group, modern site is created automatically. Not really know what Suphatra means with 'it can be easily converted into a team in Teams' because it can't (well it can but not easily and without API :)), but may be she will clarify.
Hi Suphatra, I don't know what is meant by a Modern Group (I can't find any information on it anywhere) but this review doesn't look like it's going to provide the flexibility needed for Teams to be used in existing environments. E.g. Link a Channel to a specific folder.
If I can't bring along my existing infrastructure, Teams remains unusable...