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.
Chris Webb commented
Hey guys, I read they are adding support for flow and if this gets added you can easily link a conversation action into a SharePoint list/item on any page you want.
I have been happy to see Microsoft's development of Groups and their integration with permissions on SharePoint. However it has been an operational nightmare when considering allowing individual to create their own Groups. There is no way to limit what is automatically created when a group is setup. What if the group does not need a SharePoint site linked and only needs a communication setup. Management of SharePoint permissions can be daunting and groups can help solve this problem but not being able to link them back to existing pages without creating entirely new Sites will cause confusion very quickly. At this time we are very hesitant to deploy groups company wide and will continue testing until solutions can be found.
We have deployed and adopted SharePoint Online and Team Sites, and have built out project management support sites for governance and auditability according to our project management framework globally. We cannot effectively use Teams without being able to link them to existing SharePoint sites. We will have mass confusion with our project team members on where to store project deliverables, etc. This will likely result in an audit finding if we're unable to track all project collateral in the designated and approved site.
Binu Thazhe Veetil commented
I strong support. In any organization it would be highly required to have the Microsoft Teams created for existing portals on O365 rather than creating new sitecollection->site.
As a user, I should be able to create a channel and link it to a sharepoint page so my team (or a target audience of the team) can have focused discussions on the topic and share documentation and calendars in Teams and on Sharepoint.
The common sharepoint page that links to a Team in Teams is too broad for a large team that works on multiple projects and different topics
Right now, I cannot use document library (add SharePoint tab) from the root SharePoint site (https://organizationname.sharepoint.com)
I opened a ticket with the support team and they tell me "unfortunately the feature of enabling SharePoint root site collection in Microsoft Teams cannot be enable; this is something that cannot be modified by design."
Like others have said, we already have SharePoint implemented. Creating a new, separate SharePoint site just to use Microsoft Teams will cause confusion for people. It will also make it more difficult for teams to decide where to store documents, and you may end up having documents saved in two different locations. Then you have the added issue of which document is the system of record.
When creating a new Team in Teams, it would be nice to allow "Create a new team from existing Sharepoint Team Site"
Harald W. commented
I appreciate the ability to add further ducument libraries to the Teams SharePoint and than link it to a new folder within a channel - getting all Teams functionality on this library (chat, ...). It would be great if this would work with all SharePoint apps (lists, contacts, ...). Visibility of meta data in Teams would be an other big improvement.
In Addition the option to link Teams to an existing SharePoint site, as discribed in various posts, would be very helpfull but not so easy do implement (I guess).
Steven Wong commented
As Jeff West, Laura and many others commented below, Teams should EXTEND an existing Site in a Site Collection, not create a whole new one.
Jeff West commented
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.
John Wildes commented
I think it should be called out that if you've built a team, you get a SharePoint site with that team. Anytime someone adds a file or folder outside of Teams to the SharePoint site, and then wants to reference that file in a chat / conversation, Teams copies the file (even if you've browsed to Microsoft Teams - > Channel Name - > Sub folder with files you need) to the default Channel Folder rather than linking to where they were saved e.g. in a folder inside of the Channel. This shouldn't be hard to do...
Matt Allan commented
To allow a team to actively collaborate on the wiki which is publicly visible by others on the SharePoint site
Tarik Kranda commented
I would also like to inform that afterwards of your team creation, you can go to Office 365 Online and remove that office 365 group created behind. But in this case, you are not able to use some functionalities of Teams such as file sharing and you can not get email address of the channels for that team etc. Some functionalities of teams are directly attached with Office 365 groups. It would be great to have this functionalities with no binding to a new or existing Office 365 groups.
Fanny Tsui commented
Connect to SharePoint document library sub-folder/file and list
At the moment you can add a SharePoint Document Library as a Tab. However, we want to add individual folders in that Document Library as a Tab.
I agree, SharePoint Team sites should be the same as Group sites. It is too confusing to have a department SharePoint site but then create a department team which creates another completely different site... You should just be able to select an existing SharePoint site to bind the Team to if one exists.
or at least, if you could create the Team Group site within the SharePoint site but I really think they should be the same...
A ticket has been open by Microsoft Support and they can reproduce the problem. It's an obvious bug ! if you just copy paste the link "as is" in a conversation, it will just lead you to a 404 (indeed it will stop at "/Documents" while it should be "/Documents%20Partages/...)
We are using SharePoint Team Sites and when taking Teams into use, we want to be able to link Team with an existing Team Site and that Team Site's document libraries, NOT create a new group Team Site -> We end up saving documents into two different Team Site document libraries (the existing, "old" one and the "new" one created together with the Team). This is a BIG hurdle, hope you will get this solved soon!
It is possible right now. + -> SrarePoint -> URL -> Choose folder
There one big limitation. You choose top folder only. Subfolders are not allowed.