Description

This solution shows how to use Office 365 Dev PnP remote provisioning engine in context of provider hosted app. Engine can be used from managed code or using PowerShell and the exact UX is dependent on the deployment functional requirements. In this recording the engine is used to provision needed customizations to site collections, which are provisioned using asynchronous provisioning pattern.

Video shows following topics

How use PnP provisioning engine from provider hosted app

How to use PnP provisioning engine from console application

How to extract delta changes from existing "template site" compared to out of the box team sites

Notice. there are small hiccups in this video due resource constraints. Video will be re-recorded in later stage based on availability. We did not want to postpone the demonstration publishing for later stage.

@cveld:It works on premise although it seems there may be issues with the Term Store. Web service calls to the term store failed with unauthorized errors. I don't know if that was an issue with my configuration or a current limitation of the engine. Either way, I anticipate it will work better with SP2016. I could not get it to work with a publishing site, but it did work against a team site. It did not copy apps, but I would expect this since the apps need to be trusted to the site where they are running. I also found limitations with certain list definitions such as out of box tasks and calendars. Custom lists seemed to work well. I hope future releases will take current limitations into account.

So would this allow us to create a provider hosted app that provides a site creation and configuration solution that could be distributed via the Office 365 app store? I note that your actual app that was deployed did not ask for full control permissions which we currently require and therefore stops us getting app store approval.