Over the last year or so many of my posts have been related to the PnP Provisioning Engine.

I’ve created multiple scripts to replicate my whole intranet from one tenant to another. I’ve set this all up in such a way that this would work for any intranet solution based on Office 365 or SharePoint on-premises solutions.

Big advantages of this solution:

  • It can handle multiple pages, unlike PnP out of the box
  • It can handle complex combinations of look-up fields and lookup lists
  • One click for both reading templates and applying them
  • An option to disable/enable features
  • Fixing template issues in between getting the templates and applying them without any user intervention
  • Switching between latest and older versions of PnP PowerShell

So this isn’t just about provisioning a solution, it is also about replicating your solutions between Development, Test and Production. Are you interested in this solution then please leave a comment below or contact me at Triad

While I was testing the solution Yesterday, I noticed that my pages weren’t replicated with my PnP PowerShell scripts. I had create 2 new tenants so there can’t be anything wrong with my tenants.

Quite quickly I remembered one of my previous posts about enabling scripting.

 

Then with the PowerShell scripts mentioned in my previous post, I got things up and running and my full site was replicated.

See Also

https://veenstra.me.uk/2017/03/30/office-365-sharepoint-20132016-replicating-or-migrating-sharepoint-sites/

Advertisements