02-05-2019 01:34 AM
02-05-2019 01:34 AM
I am currently in the phase of analyzing the implications of rolling out Teams to be used as the main collaboration tool in our organization.
Anytime that you create a site in MS Teams a new site is created in SharePoint, I get the following questions:
- Can we avoid a site's creation when adding a new group?
- Can we link previous sites created in SharePoint with new groups? (so that we avoid sites duplication)
- Is there any documentation available for best practices and governance for this topic?
Thanks in advance!
02-05-2019 02:00 AMSolution
1: Creating a team, creates an Office 365 group which includes a SharePoint Team site! This is not optional! Also this is where Teams store its files!
2: You can create a team on an existing Office 365 groups! If its a modern team site a group was created here as well! If you are an owner of the site/group, you can go to teams - create a team and choose "create a team on existing office 365 group"
3: Documentaion on governance in teams:
02-05-2019 02:08 AM
02-05-2019 02:14 AM
Yes! Thats a good idea!
There are also alternatives as restricting group creation to a security group! The members of this group need P1 (azure AD premium) licenses though!
Also there is group expiration policys to have a look at:
Files in private chat are stores in the sharing users OneDrive!
02-05-2019 02:26 AM
02-05-2019 02:28 AM
03-20-2019 03:28 PM
@adam deltinger Hi Adam, related to this - I would still like to understand best / common practice between Teams and Sharepoint. We started out with using MS Teams. We now need a document storage location to move our 1000s of files off a network drive to and so a Sharepoint site with libraries was created by our IT dept. We then discovered that you can only link a SP library to your teams files location list (not a folder within the library) so I suggested we just use the SP site that was created when the Team was created. They (our IT dept) then advised that this might not be a good idea as should the Team be deleted so would our document repository. Seems strange to me that there might be a greater chance that someone could delete a team (that is in use all the time by the team) over a Sharepoint site.
In short - Do you know what the standard practice is? - Using the MS Teams created Sharepoint site for only team chats and adhoc files and a separate Sharepoint site for document storage or only using MS Teams and its own Sharepoint site for both?
Thanks in advance.
03-23-2019 03:26 PM
03-23-2019 04:16 PM
@anagonzalez I would agree with you , for smaller companies it might not be an issue but for larger enterprises with more then 40-50 k user's , it would create an issue and i have seen this . As lot of sites will spun , Also same way lot of corresponding office 365 groups will be created.
On the other hand if limit the group creation via Azure AD then we are limiting the capabilities of team's , as they will loose the ability to create team's on their own.
I think it is real issue which needs to be addressed.
03-23-2019 04:27 PM
04-04-2019 05:43 AM
Thanks for your insights, they've help a tremendous amount.
I found however, I don't require an Azure P1 license in order to be able to restrict who can create groups.
I create a "Group Creators" group and anyone I add inside of this (regardless of having an Azure P1 License) then has the ability to create a group - Others outside of this group cannot create a group.
Just wanted to share.