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.
Having the ability to create a Team associated with an already-existing SharePoint site would be a HUGE feature as it would prevent the oh-so-common issue of "The org already stores files in an SP site, but Teams users now store files in the Files tab for the Teams group" madness.
This would also help those users who are annoyed by the fact that you cannot change the SP site location for the Files tab in Teams.
Nathan Berger commented
Just a gentle reminder that some of this is already possible: https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-connect-to-office365-group
Along with this, some members are saying below that there's a link on the root of a SharePoint site collection that can do this as well.
Adding support for linking to a site and not a site collection so team sites reside within the one site collection. Information managers and SharePoint governance would greatly benefit.
I understand Microsoft has struggled with its culture of Teams not collaborating. But other organisations don't operate like this, especially academia. Reduce information silos and empower cross team communication/rollup. Remove barriers, don't create them by default.
I cannot locate the link to create the MS Team from the SP Team Site, and I'm in the Root site of the site collection. Where is this link located?
Quick update.. The link to create an "MS Team" from a "SP Team Site" will only appear in the "Root" site of a site collection. It does not appear for "sub sites" that may themselves be "SP Team Sites" /Marcus
Hi All, I noticed that a link appeared yesterday (22 Nov 2018) that allows me to create a "MS Team" from my existing "SP Team Site".
The only confusing thing for end users is that "Conversations" in the "SP Team" links to the "Group" in outlook whereas in the "MS Team", the tab "Conversations"relates to the threaded "MS Team" discussion.
The "Files" tab in the "MS Team" now correctly navigates to a folder in the "SP Team Site" document library to a folder with the same name as the Channel.
I also noted that the the "SP Team Notebook" did not come over to the "MS Team" automatically and needed to be added manually as a tab in Teams - but it DID work nonetheless.
Also when I went back to the "SP Team Site", the Quick Links menu automatically gets a new entry "Team" - which links directly to the corresponding "MS Team".
This is a great feature. Thanks to all those on the Microsoft team that made this happen.
PS. Whilst this is a fantastic feature, it would have been even better had the "SP Team Site Notebook" been added automatically and "Conversations" in the Quicklinks was renamed to "Group Conversations" so end users realised it was different from the "MS Team" "Conversations"
Revathi SC commented
Adding to the request for integration with SP site, it will avoid duplication of effort and documents. During actual execution, there will unwanted confusions of which document to use.
Can also enable the calendar feature or integrate with SP calendar to track leave and enable in resource planning. The current feature only has task tracker
I need the "files" tab in a channel point to an Existing SharePoint Site. Having existing SharePoint libraries linked to as "tabs" does not help us. If someone accidentally uploads a file in the "conversations" tab, now it's in the New Team SharePoint and not our existing site. Having more that one place where files are stored and not being able to control where files get uploaded is pretty unmanageable.
this needs to be a thing..... we are looking to deploy teams around our company and like the teams integration it has with SharePoint team sites. BUT all of our SharePoint sites are legacy sites and we cannot link them to teams. cannot believe this is in back log and not urgently being worked on! also when you are trying to push a product like teams having the functionality working before release would be advised! but we area ware that this is unheard of by Microsoft so i guess ill just have to wait for a long time!
When is it expected to get this feature to link to sharepoint sites as this is required to really benefit from using Microsoft Teams and not having to copy paste which is WASTE in my books.
Bart Louwagie commented
Agreed. Is crazy how complex Microsoft makes this. Why is there a "open this in Sharepoint" when you then can't really connect to a Team's location from SharePoint.
If that is not possible then make Flow be able to use/be triggered by Teams's lists.
please get this off the f-backlog and into f-development!!!
We really need this function in our organization... Please add it.
2000 Votes! Please make this available. I followed the post shared by @Nathan Berger but this option isn't available to me in our sharepoint environment.
@Nathan Berger. Its still here because Microsoft is insistent on creating thousands of site collections. Furthering the SharePoint Governance mess. Teams should be one site collection with subsites for each Team. Site Collection administrators IS NOT a permission level for users.
A Governance mess doesn't even touch the sides.
Nathan Berger commented
This is currently possible. You have to create an O365 group on a SharePoint site: https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-connect-to-office365-group
Then just create the Team on the O365 group and you're all good to go.
I have no idea why this is still up here.
Iain Hands commented
Is there any way this could be moved further up the development queue?
I cannot believe that two mutual technologies that are essentially built on the same platform cannot be linked! We have spent years developing and enhancing our SharePoint sites for project and team working. We are wanting to embrace Teams as we see the benefits of what this offers, however the fact we cannot put a Teams front end onto our existing SharePoint site seems, well frankly, ridiculous!
Please Microsoft development - fix this one!!
Bernard Mariès commented
Since Teams and Sharepoint are supposedly parts of the same O365 universe, they can not and should not be isolated one from another. That in the current state, Teams automatically generates its own sharepoint, whithout letting users choose to connect existing ones, AND that it is not possible to generate a Team page from an existing sharepoint is a SHAME ! Hope you guys put that one on top of your desks - should never have happend in the first place. #basicLogic #coherence
S. MacLaren commented
For reasons of backward compatibility and Office365 transparency, export / import one-way - minimum - into Teams is important for productivity.
To me, the import of any Sharepoint library should be seamless, and I do not care if it uses a compressed folder. (Meantime the get-around is to simply link the external library with the Team, which works VERY nicely, web app or desktop app). There are advantages in leaving it on the Sharepoint which include not having to add people you do not want in the Team but letting them stick with their existing permissions for the Sharepoint library.
I'm a Scenario A voter. I want the ability to connect a new Team to an existing Sharepoint site.
> If you are asking for Scenario A, then can you please answer these follow up items:
> Q1: If we made this possible, then would you expect the SP library to auto-generate channels in accordance to the folder structure? What would you expect to happen if you selected an existing SP site in the team creation process?
I think an *option* to auto-generate the channels would be fine. Just prompt when creating the Team. I guess when creating a new channel you'd need to check if a folder of the same name already existed in the structure. If so, just link them.
> Q2: How important is this to you, comparative to other asks in UserVoice? The best way to answer this is giving it a 1 to 10 rank, 1 being this is nice but not vital, 10 being there is no other feature you want more.
> Q3: Would using the Create Channels API fix this for you, so you could make your own solution?
That wouldn't be feasible for my organization.