Teamsite created with Office 365 groups - how to DISABLE subsite permissions ?

[Rochen Ghisaidoobe]

Hi everyone,

as everyone knows together with the creation of an Office 365 group also more stuff is being provisioned, like a sitemailbox, SharePoint site, Planner, team. 

We have an issue with the SharePoint site provisioned in this way, cause it is possible to create below this teamsite also a subsite (with the choice of different OOB templates). 

We have an urgent requirement to disable the creation of subsites for sites created via Office 365 groups. 

How can we achieve this other then let our businesses not be owner of the Office 365 group (and therefore not owner of the SharePoint site? Creative solutions are also welcome :)

Regards,

Rochen

[#2]

To be clear, Office 365 Groups DO NOT create site mailbox and every Office 365 Groups comes with a full SharePoint teamsite (you cannot disable the SP provisioning since that's what all workloads use to store documents for instance: Outlook, Planner, Yammer, Teams, etc.)

[#3]

Might I ask you why do you want to disable subsite creation in the context of a Team? Technically it's feasible to do this, but yoo will need to break the security model you have in place with Teams (built on topo of Groups) that it's not advisable

[#4]

Hi Juan,

To elaborate a bit why this is an urgent request. 

1)

The permissions from the teamsite provisioned with Office 365 groups is managed via Office 365 groups. When creating a subsite currently the site owner has the  possibility to break inheritance, and create a subsite, with three separate SharePoint groups (owner, members, visitors). You can create more groups or even custom permission levels and attach to these groups (classic sharepoint behavior).

So the whole idea of setting permissions via Office 365 groups (only) will be broken if users will use this option. And then you can say: just train them to not to do this, but within an enterprise with the expectation of 1000+ site collections very soon, this is not realistic to expect end users will not do this. Therefore we require to enforce this to disable subsite creation (or disable breaking of inheritence...)

2) very bad user experience:

teamsite from the site collection has a complete different experience as the "classic" teamsite. This classic teamsite is the one which will be provisioned currently when creating a subsite.

Rochen