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.
same issue then Mike Weiss
Mike Weiss commented
Let's include http / https integration with this as our internal portal uses sharepoint but bc its http, i can't share the url from an internal portal page.
A migration without this option is almost impossible. This solution does unfortunately not fit into our existing sharepoint environment.
Dear Suphatra, for new projects or initiatives teams is perfect: I get a Teams, an O365 group and underlying Sharepoint site.
But what if I have a sharepoint site created earlier? I kno wI can embed doclib as tab, but How do I explain to my user, here are files from this teams underlying site and here are files from your old site, thats totally confusing.
what would even help is to be able to REMOVE native files and Wiki tab, replacing it with existing sites objects.
any progress on this? "Under review" was over a month ago
I will reiterate that of voice of 10's, 100's thousand enterprises who have followed good practice and implemented sharepoint with a level of governance on site types, that this idea of now creating groups ad-hoc as part of planner and teams completely breaks the model if you do not allow the ability for planner and team to link to existing sharepoint sites. It makes no sense. I have tried teams with my project team and the fact that the file location is not the existing sharepoint project site has caused lots of confusion and already effected user adoption of what could be a fantastic application. PLEASE PLEASE MS sort this out for planner and teams, it seems bonkers.
AJ Kelly commented
My company uses a SharePoint site collection to organize collaboration, files, calendars, etc. based on corporate division and project team. To see real value in Teams, we need to either be able point at a specific subsite (configurable when making the team and editable later) or to be able to include specific document libraries, calendars, and the like from the "Add a tab" feature.
We have spent a lot of time designing and implementing an existing Document Management infrastructure in Office365/SharePoint Online. Teams Files approach has driven a Coach and Horses through this!
When you create a Team, a new SharePoint Site is created. When you create a Channel, a new folder is created.
But we already have the Sites and Folders we need and have been successfully using for a number of years!
In order to deploy Teams, we need the OPTION to be able to link to existing artefacts within Office365 - Teams Files to Document Libraries/Folders; Teams OneNote to OneNote Section/Page.
I presume the defaults are fine for those coming new to Office365 and Teams. Integration with and adoption by existing users needs to cater for their existing infrastructure...!
Lukas Pinta commented
I already have some SharePoints sites. Each of them has members, libraries and so on. It would be usefull, if I could use this sites as a teams in MS Teams.
At the moment I can create a team with the same name as a SharePoint site, but I have to add members, libraries and other channels manually. And I don't like that. Make it easier, please.
I am also at a loss, I have a Team Site, within this site I have a folder called Social Media. Within this folder there are folders for each client.
I now in Teams want to add that client folder to each Channel so my team can go directly to the folder of the client where everything they need is located. I can't figure it out, when adding a tab it says we can use a link to a specific folder but doesn't seem to work
I have been trying to achieve this using the URL to a view, folder etc with a Website app tab, but it won't show it in a frame. When you try to do it via the SharePoint tab app, it only allows you to select a library. Extremely limited!
*** Need to link created teams with nested SP team sites of an existing specific hierarchy ***
We have an automated process by which our internal PM system creates a nested hierarchy of SP team sites like -> "Projects" -> "Clients" -> "Site" -> "Project Number" (nested sites). We need a way to add the creation of a Team to each sub-site (and integrate/link existing team sites if possible)
1) Create Team at specific path or link team to SP team site @specific path
2) Pass / match users upon creation of team site to be added to Teams (moderator and user)
3) Integrate Files/Planner/ETC components to be consistent between SP team site and Teams
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"