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.
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
Office 365 groups is the barrier that is preventing my organization from being able to use MS Teams. Our IT department already supports SharePoint online, but they don't want us using Office 365 Groups.
If I could create a new Team through an existing SharePoint site, that would be perfect.
Jamie Thomson commented
Please don't do this. Please don't turn Teams into a SharePoint client. Let SharePoint do the thing (the only thing) its good at - be a document library. Let all the other "features" of SharePoint (webparts and all that other nonsense) whither and die. Please.
One of the beauties of Teams is that there is no taxonomy, please don't try and heave a SharePoint taxonomy onto it.
Love the comment below "WHY are you using uservoice when you have products that can do discussion board/forums that you own?" Newsflash, its because SharePoint is awful (and Teams gives me some hope that Microsoft seem to be realising this) and there many many people in the world that hate it.
As many have stated having two sites would be redundant and confusing, not to mention the nightmare of provisioning access and governance of proper file saving.
If a channel is deleted and no files were uploaded to the sharepoint document library folder created for the channel it should delete the folder.
Greg Short commented
I have to add my voice to embedding Teams in SharePoint. Being able to embed or add it as a webpart would keep the Slack inquires away. We are looking for an instant messenger inside of SP. Please add this part of the Enhanced integration with SharePoint.
Isaac Chua commented
@Suphatra: This issue raised previously is essentially the same as this later one which has received more votes: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/16935565-enhanced-integration-with-sharepoint
It is a very simple request actually. We have an existing SharePoint site / site collection for a project. We want to use Teams on the project. To do so, we need to create a team on Teams. We want Teams to use that same project's SharePoint site / site collection instead of creating a new site collection upon creating a new team on Teams. Having a second site collection is redundant and confusing. We want an option to select an existing site / site collection to start a new team on Teams.
As others have said it is pretty clear that we need the choice at the time of site creation:
[ ] - I want to use an existing site (brings up a site selector)
[ ] - Create a new site for this team
Kate Imholt commented
As many have pointed out, we have existing SharePoint sites. Teams requires us to create a second site rather than link to the one we already have. Having two sites is bound to create confusion, duplication and extra work.
1) Every Team automatically gets a sharepoint library. Currently I can add a new tab with the sharepoint site I want to link it to. But then there will be multiple sites associated with the team now. An ability to turn off the default team will be appreciated.
2) Ability to point each channel to a particular folder in the sharepoint library.
Matthew Parowski commented
My company provisions new SharePoint site collections (based on "SharePoint Team Sites"--not "Team SharePoint Sites") for each of our field offices using a standard set of 15 document libraries that are used to ensure that different categories of files are accessible to the right subsets of staff in each of our field offices. What we are looking for is the ability to add the Teams conversations/collaboration front-end to that existing SharePoint site collection. It would be fine if the Teams/Groups infrastructure also added a new document library for "Teams"-related files, but we have a governance structure around our SharePoint document libraries (15 of them) that we have a strong need to preserve. The single Teams site lacks sufficient corporate visibility or governance for our needs, but the collaboration features for the subset of staff who use a site are outstanding and in high demand. We are currently in a position where these groups are creating team sites on their own and then neglecting the governed SharePoint site, which creates huge audit and compliance liabilities for my company down the road, and/or a governance nightmare where we are constantly trying to force people to save files in one place and collaborate in another. The best work-around we have found so far is to create a Tab in Teams for the SharePoint site, which then shows up in an iFrame. This is tolerable, but a tighter integration would be so much more attractive.
Would be helpful to have the sharepoint tab show the homepage of the sharepoint site, not just a document library.
Suphatra, Our company uses classic sharepoint sites extensively. In order for us to start using teams we would need to be able to link a team to our existing sites. This includes the Documents and OneNote. We can not be expected to migrate these items to a new structure. We do not want the new onenote book or document library that is created with the team at all. We need a way to remove those and put our existing content in their place.
Hi there, thanks for picking it up !
My scenario is:
1. I create a new Team. what happens: a sharepoint site is being created in background. To store all the files notes and stuff from that team. right ?
2. BUT, - I have another site already, dealing with same subject, created in the past. It already has notebook, doclib, all the objects needed in Teams.
3. What I want is to be able to have this old site underlying my new Teams rather than using new one. OR, an option to switch them. I just dont want to end up with 2 sites.
Having said this, I do know about the option of embedding doclibs from other site in Teams, - thats very good, but not perfect.
Maybe some kind of migration tool would help.
Gerry McDaid commented
I agree teams would be much better if it where like a Hub for O365 everything in one place.Teams,Planner,mail,cal
Right now you can easily connect to SharePoint document libraries in every location but the top-level SharePoint site. Teams states that these files can't be displayed when the libraries are added as tabs.