This week at the Microsoft Ignite conference we introduced the new PnP Provisioning Engine.
What is PnP?
Before talking about the new Provisioning Engine, let me introduce you the PnP group.
PnP stands for Office 365 Developers Patterns and Practices. I’m proud of being
one of the PnP Core Team members, and what we do is supporting developers adopting the new Cloud App Model, moving from the Full Trust Code model, and to
develop SharePoint Add-Ins (formerly known as SharePoint Apps), as well as Office 365 Apps. We do have a site, which is hosted by Microsoft,
and we do have a GitHub repository. Please, have a look at what we do,
and feel free to contribute.
What is the PnP Provisioning Engine?
And now, let’s talk about the PnP Provisioning Engine. It is an engine, which is available for FREE and under an
Open Source model, to easily do Remote Provisioning (via CSOM) of artifacts in SharePoint on-premises and
SharePoint Online. Would you like to learn more about this topic? Please, read this white paper and let us know your feedbacks!
How can you get it?
You like it? I guess so … You can get the new PnP Provisioning Engine in many different ways, depending on your needs.
If you plan to use the engine within PowerShell, you can install the PowerShell extensions that we provide (thanks to Erwin van Hunen). Those PowerShell extensions are available here. You can download the extensions for SharePoint Online (v16) or for SharePoint on-premises (v15).
Another option is to get the OfficeDev PnP Core library as a NuGet Package in Microsoft Visual Studio. We do still have a library for on-premises, and another for the cloud.
Lastly, you can download the engine (including its source code) from the OfficeDev PnP repository on github. The PnP Provisioning Engine is in the Framework/Provisioning folder. We have both the monthly release (master branch) and the “under development” release (dev branch).