Updates to SharePoint self-service site creation
Published Jul 26 2018 09:00 AM 49.9K Views

Empower users to create their own sites and watch their productivity soar.


Beginning in late July of 2018, we’ll begin rolling out several improvements to the SharePoint site creation experience – to empower more users and provide the right controls to admins. Included in this update are the ability to:


  • Allow users to create modern team sites even when Office 365 Group creation is disabled for them
  • Select the default language for sites at the time they’re created
  • Enable or disable admin settings to allow or disallow self-service site creation, including subsites


Let’s dive into the details…


Allow users to create modern team sites even when Office 365 Group creation is disabled for them

SharePoint admins, or Office 365 global admin, can allow their users to create SharePoint sites. They can determine what kind of sites they can create; by default, users can create communication sites and team sites (that include Office 365 groups). Previously, if Office 365 Groups creation was disabled for a set of users, those users were only able to create “classic” SharePoint team sites.


With this update, when these users click Create site from the SharePoint home page in Office 365, they’ll be able to create a modern SharePoint team site (that is not connected to an Office 365 group) or a communication site. The modern sites they create will have the modern user experiences for the home page, lists, libraries – and they are their own standalone site collections.


If a user is not enabled to create an Office 365 group, they can still create modern SharePoint sites.If a user is not enabled to create an Office 365 group, they can still create modern SharePoint sites.

Learn more about managing site creation in SharePoint Online.


Select the default language for sites at the time they’re created

A big part of business diversity is language. As companies grow across geographies, and work groups and people become more and more diverse, so, too, must the sites that support their content collaboration.


Now people can select the desired language for their site when they create it.

From the SharePoint home page, click Create site. As you name your site, select whether it’s public or private within your organization, etc. – you can now select a default language from 50 available languages. And this language can be different from the organization’s default language set at the organization level.


Site creators can select a language for their site at the same time they create it.Site creators can select a language for their site at the same time they create it.

Enable or disable admin settings to allow or disallow self-service site creation, including subsites

From an admin perspective, IT establishes both who can create Office 365 Groups and who can create SharePoint sites. With the introduction of a modern site design that does not require an Office 365 group, admins can now further enable individuals while staying within the established governance preferences of the business. This capability is reflected in an updated Site Creation settings section within the SharePoint admin center in Office 365. It, too, adjusts the choices admins have for enabling or disabling SharePoint subsites.


Site Creation updates

When you visit the SharePoint admin center in Office 365, you’ll notice the updated choices within the Settings tab (currently only visible within the classic interface of this admin center). We’ve simplified the experience by removing the hybrid option of classic and modern; the service no longer reverts to classic for some users if your goal is modern experiences for all sites. Now, if you enable users to click Create site from the SharePoint home page, you choose either modern sites or classic sites. And still, admins can route site creation through custom forms and logic if implemented or required.


The real value being that now you can allow more of your users to create modern team sites even if they are not enabled to create Office 365 Groups, all while keeping your governance plan intact.



New Site Creation and Subsite Creation options will appear in the SharePoint admin center in Office 365.New Site Creation and Subsite Creation options will appear in the SharePoint admin center in Office 365.

Subsite Creation updates

We encourage people to consider using SharePoint hub sites going forward. In the past, many organizations used subsites to create nested zones for various teams to work. However, subsites give little room for flexibility and changes to the business across projects and teams. In contrast, hub sites were designed for change and adaptability, to help organize all your sites throughout your intranet.


If your organization still uses or requires subsites, they continue to be supported. And when created, they will have a modern look & feel – yet still nested within a parent site. Simply select Team site among the list of classic site templates when you create a new subsite from the Site contents page.


We’ve made some updates to address site and information architecture as it evolves for you going forward. In the past, subsite creation settings were enabled for all SharePoint Online sites and could be disabled for Office 365 group-connected team sites. Now, admins control if, how, and where subsite creation works – by selecting one of these three options (see figure 3 above):


  • Hide the Subsite command (no matter if a site is modern or classic)
  • Show the Subsite command only within classic sites
  • Show the Subsite command for all sites


If subsites are enabled, you create them from the Site contents page and select the "Team site" template to get the modern look and feel.If subsites are enabled, you create them from the Site contents page and select the "Team site" template to get the modern look and feel.

Note: The New > Subsite option only appears as a menu option from the Site contents page of a site (accessed via the upper-right gear icon > Site contents).


Learn more about managing site creation for SharePoint in Office 365. And learn more about how to plan for SharePoint hub sites and consider moving your information architecture away from nested subsites to a more flexible, flattened structure.


Try more and more of what SharePoint offers, and let us know what you think

