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.
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.
Guilherme de Paula commented
It would be a GREAT improvement to have the tabs, like a browser, to be able to use the chat and open a sharepoint file at the same time.
Adam Brown commented
Lists are everything! Please do this :)
Ivar Kukk commented
Also if you choose some Sharepoint folder and get even Teams link, it doesn't work when you want to add this folder with Teams link to a Sharepoint TAB.
Ivan Corberó commented
@Supathra, I agree @Isaac Chua's comment (a thumbsup is missing here). In fact I first voted the one he appoints.
To both requests I would add the possibility to give a SP Group the ID of a Team and save this way the need to different places to update arrivals and departures.
Indeed, SP was first and there are already many teams working around their shared workingspaces... making it easy would to extend a site with the current Team's new features... at end, be able to embed, among other things, the main chat timeline in a webpage.
Ivan Corberó commented
Great to discover that we can add a SPO as a tab. However I agree with all those colleagues who wish to embed, show, add ... (whatever you want to call it) the timeline of a Team conversation in a SharePoint Page. By extension, maybe available already, to authorize users by adding the team ID at the security layout of any site.
I agree too with the comment of anothe colleague asking for a way to connect all the chat applications you already have (Skype, Groups, Slack, ... ) and get a single timeline. It sounds a bit Tolkien... but not in fact "...a ring to rule theme all" but connectors to have all what happening at a glance... something like what in Twitter when following a #tag but with the ability to post at all timelines associated (maybe this should be posted in another thread)
Since GA, in french version at least, sharepoint link to folder does not work. It does not translate space into %20 for instance, and thus they are unusable.
Would love to have the ability to add Conversations into a SP page as an app or webpart. (As a replacement for discussions)
Fernando Calix commented
Share documents from sharepoint in the chat general without create a copy