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.
As far as I understand this is possible to do for SharePoint online site when you create a new team. There is a link called "Looks like you're an admin of a group. You can add Microsoft Teams functionality without changing the existing group. Yes, add Microsoft Teams functionality" and when you click it you will see the list of existing SharePoint groups.
In this case Teams doesn't create a new ShP site, but attaches to the one associated with the group.
I tried adding only one folder from existing SharePoint group but end up with the whole library... Help!
Any updates on this? My SharePoint sites and Teams sites sprawl is getting out of hand. I'm almost about to boycott O365 all together because there are so many disconnects now.
Any news on this topic. We are don't like the idea to have out file repositorys split between SharePoint and Teams. Makes no sense
Jose Carlos Garcia Sogo commented
We also need to bring in our existing infrastructure (Sharepoint sites) into Teams for this to work in our organization. Creating new Teams with its own site works only for a limited amount of cases.
What's the latest on this "Upgrade"? This would be a HUGE help to my organization!
Bob McKeating commented
Its now a month since the last post is there an update or reference to the sharepoint uservoice planner item?
John, I think she means 'modern site' and 'O365 group', she just mixed it up a bit. When you create a O365 group, modern site is created automatically. Not really know what Suphatra means with 'it can be easily converted into a team in Teams' because it can't (well it can but not easily and without API :)), but may be she will clarify.
Hi Suphatra, I don't know what is meant by a Modern Group (I can't find any information on it anywhere) but this review doesn't look like it's going to provide the flexibility needed for Teams to be used in existing environments. E.g. Link a Channel to a specific folder.
If I can't bring along my existing infrastructure, Teams remains unusable...
David Harbert commented
Have we thought about users that already have both.
we have a SharePoint Team Site we use per our customer.
In using Teams we now have another O365 Group per customer.
In a perfect world I would like to move from the new O365 Group back to real SharePoint Team Site without; losing files, conversations history, Teams setup (tabs), O365 Group email address.
Basic intelligent merge where during merge process I can choose what is primary of each O365 feature (e.g SharePoint Team Site or the Office 365 Group site under Team). Then anywhere there are config such as email I can elect which to keep or keep multiple. Then when comes to content merge, replace, add into folders, etc.
@suphatra Do you have an idea of the timeline for this upgrade? Thanks!
Josiah Thomas commented
This is a must
any update on planned? its now over 4 months since this item was marked planned.
is there an ETA for Planned?
Hi Suphatra, are you considering working on this soon? We like Teams a lot but we're really getting problems with our data structure because its not linked to our originary sharepoint site.
Given last post on this was June 22 any progress on your discussions with the sharepoint team to firm up the plan?
As i want Microsoft Teams integration with SharePoint online ,I am trying to access MS teams group in RSS feed web part with the help of "Get a link to the team" URL.
But web-part will raise an error of "Object moved Object moved to here".
Do you have any solution with respect to this issue.
I'd very very happy if you could allow us to link to individual folders rather than to entire libaries, i.e. General -> Folder X rather than to General only. That way I can share individual (sub-) folders with others in my team.
Here is my use case, which I suspect others are facing as well, along with my current work-around:
* I don't want our users to save their files in lots of different SharePoint sites, which makes it harder to find things. I want them to save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
* We have already created and used for years an awesome SharePoint document library with a taxonomy managed metadata and views everyone loves
* Therefore, in Teams, I want users to only be able to upload files to our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically (accessed through the Files tab in teams)
Here are the problems I faced that Microsoft could fix, and the workarounds I did to get it to (kind of) work the way I wanted it to -- you're welcome, Microsoft Team users :)
Problem 1: When I add our existing SharePoint document library in a tab, it does not include the fields and metadata I need.
Workaround 1: Create a new tab not as a SharePoint site, but instead add it as an ordinary website, and put in the URL of your document library. (The UI is not ideal, since there is a left hand nav bar in teams I have to do more scrolling to the right to see all of the SharePoint Document Library view, but at least we can access our views and metadata.)
Problem 2a: I can't hide the default File tab. This means that, instead of going to the new tab I created above to get to our existing SharePoint site, some users will see the files tab and upload file to it, leaving a mess ("wait, did I add the file to my new Team file area or to my existing SharePoint document library?")
Problem 2b: I can't change it so that, when you click on the default Microsoft Teams File tab and upload a file, it actually gets saved in our existing SharePoint Document Library instead of the automatically created new Microsoft Team site.
Workaround 2: In the Team File area, I add a link that goes to the URL of my existing SharePoint document library. I name the link "Use this link to the place to save files." I think click on the top nav bar item Open in SharePoint, and from there I clicked on Site Permissions, and set Site Members' permissions to Read-Only.
Result: Users save their files in our existing SharePoint sites, not in the new SharePoint site that Microsoft Teams created automatically when I created the team, and users have full access to the taxonomy, metadata and views they already know and love from their existing SharePoint site.