We encourage you to review your current site creation settings and adjust to the desired configuration for your organization.


We want to empower you and every person on your team to achieve more. Let us know what you need next. We are always open to feedback via UserVoice and continued dialog in the SharePoint community in the Microsoft Tech Community —and we always have an eye on tweets to @SharePoint. Let us know.



Mark Kashman, senior product manager – SharePoint / Microsoft [@mkashman]


Frequently Asked Questions (FAQs)

Q: When can I expect the new self-service site creation features to roll out to Office 365 customers?

A: These self-service site creation features will begin to roll out to all Targeted Release customers in late July 2018. We then are targeting end of August 2018 for complete worldwide roll out into production.

Q: Can I change the default site language after the site has been created?

A: No, this is an absolute site property, previously set by the tenant language by default. By providing this option in the updated site creation flow, your users can set an alternate language at that time, but it cannot be changed after creation.

Q: I like Easter eggs. Can I learn some fun self-service site creation trivia, so I can play to win a SharePoint and OneDrive hoodie (see Easter egg giveaway rules* below)?

  • Trivia 1: When a user’s Azure Active Directory EnableGroupCreation property is set to disabled, IT can still empower them to create modern SharePoint sites.
  • Trivia2: If subsite creation is enabled, a user will still use the classic createnewsbweb.aspx form when creating a subsite.
  • Trivia 3: Modern sites not connected to an Office 365 group, and subsites going forward, use the same STS#3 template, giving them both the latest modern sites experiences (home page, lists and libraries, etc.).

*EASTER EGG GIVEAWAY RULES | If you’re answer is “Yes” to this last FAQ, and you wish to play, tweet me (@mkashman) your best, silly sentence that uses all three bolded Easter eggs from within the guts of self-service site creation: EnableGroupCreation, createnewsbweb.aspx, and STS#3 – plus you must include this hashtag: #SPSSSC. The person whose fabulously creative tweeted sentence that gets the most likes in one day wins the SharePoint and OneDrive hoodie. Get creative. Have fun. Go!

Valued Contributor
Appreciate this information Mark. Previously, this knowledge would come from experience rather than being presented this way. Thanks!
Occasional Contributor

Is the API level support also rolled out when we try to provision modern sites ? I mean the LCID parameter , will it be respected now on when we provision it via PowerShell or CSOM or REST ?  Currently, it takes the tenant's default language.

Frequent Contributor
If you're in an organisation that isn't self-service orientated this is like nails down a blackboard. Where's the soothing benevolent dictator mode where IT and the business can create sites when appropriate and hang them within their desired information architecture? My concern is our information strategy goes from resembling neat drawers to something resembling a teenager's bedroom.

Merci @Mark Kashman we really neaded that default language setting. Other settings could be updated after the creation but not that one.


Next question is, if we create a Group connected Modern Team Site, will the mailbox default language follow the specified site language? I really hope so.




Since you are updating the admin page, can you set different paths for Communication sites (/sites) and Group connected Team Sites (/teams).


I was able to use the STS#3 template with the classic site creation commands that accept the complete site path but the process is much slower than a Group connected Team Site.


We are so close. Help us achieve more! 

Valued Contributor

Hi @Mark Kashman 

@Mark Kashman wrote:


Q: Can I change the default site language after the site has been created?

A: No, this is an absolute site property, previously set by the tenant language by default. By providing this option in the updated site creation flow, your users can set an alternate language at that time, but it cannot be changed after creation.


Are you sure that ALL new sites use the tenants default language by default? I know it has been like this previously, but for the last couple of weeks I've noticed that this isn't the case anymore - and I have been expecting some new feature regarding that.

Our tenant language is set to "German", but recently all new communication sites use "English" as their language, while Team Sites still respect the tenant setting.

Occasional Contributor

Thank you very much for this new possibility: a modern team site without O365 group! I have been waiting for this! It makes it so much easier to explain to our customer the differences and advantages of Microsoft Teams vs. SharePoint team site (without O365 Group). Now, we have a real choice between the two when deciding what is best for what use case. 

Senior Member

Will there be an option to create a modern team site without an O365 Group even if you have permission to create a group? This is possible via PowerShell, but would be nice to have a UI option as well.

Not applicable

This is great news!


For the sub site creation setting, we have this configured today:



After the new setting is available, what will our configuration be changed to?

Frequent Contributor

Sooo........use sub sites?  don't use sub sites?  Use connected groups?  Don't use connected groups?   I'm glad we get more flexibility, but it's increasingly more difficult to make recommendations to end users as the options and recommendations seem to be changing so often.  Just a week earlier the message was to never use sub sites again.  Is there a whitepaper that explains how Microsoft IT manages Groups/Team Sites/Teams/Yammer Groups?  

