if this might help anyone on the “Get a site provisioned using the ‘classic’ sites method – SharePoint Admin Centre, Site Collections, New Private Site – but using the Office 365 Group team site (with modern UI home page) as the template”, type angle …
How to save the team site of an Office 365 Group (Unified Group) as a template, and create sites via the “classic” provisioning process from that template
Create a Unified Group with associated team site. This team site will be used as the source for the site template.
Navigate to team site, Site Settings (Site information, View all site settings), notice Save site as template is missing.
Notice that appending _layouts/savetmpl.aspx to the URL doesn’t work, you get “Sorry, you don’t have access to this page”.
This is due to scripting being disabled in the Unified Group team site, which over-rides the SharePoint Admin Centre, Settings, Custom Script, configuration.
To enable the scripting for the site, per this article, …
… run the following PowerShell …
# Import general SPO module and connect
Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking
Connect-SPOService -Url https://yourname-admin.sharepoint.com/
Set-SPOsite “https://yourname.sharepoint.com/sites/yoursite” -DenyAddAndCustomizePages 0
Return to the Unified Group team site, Site Settings, notice Save site as template is now available.
Click Save as a template and save the site as a template.
Go to Site Settings (Site information, View all site settings), Web Designer Galleries, Solutions.
Notice the site template you just saved, click the file, Save the .wsp file locally.
Go to SharePoint Admin Centre, site collections, New, Private Site Collection, and create a site collection using Custom, <Select template later… > .
Go to the home page of the new site collection, in the Template Selection choose Solution Gallery.
In the Solution Gallery click Upload Solution, browse locally and select the .wsp file you just downloaded.
Click Activate to activate the template solution.
Return to the home page of the new site collection, the Template Selection is displayed again.
Select Custom, then your template you just uploaded.
Use the default SP groups for the site’s groups setup.
So this new site collection has the following properties: –
- The home page is a genuine Unified Group team site home page, because it is based on a template that was a Unified Group team site.
- The site collection appears in SharePoint Admin, Settings, site collections, because it was provisioned using the “classic” site collection provisioning process.
- None of the steps performed are “unsupported” by Microsoft. There was no “copy-and-paste” of the _layouts/savetmpl.aspx URL (as, for example, can be performed to save Publishing Sites as a template and thereby render them unsupported by Microsoft). Microsoft technical support confirmed this.
- The site is linked into the Unified Group that is associated with the source site of the template. Clicking on “Group Conversations” on the home page of the newly created site takes you into Outlook positioned on the Unified Group associated with the source of the template. So now instead of a 1-to-1 relationship between the Unified Group and the Site, it is 1-to-many.
- If you create sub-sites using the template, in either the source site or any site created from the template, these behave similarly i.e. all have the relevant properties 1, 3-4 above.