Skip to main content

Automate SharePoint Site Creation with PowerShell and PnP

Creating new SharePoint sites while maintaining a consistent look and feel can be challenging. Fortunately, with PowerShell and the PnP (Patterns and Practices) framework, we can automate the process of backing up a site template and applying it to a new site. This blog post will guide you through the necessary steps.

Prerequisites

Before you begin, ensure you have the following:

  • SharePoint Online Management Shell
  • PnP PowerShell module installed
  • Appropriate permissions to access the SharePoint site and admin center

Step-by-Step Guide

1. Backup the Site Template

First, you need to connect to the source site and back up its template.

# Source Site URL input
$SourceSiteURL = Read-Host "Enter Source Site URL"

# Path to XML file
$SchmaXMLPath = ""

# Connect to PnP Online to take template backup
Connect-PnPOnline -Url $SourceSiteURL -Interactive

# Get Site Schema and save to file
Get-PnPSiteTemplate -Out ($SchmaXMLPath) -PersistBrandingFiles -PersistPublishingFiles
    

This script prompts for the source site URL, connects to it, and exports the site's schema to an XML file named . It also includes branding and publishing files in the backup.

2. Connect to the Admin Center

Next, you need to connect to the SharePoint Admin Center to create a new site.

# Take Admin center URL as input
$AdminCenterURL = Read-Host "Enter Admin Center URL"

# Connect to admin center
Connect-PnPOnline -Url $AdminCenterURL -Interactive
    

3. Create the New Site

Now, create a new SharePoint site with the specified details.

# Variables
$SiteName = Read-Host "Enter New Site Name"
$SiteURL = Read-Host "Enter New Site URL"
$SiteDescription = Read-Host "Enter New Site Description"

# Create new site
$NewWeb = New-PnPSite -Title $SiteName -Url $SiteURL -Description $SiteDescription -Type CommunicationSite
    

This script prompts for the new site's name, URL, and description, then creates a new communication site with those details.

4. Apply the Backup Template to the New Site

Finally, connect to the newly created site and apply the backup template.

# Connect to PnP Online to destination site
Connect-PnPOnline -Url $SiteURL -Interactive

# Apply Pnp Provisioning Template
Invoke-PnPSiteTemplate -Path $SchmaXMLPath -ClearNavigation
    

This script connects to the new site and applies the previously saved template, ensuring the new site has the same configuration as the source site.

Conclusion

Using this PowerShell script, you can easily back up a SharePoint site template and apply it to a new site. This ensures consistency across your SharePoint environment and saves time in setting up new sites. Remember to run these scripts with appropriate permissions and verify the applied template to ensure all customizations are in place.

If you have any questions or run into issues, feel free to leave a comment below. Happy SharePoint site creating!

Comments

Popular posts from this blog

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3 rd party portal using API’s and then bring them to SharePoint server. The first approach that I finalized was just to make BDC solution that will get data from 3 rd party portal and will deploy it to SharePoint. How to Create BDC solution in SharePoint? I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint. http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/ After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm. So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also. So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal. We can them publish that service to IIS or Server and use the servic...

SharePoint hosted apps with Angularjs

Wow.. I thought i won't be able to manage to write a blog this month. Hey guys today i am here with a something of that i have been planning since a long time. Some time back i tried to implement Angularjs with SharePoint. To be frank Angularjs is just awesome. You can have flawless feel while working with it. I don't know how will i manage to work with Angularjs in huge projects but i found it really really good to work with single page applications. Let's have a look to the classic definition of Angularjs that you find when you google for Angularjs. Angularjs "AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template language and lets you extend HTML's syntax to express your application's components clearly and succinctly. Angular's data binding and dependency injection eliminate much of the code you would otherwise have to write." SharePoint Apps SharePoint Apps, I personally found it more developer...

SPGridView control Example

We normally use asp.net gridview control as substitute to SharePoint gridview Control. Compare to asp.net gridview control SharePoint gridview provides rich functionality. Below two are the reasons that I feel to use SPGridView control instead of asp.net gridview control. 1.        SPGridView is inherit from GridView, so it will have features of GridView and also some special features that suite for SharePoint environment, so for a SharePoint web part, I suggest to use SPGridView. 2.        Also SPGridview control supports built-in SharePoint cascading style sheets, menus, sorting in SharePoint manner. In this blog I will try to show, 1.        Create SPGridView. 2.        Bind data source to SPGridView. 3.        Apply paging to SPGridView. 4.        Allow Filtering. ...