Valued Contributor
@Luke Hoffman I have to agree with you regarding sub sites. I feel I have given clear direction only to be contradicted by Microsoft itself. My take is Microsoft is making it possible for customers to align a 2019 on premises experience with SPO. That makes sense but it does feel like an unscripted turn.

@Mark Kashman Thank you for giving this new flexibility. Much needed. After this roll out what will be default configuration with sub site settings in the admin center?

Occasional Contributor

Hi, @Mark Kashman, I've got 2 questions:

  1. for a Modern Team site created by the end iuser not connected to an O365 Group, is there the chance to connect it lately (with the groupify feature), as it is/it will be with the classic site?
  2. If we disable the self site creation feature, is there a way for administrators (so from the central admin) to create all the 3 kind of sitess (not connected modern team site, connected modern team site, communication site)?


Not applicable

Rally nice feature! I was waiting for that since we decided to disable the modern team site creation and use only teams for collaboration.


@Tony SuttonYou can create modern teamsites without a connect Office 365 group via powershell?
How do you do this? I only find documentation on creating a communicationsite but not teamsite without group.



@Mark KashmanFor me the biggest news in this post is not self service site creation, but the fact that we can create modern teamsites without a connected group. What happens if you do have the permissions to create groups but don't want to? Will the GUI present an option at creation where you can choose to add a connected group or not?



Senior Member

@Denis Tiri https://gist.github.com/zplume/527fe5437ff3f1232d71a5c69843343c 

See "New-SPOModernTeamSite.ps1" for single site creation, or "Create-SPOModernTeamSites.ps1" if you want to pass in a CSV


@Tony Suttonthank you very much.
I didn't know about Template ID's. Checking up on them now.


<apologies, I'm not able to @ mention folks who asked questions above - hopefully you all see my replies!>


