SharePoint Site Templates: Standardize Enterprise Site Creation

SharePoint Site Templates: Enterprise Standardization Guide

Consistent site creation is fundamental to SharePoint governance. Without standardization, organizations end up with inconsistent branding, missing security configurations, and governance gaps that compound over time. Site templates solve this by providing pre-configured blueprints that enforce organizational standards while enabling rapid site provisioning.

This guide covers every templating approach available in SharePoint Online, from the built-in template gallery to advanced PnP provisioning and custom site designs.

---

Understanding Template Types

Built-In Site Templates

SharePoint Online includes a gallery of pre-built templates for common scenarios. These templates configure page layouts, web parts, lists, and navigation for specific use cases.

Available templates include:

• Crisis Management for emergency response coordination
• Department for departmental landing pages
• Human Resources for HR portals
• IT Help Desk for support ticket management
• Project Management for project coordination
• Event Planning for event management
• Training for learning content delivery
• Retail Management for retail operations

Built-in templates are a good starting point but cannot be customized. They provide a consistent foundation that you can modify after site creation.

Custom Site Templates (Save Site as Template)

Modern SharePoint allows saving any site as a template. This captures the site's page layouts and content, web part configurations, custom lists and libraries, navigation structure, site columns and content types, and theme settings.

To save a site as a template, go to Site Settings then select Save site as template from the gear menu. The template becomes available in the template gallery when creating new sites.

Limitations: Templates do not capture permissions, workflows, or content (only structure). Large sites may not save reliably.

Site Designs and Site Scripts

Microsoft's recommended approach for enterprise site templating uses Site Designs (the user-facing template selection) backed by Site Scripts (JSON-based configuration).

Site Designs are the templates users see when creating a new site. They include a title, description, thumbnail, and one or more associated site scripts.

Site Scripts are JSON files that define actions executed during site provisioning. Supported actions include creating lists and libraries with custom columns, applying themes, setting external sharing capability, installing SPFx solutions, triggering Power Automate flows, joining a hub site, and setting regional settings.

```json

{

"$schema": "https://developer.microsoft.com/json-schemas/sp/site-design-script-actions.schema.json",

"actions": [

{

"verb": "createSPList",

"listName": "Project Tasks",

"templateType": 171,

"subactions": [

{

"verb": "addSPField",

"fieldType": "Choice",

"displayName": "Priority",

"choices": ["Critical", "High", "Medium", "Low"]

},

{

"verb": "addSPField",

"fieldType": "User",

"displayName": "Assigned To"

}

]

},

{

"verb": "applyTheme",

"themeName": "Corporate Brand"

},

{

"verb": "setSiteExternalSharingCapability",

"capability": "ExistingExternalUserSharingOnly"

},

{

"verb": "associateHubSite",

"hubSiteId": "hub-site-guid-here"

},

{

"verb": "triggerFlow",

"url": "https://prod-xx.logic.azure.com/workflows/...",

"name": "Post-Provisioning Setup"

}

]

}

```

Deploying Site Designs via PowerShell:

```powershell

# Add the site script

$script = Get-Content "SiteScript.json" -Raw

$siteScript = Add-SPOSiteScript -Title "Enterprise Project Site Script" -Content $script

# Create the site design

Add-SPOSiteDesign -Title "Enterprise Project Site" -WebTemplate "64" -SiteScripts $siteScript.Id -Description "Standard project site with governance configurations" -PreviewImageUrl "https://contoso.sharepoint.com/SiteAssets/project-template-thumbnail.png"

```

PnP Provisioning Templates

The PnP (Patterns and Practices) provisioning engine provides the most comprehensive templating capability. PnP templates capture everything about a site including pages with full content and web parts, content types and site columns, list structures and views, navigation, theme, and regional settings, search configuration, and tenant-level artifacts.

Extracting a PnP template:

```powershell

# Connect to the source site

Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/TemplateSource" -Interactive

# Extract the template

Get-PnPSiteTemplate -Out "ProjectTemplate.xml" -Handlers Lists, ContentTypes, Fields, Pages, Navigation, SiteSecurity, Theme

```

Applying a PnP template:

```powershell

# Connect to the target site

Connect-PnPOnline -Url "https://contoso.sharepoint.com/sites/NewProject" -Interactive

# Apply the template

Invoke-PnPSiteTemplate -Path "ProjectTemplate.xml"

```

---

Enterprise Template Strategy

Template Catalog

Build a template catalog that covers your organization's common site types. A typical enterprise needs 5 to 10 templates.

Recommended templates:

