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.
Q1: Make this a configurable option.
Q2:10. Without this every team we are creating gets a ghost sharepoint site (the teams one)
Q3: No, we go to office 365 as we want Out of the Box solutions not additional customisation to make Office 365 integrations better (this is not about integrating 3rd party components to office 365)
Does this mean those libraries will be searchable??? (please, please, please!)
I seem to have the opposite issue. I'm trying to add a specific sharepoint folder and it is only allowing me to point to the entire document library
Bill Blais commented
Q1: Not automatically, but as an option.
Q2: Most important. Period. Without this, it is an adoption and management nightmare.
Q3: Definitely not. This should be a simple default choice when creating a new team, something like the following:
Would you like to:
A) Create a new Sharepoint site
B) Connect to an existing Sharepoint site (if users click B, they should then be presented a second question of whether or not to create channels for existing folders)
Require Scenario A. However, Q1 no because I want to control the channels and not all libraries will need a channel. Q2 10. Q3 potentially however that is putting the responsibility back onto the customer. Alternatively, provide the details on a tested procedure.
Scenario A - like i mentioned my company like so many others have followed best practice in having sharepoint governance, 0365 groups contradict this and like someone else mentioned its crazy and unmanageable. we must be able to point to sharepoint sites.
thanks for response.
I would like to be able to choose subsites too.
Q1. No auto channels. I think auto tabs based on the SP site (or subsite) especially the document libraries.
Q2. Important. 10. Site Mailboxes can no longer be created.
Q3. I don't know. I really want to edit the tabs of a channel I think.
Concerning Scenario B. It is a helpful feature which was rolled out & appreciated. Several times as a team is working on a project, we want to reference and collaborate with an existing location and don't want to copy content in to the team. This is useful, just not the root request.
Please pass on the appreciation for the work going in to Teams and o365 solutions, it is all coming together. ...speaking as a user of course, just not fast enough! :)
Scenario A is the paramount point. For the simple reason that if you have been using SP already, introducing teams for an effort creates a new SP site at the root, which is crazy confusing and miserable to manage.
Answers to your question:
1. How about just a drop down that says 'make new site' or 'connect to existing'. set the path. agree to whatever permissions / alterations are necessary.
-- this gives us 'files' to the default document library
-- anything else is using the SharePoint link or other features.
2. 10+ I can't continue to adopt at our present rate, the duplicate SP sites and split knowledge is horrible
3. ....Given the narrative use case I presented, my sense is this should be core / OOTB. but i see the point of how best to tackle this now / later.
Thank you so much for re-opening this!
Ivan Corberó commented
Hello Suphatra, hello all,
I believe that we started/voted this petition because most of us are working in/for a platform that already contains hundreds of sites (and in my case thousands sub-sites!). Some of them belong to departments existing for years.
I wanted to mention that my curiosity on this tool started at the moment that, as central support for SPO, an end user asked me about the best chat app to add in a site, something more dynamical than the good old discussion boards. I believe that Microsoft, after so many years of experience in chat applications, will find the best GUI to manage all generated conversations (historical, logs, search, apps for mobile devices and other OSs).
Hence, the scenario my company prefers is A rather than B, that we already tested and, as someone already said, may cause confusion.
As long you enable linking the creation of a new Team to an existing site or (remark) sub-site I don’t mind if, for the case, a new library is created to log all the activity related to the new team: chats, notes, calendar and documents by default.
And what about making feasible to link several new teams to a single site or sub-site then? In fact we are all claiming to link to an existing site, but what about if the site is already linked to another team?
(I’d like to remind that my interest to this awesome tool started at the moment I was looking for a chat tool to embed in an existing site and empower the users to use it from their mobile devices)
9/10 …then improve the GUI of the app for mobile devices that is too poor :-D!
Not sure about what you mean with the “Create Channels API”. In a quick search I could not find clear information about it; but I rather prefer something easy to explain to the end users of my company, directly in the webform at the moment to create a new team.
Blessings from Barcelona!
Q1: I have an existing sharepoint site collection for all my corporate teams today so all I expect is a new document library to be created for the new team and teams to control folders being put in it for each new channel created in the Teams application. The only change from the current functionality is that instead of creating a completely new site for the document library then you just create a new document library on the existing site. You would obviously need to change the permissions on the newly created document library so the team could contribute to it but should be as simple as breaking inheritance and adding the O365 group with contribute permissions. (I am open to any solution that allows me not to make new SharePoint sites collections for every team!)
Q2: 9, the only item I want more is private channels.
Q3: Nope, would be nice if there was a create teams powershell with this as an option.
Scenario A would be my vote. As my company does not use O365 Groups.
When creating a new team, I would like to connect to an existing SP site of my choice. Connect to my existing Team Site Notebook, Planner Board, and email address (if applicable).
1. No I wouldn't. I would expect it to ask me what channels I would like to create, and then suggest based on the document library folders.
2. 9 out of 10. If I can create a team based on an existing SharePoint site, without worrying about extra sites, notebooks and whatnot being created in the background. All I want is Teams.
3. Probably not, but I cannot answer this question ad I'm not an admin
Andreas Roth commented
No, I want to create the channels myself.
When selecting an existing SP Site, I want to select a DocumentLibrary(optional: A Folder in this Library) which then appears under the "Files" Tab.
It would be nice to freely change the used source DocumentLibrary(optional: Folder) shown in the "Files" tab.
This would create even more options for possible SharePoint Setups in the future.
Mike Mealey commented
Scenario A, Q1: yes, Q2: 10, Q3: probably not
Rob Simmes commented
We already have many SharePoint sites created under https://***.sharepoint.com/teams... It isn't productive to create a new site just so that it works within the "Teams App UI" however, I have asked everyone to install "Teams" and start using it for the various initiatives. I don't want to merely point an existing SharePoint site to teams. When creating a Team site, I want it to have the option to use my existing https://***.sharepoint.com/teams.. SharePoints instead of creating a new one.
A little bit from column A and B.
Our departments already have SharePoint Sites. We are looking to Match these existing SharePoint Sites to the newly created 0365 Groups/Teams
Currently when you create a Group/Team you get a premade SharePoint site but there does not appear to be a way to opt out of that premade and link an already existing site. The problem with the premade site is that it does not link to the existing SP Site Collections. This is making our a headache of our auditing.
Scenario A: When creating a new Team, you want to be able to point an existing SharePoint site to that Team without having to migrate the site over. (For example, currently when you create a new Team, we let you elect an existing O365 Group during team creation so it automatically ports all the people into the new Team.)
Q1 "SP library to auto-generate channels in accordance to the folder structure" - YES, our current API process generates nested teamsites at a specific url like xxx1.onmicrosoft.com/Projects/ClientX/SiteY/Project########
Q1 "What would you expect to happen if you selected an existing SP site in the team creation process" -- Ideally we could add/create/extend Teams to existing teamsite URLs
Q2 " How important is this to you" 10 (currently we ad hoc create a parallel unlinked Teams which is making a mess of our project structure)
Q3 "Create Channels API" -- if we could integrate the creation of the Teams with our existing API calls to create the team site, this would be acceptable
Thanks so much!
Matthew Parowski commented
We were looking for a variation on Scenario A, since our concern is mainly about file storage. I can see this going two ways, and it would nice to have a choice: (A1) When creating a Team, point to an existing document library on an existing SharePoint site as the repository for "Files" associated with the Team, and let the Team use that in the way it uses SharePoint in the current architecture. If there are other (hidden) libraries or lists that need to be created to add a team, that's fine. (A2) When creating a Team, point to an existing Site and have the Team create everything it needs within that site, including the document library. It's fine if the Team creation process creates a new document library within the site for this purpose. Permission to the files (including the Team files) to be driven by the existing SharePoint site permissions structure; no need for the permissions to be driven by the Team membership.
Q1: We have two use cases for different types of collaboration. In one of them (and the more urgent), it's fine if the channels continue to create folders within the "Files" space within the Document Library, but it would be nice to have the option to have files tied to different document libraries. In our other BYOS use case, we have existing sites with a lot of different document libraries, each of which have different permissions. In this case, what we would probably want to do is create a different Team associated with each Document Library (until Teams is able to manage permissions on Channels within the team). In both of these cases, permissions to the files should be driven by the permissions configured on the SharePoint site, since we generally want content on these sites to be searchable/discoverable by people outside of the Team proper.
Q2: 9 - having Teams store files on a site with wider-access-than-the-Team-list permissions is critical to our corporate information security framework.
Q3: Channels is much less of an issue for us than the default "Files".
We are already experimenting with Scenario B as a workaround to our needs, linking to existing SharePoint document libraries as a "Tab", but the inability to remove the "Files" tab causes confusion for users.
Jeff Allen commented
Scenario B to connect to an existing SP site.
I don't personally have a need for scenario A, it is Scenario B that for me needs to be further explored and defined.
"be able to add an existing SP site as a tab into a channel" is option B, but that can be many things, right?
Rarely would I want a tab to just be an entire sharepoint site - but if I did, I could use the existing web view tab and accomplish that (and indeed in some channels I do exactly this).
But a SharePoint site is really a collection of apps right? What I think Option B needs to be expanded into, is Tab support for these various SharePoint apps *AND* a philosophy that for *all* SharePoint App-Based Tabs there is ALWAYS an option to select an existing one rather than just always create new.
It is not particularly important to me what is happening on the back end between the Team and the SharePoint site and the Group etc etc. I just want to be able to say (in any channel, on any Team in my org) "this specific SharePoint resource is important to this channel and should be a tab." - and today the ability to do this is very hodgepodge.
Here is a rundown of SharePoint apps and their support as Tabs in the current state, ordered by their own frequency of use for myself:
* SharePoint Lists. Currently no real support for Tabs at all. Only option is to use Web Site tab and link to the list. This is way better than nothing but native support of lists as tabs would be neat.
* SharePoint Document Libraries - *Already fully supported!* in fact this has been supported since launch of Public Preview. Great job on this implementation guys!! This implementation should be the model for *all your other SharePoint apps tabs!*
* SharePoint OneNote Notebooks - You guys are *so close* here - if you simply had the create Notes tab UI mimic the SharePoint Document Library UI *exactly* it would be perfect. Right now you only allow creating a new notebook. Let me just give you the URL of an existing Notebook in SharePoint please!!
I hope this helps!