07-14-2017 05:06 AM
07-14-2017 05:06 AM
All, I managed to preven the creation of a Team (based on powershell), BUT is there also a way that you can create a Team BUT prevent the automatic creation of the underlying Sharepoint site ?
Every new Team creates a new Sharepoint site and this is something we want to control or prevent.
07-14-2017 05:25 AM
No, that is not currently possible. Every team needs a place to put their files and the SharePoint site is provided to fulfill that need. There is a new option to allow people to use other file stores (Box, DropBox, Google Files, and Sharefile), and that can be blocked, but you cannot block the default SharePoint option. See https://support.office.com/en-us/article/Administrator-settings-for-Microsoft-Teams-3966a3f5-7e0f-4e... for the instructions on how to disable the other services.
I'm curious, why would you want to block the SP site option? This provides extensive integration with many of the other features in O365.
07-14-2017 05:48 AM
07-14-2017 06:00 AM
Tnx for the insight ! Indeed, most teams would need files (storage), but we want to control that upfront and we require some flexibility:
- some teams do not need files/SP sites
- some teams need simple SP sites
- some teams need more complex/complete SP sites
- some teams would work on the same SP site
So the most "simple" solution would be to not create a SP site automatically and after the creation of the team, manually link the (already existing) SP site to a team (which you can already).
Main reasons why we do not want automatic creation of SP sites:
- we have specific Sharepoint templates already available depending the team, so we would like to (re-)use the existing ones
- prevent the creation of a lot of SP sites, which we cannot control (admins even do not see them?)
- creation of folder(s) per channel on a Sharepoint is not best practice
Hope it helps !
07-14-2017 06:56 AM
07-14-2017 07:02 AM - edited 07-14-2017 07:03 AM
:) Thanks for the advice.
I know the O365 Groups implications, but "hoped" that would be configurable ;)
I also thought I had the solution by linking a newly created Team to an existing O365 Group, but even in that case, a new SP site is created :(
07-23-2017 03:29 AM
It might be the case that you get more control over what Office 365 resources are automatically created in the future but for now this part of the product is on automatic pilot. I really don't see an issue because few resources are consumed if the SPO site is not used and anyway, Microsoft delivers those resources. The other thing to consider is that Teams is still evolving and changes that you make to configure the creation of Teams in the way that you describe might end up breaking something in the future. I would accept what you have now and keep a watching brief on what develops in terms of configurability in the future. Or do what lots of people do - come to Ignite, find an engineer working on your favorite product, and badger them to know what's happening.
07-24-2017 12:01 AM
Thanks for the insights ... would love to attend Ignite, but we have some budget constraints in Europe right now.
05-08-2018 10:56 AM
I know this is an old post, however this is the issue with the auto-creation of the SharePoint site with Teams.
I want to structure my intranet the way I want. For example, I have an IT Site and sub-sites underneath, like HelpDesk, Infrastructure, DBA's, etc.. The way Teams work currently does not allow me to select a sub-site upon creation, so, I would have a repository for "Infrastructure" in 2 different locations.
Root site (IT) - Teams Repository Location
Sub-Site (Infrastructure) - Where I need my repository for Infrastructure.
Team is connected to Root site (IT) with an infrastructure folder, plus there is a whole infrastructure site that I want to have set up. This leads to confusion and messy management of content.
05-24-2018 02:08 AM
I'm also just beginning to look at this Jeremy, but from reading various articles, the view seems to be that Microsoft don't want people using sub-sites any longer, they expect you to flatten the structure and use hub sites to pull together the various sites. This avoids you having a subsite for say IT that needs to move from a parent site of Finance to Operations (because of a business restructure), instead Finance/Operations/IT would all just be regular sites, and you'd simply change the hubsite links to move IT from Finance to Operations...
07-13-2018 10:38 AM