Gautam - Yes, this new site option is just another template (STS#3). Check out: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/modern-experience-customizations-p.... Also, you can set the LCID, along with other site properties, using the New-PnPTenantSite cmdlet (https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/new-pnptenantsite?view=sharepoint-...).
Benoit - No, I'm sorry the mailbox language won't follow the designated default site language setting, but that's great feedback! Same with the setting of different managed paths by template; a request we've heard and are evaluating, but it isn't available with this update.
Tony - the admin creation experience will, but self-service site creation will only provide the user with one or the other (depending on their permissions).
Kelly - if you'd previously selected "hide the subsite creation command" we continue to honor that with the update, but it now applies to all modern sites.
Luke - sorry for any confusion. We are still firmly committed to moving toward a hub-site world; the updates to subsites are strictly around creation settings - to actually to make it easier for admins to hide for *all* site templates, while still providing an option for those not ready to move fully to a hub site architecture. Same with offering the non-Group connected team site; it's to provide a modern option in self-service site creation for those customers who aren't ready to enable group creation.
Srikanth - we'll be implementing hidden as the default, but this would only affect new tenants; we aren't changing your current settings (just expanding what they do).
Barbara - for (1) - this is an option we're currently evaluating (but note that it would only be available to site collections, not subsites). For (2) - yes, these changes only apply to self-service site creation. SharePoint admins will still be able to create sites from tenant administration.
Denis - No, the self-service site creation ux will only provide the team option your eligible (group-connected or not); there won't be a choice. SharePoint admins will be able to choose which template through that experience.
Frequent Contributor

Thanks @Mark Kashman and @Sean Squires for this. However:


  1. Option to be able to create a non-group-connected modern team site for users who do have permissions, is still left desirable.
  2. Even as an admin, I cannot create a non-group-connected modern team site from the admin panel. It shows three choices: Team Site, Communication Site, and Other Options. The Team Site option does not allow for non-group connected modern team site, it forces a group even to the admin. The Other Options provides only the templates for a Document Center, Enterprise Wiki, Publishing Portal, and a Classic Team Site.


So, the admin creation experience does NOT yet allow for the non-group connected modern team site, and the self-service one does not allow for opting out of a group.



 @Sean Squires, I asked the question about mailbox language in last week's AMA and @Mark Kashman said it would flow thru https://gorovian.000webhostapp.com/?exam=t5/Shipping-SPC18-into-Production/SharePoint-self-service-site-c...


We need it because we now have to create team sites in Outlook to select language and by doing do, we cannot select a template (design).



Hi @Abhimanyu Singh - thanks for the feedback. That is correct; these updates apply directly to self-service site creation. Site creation updates for administrators will be coming soon through a separate release/update. 


Hi @Benoit Fournier - if you're talking about the language for group-related notifications (I believe that's the same one you're referring to) it is, unfortunately a different setting - but, unlike the default language for a site, this group language can be changed through group settings. Not fully automated, but getting closer! To get the desired default language for the site you'll need to create that through the SharePoint creation form. HTH!

New Contributor



I am unable to see option as Team Site (Modern - without classic experience) when I try to create subsite under Modern Team site or Communication site.

Even my options for "When users select the Create site command, create:" are different as well. Look at the screenshot. https://imgur.com/a/LAGTUla


I have targeted realease for everyone enabled. I am Global administrator. Anyone cal help if I am doing anything wrong.


Hi @Chirag Shah - you're not doing anything wrong; we're not at 100% TR yet on the admin settings update yet! I'll keep this thread apprised...should be there soon!

Occasional Contributor

In general lot of chaos and not easy to find best options from long time view.

Wihich site type we should  use for onprem migration (15k sites).

Also question can we change existing modern sites to  sites without groups ?


And most important what are the identifiers for the site types innclude hub site using ps,graph etc for professional governsnce reporting ?

Occasional Contributor

missing the default quota management for the different site types

Occasional Contributor

What is the difference between modern team site with and without a group from customer view ? Means any limitations without using groups ? 


@Heiko Fuhrmann - for migration - it really depends on the scenario, though we recommend moving to modern sites (whether group-connected or communication) if possible - as these already reflect recent updates and feature investments (as opposed to classic site templates - which are still available in SharePoint Online and have many of the modern site features).


You can "groupify" a classic team site, but no, there is no mechanism to decouple a group from its associated SharePoint site.


For identifiers, you can use the template titles available when you use a command like Get-SPOWebTemplate. Hub isn't a template, but a setting on an existing one; these can be identified via Get-SPOHubSite cmdlet. You can find the full list of available cmdlets - even PnP ones - at http://aka.ms/sppowershell. 


I'm not sure what you mean about default quota per site type. With the new pooled storage model, admins can set the limit, but only the actual storage used counts against total pooled storage - regardless of template. 



A group-less modern team site has all the same SharePoint site elements and features as the one connected to a group. All of the related group-elements, like the user membership, shared mailbox or Yammer group, and related workloads (shared Planner, etc.) are not available. HTH!

Senior Member

Hi all, do you have an ETA of the deployment of this feature to the standard release?  STS#3 is available on my tenant thru PowerShell but not in the admin portal.


Also, when creating a subsite from a site collection with STS#3 template, the webtemplate of the subsite is STS.  Do you have any plan to fix/update that as well?




@Sean Squires and @Mark Kashman 


Good news! I now see the language option for both Team and Communication sites. I tried both and it works perfectly for the Communication sites but has no effect on Team sites. Is it a bug or it is because the rollout is not completed? 


I openned a support call but they (level 1) have no clues of the status.


I also saw that we can now select the managed path of Communication sites. Thank you, thank you, thank you. 



Not applicable

Hi all,


The modern team site template was available in our tenant (as template in the central administration and as sub site template), but it disappeared last week. Does it mean there is something wrong with the template, because I can still create site collections using Powershell. Does anyone know what happened and when it will be available again? Thank you!

New Contributor

So, how exactly do I find all of the self-service site collections? They do not show up in the SharePoint Admin console. I'd like to know if users are creating these...and somehow figure out how to keep track of them.

Occasional Contributor

I'm not happy about current situation...

- MS does offer a content life cycle feature for o365 groups where SharePoint sites also included at the end , but classic sites no solution available, now on top the possibility creating modern sites without an o365 group, also this site type excluded from the retention  configuration
- you can configure on tenant level a second site admin mandatory but not used for all site templates, self service modern team site and communication template different handling, one example

- you can configure site sharing settings on tenant level (which level is allowed to set), classic sites are after creation  in status disabled, modern  sites sharing enabled if you not modify the default template and a trigger

- if you connect later a o365 group to a modern team, site, template not changed, 

- no clear identifier for scripts and automations for which app a o365 group is used (Teams Planner, site only, Yammer, PowerBI, etc)
- same with naming convention concept o365 group names, some apps, services you can configure, other not

- the script based auditing, also be able to trigger automations based on the output, more and more complex, several  tools with limitations in parallel required to make an inventory, main reason  get-spo, pnponline, get-unified group, get-teams have all different output and restrictions, for example using get-teams as Azure runbook, all the time looping with 3-4 modules

Version history
Last update:
‎Jul 25 2018 11:53 AM
Updated by: