PnP Remote Provisioning

  • 2 minutes to read

The current recommendation when it comes to provisioning artifacts like sites, lists, content types, pages is to use something called "remote provisioning". In a nutshell, remote provisioning means that you utilize one of the available APIs (SharePoint REST, the SharePoint Client Side Object Model or the Microsoft Graph) to create those artifacts. Your code runs on your own machine or on a separate server.

Note

PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.

In order for you to create a repeatable process, with known parameters, the SharePoint Developer Community created an engine, called the PnP Provisioning Engine, which allows you to easily create templates and apply those templates to sites or your tenant. The PnP Provisioning Engine can be called from C# code or by using PnP PowerShell.

See the following resources for more information:

PnP Remote Provisioning vs Site Designs and Site Scripts

The general recommendation is that if you can provision your artifacts with Site Scripts then you should go for Site Scripts. Keep in mind though that the PnP Provisioning Engine extends beyond the scope of just site collection artifacts and moves into the territory of provisioning Tenant scoped artifacts.

PnP remote provisioning resources

Article Description
Introducing the PnP provisioning engine Introduces the PnP provisioning engine, which was released in April 2015 within the OfficeDev PnP project, and which is updated on a monthly basis in alignment with the release schedule of the Office Dev PnP Core Library.
Configuring the PnP provisioning engine Learn how to configure the engine by using a JSON configuration file.
The PnP Office Open XML File Format Learn about the .PnP file format, which is an Office Open XML file, and how it is built up.
PnP provisioning framework Get a high-level overview of remote provisioning features available for your Office 365 and SharePoint Online site collections as well as an understanding about why creating sandboxed and full-trust solutions is no longer recommended.
PnP provisioning engine and the Core library Take a high-level look at the remote provisioning process, including a closer look at the OfficeDevPnP.Core library.
PnP provisioning schema How to use the XML schema to serialize and save your provisioning templates.
Provisioning console application sample Learn the fundamentals of using the PnP provisioning engine to create and persist, and then apply provisioning templates to new SharePoint site collections.
OfficeDevPnP.Core The Office 365 Developer PnP Core Component is an extension that encapsulates commonly used remote CSOM/REST operations as reusable extension methods to support CSOM provisioning objects.
Inside the PnP provisioning schema (video) A Microsoft Channel 9 audio/video introduction to the PnP provisioning schema delivered by Paolo Pialorsi.

See also