• Department Portal (communication site): branded landing page, news, events, document library, quick links
• Project Site (team site): task list, document library, meeting notes, project dashboard
• Community of Practice (communication site): discussion board, resource library, event calendar
• Client Engagement (team site with restricted sharing): external sharing enabled, NDA document library, project tracker
• Policy Library (communication site): policy document library with metadata, approval workflow, version control

Template Governance

Establish a governance process for templates. Designate a template owner who maintains and updates each template. Review templates quarterly for accuracy and relevance. Test templates on a non-production site before deploying updates. Document the intended use case, target audience, and governance rules for each template.

Provisioning Workflow

For enterprise environments, combine site designs with Power Automate flows to create a governed provisioning process. The user submits a site request form specifying the purpose, owner, template, and hub association. A Power Automate flow routes the request for approval. Upon approval, the flow creates the site using PnP provisioning. Post-provisioning steps apply hub association, set permissions, and notify the requestor.

---

Template Versioning

Managing Template Updates

When organizational standards change, templates must be updated. However, updating a template does not retroactively change sites already created from it. For existing sites, apply updates using PnP provisioning scripts that target specific configuration changes.

Version control for templates:

Store template files (JSON site scripts, PnP XML templates) in a SharePoint document library or Git repository. Use version numbers in template names to track changes. Maintain a changelog documenting what changed in each version.

---

Frequently Asked Questions

Can I restrict which templates users see?

Yes. Site designs can be scoped to specific security groups. Users outside the group do not see the template when creating new sites.

Do templates work with Teams?

Team sites created through Teams use default templates. To apply custom templates to Teams-created sites, trigger a site design application via Power Automate after the team is created.

Can I include sample content in templates?

PnP templates can include page content and list items. Site designs (JSON-based) cannot include content, only structural elements. Use PnP for templates that need pre-populated content.

---

For help building an enterprise site template strategy, [contact our SharePoint team](/contact) for a governance assessment. We design template frameworks for organizations with hundreds of sites where consistency and compliance drive template requirements. Explore our [SharePoint consulting services](/services) to learn more.

Advanced Template Patterns

Template with Automated Provisioning Pipeline

For enterprise environments, build a complete provisioning pipeline that goes beyond basic templates.

The pipeline flow:

• A user submits a site request form in SharePoint
• Power Automate routes the request for approval based on the template type
• Upon approval, an Azure Function provisions the site using PnP provisioning engine
• The function applies the PnP template with full configuration including pages, lists, navigation, and content types
• Post-provisioning scripts configure hub association, apply sensitivity labels, set storage quotas, and add the site to the governance inventory
• The requestor receives a notification with the new site URL and onboarding documentation

Template Testing Framework

Before deploying template updates, test them in a development tenant or a designated test site collection. Create a template testing checklist that verifies all lists and libraries are created correctly, content types and columns are configured properly, navigation links resolve correctly, theme and branding are applied, permissions are set according to governance policy, and Power Automate flows associated with the template are functional.

Template Analytics

Track which templates are used most frequently and gather user feedback on template quality. Use this data to prioritize template improvements, retire unused templates, and identify demand for new template types.

Template Localization

For multilingual organizations, create localized versions of templates. PnP provisioning templates support parameterization, so you can create a single template with language-specific parameters for site title, list names, column display names, and navigation labels. This reduces template maintenance burden while supporting global deployments.

Template Compliance Tagging

For regulated industries, include compliance-related configuration in templates. A template for a healthcare department should automatically apply HIPAA-related sensitivity labels, configure retention policies for medical records, restrict external sharing, and enable audit logging. This ensures every new site meets compliance requirements from creation without relying on administrators to remember manual configuration steps.

Template Maintenance and Lifecycle

Quarterly Template Review

Schedule quarterly reviews of all active templates. During each review, verify that all template components (lists, libraries, columns, navigation) still function correctly after SharePoint updates. Check that branding elements (themes, logos, header settings) are current with organizational standards. Review template usage statistics to identify templates that are no longer being used. Gather feedback from site owners who recently created sites from templates to identify improvement opportunities.

Template Deprecation Process

When a template needs to be retired, follow a structured deprecation process. Announce the deprecation to all site owners with a timeline. Provide a migration path from the deprecated template to the replacement. Remove the template from the template gallery after the deprecation date. Archive the template definition (JSON, PnP XML) for reference. Document the retirement in the template registry.

Template Versioning with Source Control

Store all template definitions in a Git repository for version control. Each template change gets a commit message explaining what changed and why. Use branches for template development and merge to main only after testing. Tag releases with version numbers that correspond to template gallery versions. This approach provides a complete audit trail of template changes and enables rollback if a template update causes issues.