How to provision and deploy the PnP SharePoint Starter Kit part two

Update: The SharePoint Starter Kit is now a solution that’s available to apply from the SharePoint Online Provisioning Service:

This is second part of my two-part series on how to provision and deploy the SharePoint starter kit into your SharePoint tenant. You can read part one below:

How to provision and deploy the SharePoint Starter Kit part one

At this point all the pre-requirement steps should be completed, our Office 365 tenant should have an app catalog site, a dev site collection and a custom user profile service property.

Download the SharePoint Stater Kit

In order to deploy the SharePoint Starter Kit to your tenant you will need to clone or download a copy of the repository. I downloaded a copy of the repository and followed the steps below:

Downloading the SharePoint Starter Kit

Deploy the SharePoint Starter Kit

Now for the fun part…deploying the SharePoint Starter Kit to your tenant! Before you begin, make sure you have run the following cmdlet to connect to your tenant:


  • Change the path in PowerShell to the location where your SP Starter Kit provisioning folder is located

Set-Location -Path C:\sp-starter-kit-master\provisioning

  • Finally, in PowerShell run the following command

Apply-PnPTenantTemplate -Path starterkit.pnp

Deploying the SharePoint Starter Kit in PowerShell

Once the SharePoint Starter Kit has concluded it will provision 3 site collections as well as other tenant level settings like themes, site designs and taxonomy term sets. You will be able to access all the site collections and web parts deployed through the starter kit in your tenant either through the new SharePoint admin center or through the SharePoint app in Office 365.

References Starter Kit repository from GitHub to install the required developer tools from Microsoft to install PnP PowerShell from Microsoft – setting up your Office 365 tenant to build and deploy client-side web parts using the SharePoint Framework from Microsoft the new user profile property/ requesting API key to Alpha Vantage from GitHub commands and minimal path to success from GitHub steps added from general cascading errors from GitHub


7 thoughts on “How to provision and deploy the PnP SharePoint Starter Kit part two

  1. yannick eberle October 2, 2022 / 7:09 pm

    Please note the “Apply-PnPTenantTemplate -Path starterkit.pnp” doesnt work no more. It has been updated to invoke instead of apply


    • Anthony October 2, 2022 / 8:34 pm

      Hi Yannick, thanks for the comment! Have you got a link to the updated documentation by any chance so I can update mine in turn? Thanks Anthony


  2. Mike Blair May 5, 2022 / 7:28 pm

    Is there a way to customise the footer that is deploy. I want to change the Contoso name etc.

    Liked by 1 person

  3. Seab July 18, 2019 / 3:55 pm

    Fantastic. For a PowerShell newbie who has been customizing classic SharePoint in SPD for years, this is exactly what I needed to jump into Modern branding. Github stops at “Change to provisioning folder”, so this closed the deal. Great post! Keep it up!

    Liked by 1 person

    • sharepointstuff1 July 18, 2019 / 2:58 pm

      Hi Seab, thanks so much for the positive comment. I’m in the same position as you and often find the “minimal steps to awesome” never really do it justice.

      Appreciate the comment 🙂


  4. Diana June 1, 2019 / 12:14 am

    Gracias por el aporte !!!

    Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s