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.
Add to scenario B:
Connect/point to a specific folder in an existing SP Site.
Karen Abbott commented
Scenario B - We almost have this now, but we can't remove or stop Teams from creating a Files tab/folder per channel. Give us the option when setting it up to create this or not and that would solve a lot of our problems. Also we can't link a tab to a folder within a document library only to the top level of that library.
Scenario A - This is about a 6 for us. We'd rather move onto Groups but there are some sites that are too large and old to bother moving. But it would be good to have it automatically port over the members of the sites. If we had the solutions to scenario B as described above then we wouldn't need it to copy the file structure.
Connect to SharePoint document library sub-folder/file and list!
Duncan Drury commented
Q1 - not necessary - the folder structure was set up years ago, and there are hundreds of them that don't reflect how we work today.
Q2 - 9
Q3 - Creative Channels API? What is that? Seriously, we aren't going to learn something new just to make existing docs and folders available to in the Teams interface. We need a simple solution.
The way Teams works right now, it is fine if your real world team has just started and doesn't have any docs - the way the team works can be influenced by how Teams works. But for teams that already decided how they work, with hundreds of docs - Teams needs to be flexible to how they already work.
So let me create a Team without creating a new Sharepoint site, because I already have a Sharepoint site that is doing fine. I just want to integrate Teams into it.
Harald W. commented
1 Vote for Scenario B! But I think, we have it already. Merging SharePoinit site members an Team members is not a key issue.
Tarik Kranda commented
We are also seeking for Scenario A;
A1: I would not expect Teams to auto-generate all folder structure automatically, since there are folders good for Teams integration unlike some other not good candidates to integrate. It would be nice to be able to have a list to select some of them as a step of New Teams Creation Wizard. So this would be up to user just by selecting All or eliminate some of them. For new folders which will be created on SP site by time, there maybe an option to bind them or unbind them to Teams.
A2: 3. This is not so cruical for us at the moment. Integration of Teams to existing O365 group resolved the ciritical part for us at least. We are using O365 groups mostly now.
A3: I did not experience Create Channel API yet, so can not give correct scoring.
B, especially if combined with the point Chris Tobler made "How can I remove the default Files in Teams?" It would do no good to add sharepoint document library as a channel, if some people were saving things there and others were saving in the default team files area. We would like to replace the functionality, so it they click on the team files area it instead shows them, and save to, the sharepoint folder of your choice.
Scenario A for me as well.
Q1 - Auto-generation should give the option to bring each existing SharePoint libary in as a Teams tab.
Q2 - 9; my initial implementation has resulted in duplication of existing SharePoint sites for each project, as well as a separate Team/Group. I would love to consolidate this (beyond adding the SharePoint "tab" manually to the new group.
Q3 - Don't think so
For me it is Scenario A with Q1 functionality as an option for the user to select.
Q2 = 9 we do not want a proliferation of Group sites when our business teams already have existing SharePoint sites they have been using and simply want to add Teams functionality on top of them.
Q3 = No.
I'm looking for something similar to Scenario A. But, I don't have an existing O365 group for my current SharePoint sites. I would like the members of the existing SharePoint site to be members of the Team and the owners of the Site to be owners of the Team. I want Teams to create folders in the document library for Channels. I don't want to have to write any code to make this happen.
Chris Tobler commented
How can I remove the default Files in Teams?
J Berry commented
My company have hundreds of SharePoint sites already in use. With the introduction of this functionality it would be great if it could fully integrate into the existing site, rather than creating a new site collection with just a button to show a document library. Most of these sites have content in calendars, lists, pages, etc, all of which still want to be accessible. And we DON'T want a second site collection created for every existing site that might want this functionality. My request, and my understanding from the original suggestion, is that it would be good if the team element could be added on to an existing site collection, avoiding duplication of sites and providing a fully integrated experience.
Karen Abbott commented
We're also in the situation where we want to link to folders rather than libraries.
Kim Lichttenegger commented
Hi Suphatra: I tried using this feature, but it doesn't allow me to go to a subfolder within Sharepoint. Only the top level folders. For instance, within my Sharepoint site, I can link to a folder called "Program & Project docs" but not to a specific project folder within that one.
This IS NOT completed! The suggestion is to integrate teams into an existing SharePoint Online site. vs Creating a new site when a Team is created!
Daniel Marin commented
my apologies for my english.
i had troubles with this issue as well, my solutions for this is open the sharepoint folders as a website tab, i know is not the best solutions but work meanwhile microsoft add the correct solution.
hope this will be useful for all of you
@suphatra what exactly did you guys change? this functunality is what we had before when you said this suggestion was completed. I will reiterate what others have said, THIS IS NOT WHAT THIS SUGGESTION IS ABOUT.
1) When making a Team, you should be able to choose an existing SharePoint site and there by:
a) the existing SharePoint document library would become the Files tab in Teams,
2) The existing onenote library would become a tab in Teams,
3) The existing calendar (ehem) would become a calendar in Teams,
In short, a lot of us have existing sharepoint sites that we use on a daily basis. Why would we want 2 sharepoint sites with 2 document libraries for the same project. For example, I have project x with an existing sharepoint site with thousands of existing documents in a library. I want to make a team. Now I have project x sharepoint site and project x team sharepoint site with one doc. library containing those thousands of files and the team doc library with zero. This makes no sense.
Yes, you can add the existing doc library as a tab within the Team. What you have done (which I'm still unsure of what has changed) is only that. You have not done the above, you have not allowed the creation of a sharepoint tab based upon a specific folder within an existing sharepoint document library, and you have not allowed the sending of hyperlinked docs within Teams. Isn't the whole point of SharePoint/OneDrive/O365 is to prevent file duplication and the emailing of files to people? The solution within Teams promotes duplicative files and sharepoint sites for essentially no reason.
Need to be able to link to a folder, rather than a document library! Our document library has folders that are 10-deep... this is a major oversight.
Suphatra - this is not what the what idea described .... - Looks like you completely misunderstanding what people need or you never created a Team in your own application.
Creating new team is going to generate new site collection - named by the name of your team - this is the way you have to create teams by your design. Idea / ticket was to give ability to create team from already existing site (believe or not, people could have some sites already in place before you created Teams :) ).
Then, when you have your team and new site created, Teams are generating subfolders connected with channels - lets say you create Channel "Developers", people are using it, and then you figure out you need to change the name to better reflect a cause - this would be "Dev - Web" - but you want to keep history of it so you don't want new channel. So now you have a channel named "Dev-web" connected with a folder "Developers". We want to change this relation - we want to change those default assignments - not libraries itself because channels are pointing to folders not libraries.
This is I guess very obvious for so many users, it looks like you don't understand the way users work with Teams unfortunately :(
Please change status of this Idea as it is not even close to the solution.
Close - but not close enough unfortunately! And, as a result, still unusable for us... We need to be able to link channels to folders - not sites or Libraries.
When adding a Sharepoint Tab, the dialog states that you can add a link to a Site or Folder. But you can't link to a folder.
Microsoft Dynamics CRM creates folders in a Document Library in SharePoint. Teams needs to be able to link to a folder to be compatible with other Microsoft products! A few years after it was originally requested, OneDrive for Business finally made folder level processing a possibility in the last few weeks. Hopefully it won't be years before the same functionality comes to Teams.