Site Provisioning

Site provisioning is the process of creating a new SharePoint site—team site, communication site, or hub site—along with its initial structure: lists, libraries, permissions, navigation, and branding. In modern SharePoint, sites can be provisioned in three broad ways: self-service creation by end users through the SharePoint start page or Teams, admin-driven creation through the SharePoint admin center, or automated provisioning through scripts, Power Automate flows, or third-party governance tools that enforce naming conventions, apply templates, and register metadata about the new site the moment it's created. As organizations scale past a few dozen sites, unmanaged self-service creation tends to produce 'site sprawl'—duplicate sites, inconsistent naming, and orphaned content nobody owns—which is why most mature tenants pair self-service with some layer of automated governance.

Every new site starts from a template that determines its default lists, libraries, and web parts—common options include the Team Site (backed by a Microsoft 365 Group, useful for collaborative work) and Communication Site (built for broadcasting information to a wide audience, with no group membership required). Beyond the built-in templates, organizations can define custom 'site designs' using PnP site scripts that run automatically after creation, applying a specific list of lists, columns, and configuration steps consistently every time. Hub sites add a layer above individual sites: a hub site associates related sites together for shared navigation, a common search scope, and consistent theming, so a department can have a central hub with several project sites and team sites registered underneath it, all presenting a unified navigation bar even though each is a technically independent site collection.

SharePoint admin center settings let administrators control who can create sites at all (everyone, a specific security group, or nobody without admin approval), which templates are available for self-service creation, and whether an approval workflow is required before a requested site actually gets provisioned. A common governance pattern pairs self-service creation with a Power Automate approval flow: a user requests a site through a custom form, the request routes to IT or a business sponsor for approval, and only on approval does the flow call the SharePoint REST API or PnP PowerShell to actually provision the site with the correct template, naming convention, and default owner—giving users self-service speed without losing the guardrails that prevent site sprawl.