Today’s webinar, “Who Needs a Developer for SharePoint Provisioning,” had a great turnout and we can’t wait to host another session next month! We know there was a lot of information during the session, so here is a quick recap of SharePoint Patterns and Practices (PnP), along with the course details and recording!
What is SharePoint PnP?
As an initiative that continues to gain steam, especially over the last year with the increase adoption of Office 365 / SharePoint Online and the announcement of the SharePoint Framework, you may still be a little fuzzy on the concept and as a non-technical person I know I am, so here is a brief intro. SharePoint PnP is an open source initiative, created by Microsoft and other thought leaders in the industry. As a community-based movement, SharePoint PnP fosters, “learning’s around implementation practices for SharePoint and Office 365.” SharePoint PnP is for SharePoint 2013, 2016, and Office 365. From sharing to offering advice and best practices, the SharePoint PnP collaboration increases our knowledge and allows us to move forward with the most recent tips, modern tricks, and effective techniques for working with SharePoint and the new SharePoint Framework.
Eric’s introduction to PnP, in particular, the provisioning aspects of PnP, offers users an in-depth overview of its core components. By leveraging PnP PowerShell based on the PnP Core Components and combining it with the Remote Provisioning Schema (you can find on Github), Eric provides users with a method to repeatedly provision SharePoint. The video will give you a step-by-step overview of installing PnP PowerShell and how to run a variety of commands, usage scenarios, and PowerShell scripts.
SharePoint PnP Resources
Also, don’t forget to join us for next month’s webinar, “Your Guide to SharePoint Branding Practices,” on March 23rd at 11 AM PST. More details will be announced soon. Stay tuned and be sure to follow us on Twitter @pixelmillteam for more info and webinar announcements. Also feel free to tweet any webinar questions at us or Eric (@EricOverfield)!