In this PnP Web Cast we concentrated on the PnP Partner Pack, which was released as part of the Office 365 Developer Patterns and Practices (PnP) November 2015 release. PnP Partner Pack is reference solution which demonstrates different PnP techniques and it can be deployed to any Office 365 tenant and Azure subscription easily with provided scripts and documentation.
PnP Partner Pack demonstrates main topics, which are commonly used within mid-sized and enterprise deployments around Office 365 and SharePoint online. Here's list of key functionalities demonstrated in the PnP Partner Pack.
- Self service site collection provisioning with remote provisioning pattern
- Sub site provisioning using remote provisioning pattern
- "Save site as a provisioning template" capability to store any existing site as template in specific site collection or as tenant level template
- My site collections personal view
- Responsive user interface for SharePoint sites without introducing custom master page
- Sample remote timer jobs (implemented as WebJobs) for Governance rules enforcement
- Uses Office UI fabric for provider hosted app user interface elements
- Deployed as Office 365 App with app-only permissions
During this web cast we first talk about the actual content, reasoning and capabilities of the PnP Partner Pack. After this Paolo will present the PnP Partner Pack capabilities with real demo, including covering some areas of the code and technical structure. You can access PnP Partner Pack material from http://aka.ms/OfficeDevPnPPartnerPack. Here's the key resources under the PnP Partner Pack repository in the GitHub.
- Architecture and implementation details documentation
- Step-by-step configuration guidance to setup PnP Partner Pack to any Office 365 tenant with Azure subscription
We will continue gradually evolving PnP Partner Pack based on the feedback and comments from the community. You are also more than welcome to help us on evolving this solution with pull requests or suggestions using PnP Yammer group at http://aka.ms/OfficeDevPnPYammer.
You are more than welcome to use PnP Partner Pack material anyway you need in your own customizations or deployments. It can be used as a starting point for your own deployments or as a solution which demonstrates different customization options for Office 365 and SharePoint using add-in model techniques. We have already chatted about possible on-premises version setup around PnP Partner Pack, but would need your feedback on demand around this.
Video at PnP Channel 9.
PnP Partner Pack has been build using different patterns demonstrated in the PnP guidance and is using PnP Provisioning Engine as the underlying capability for extracting and applying templates using the remote provisioning pattern. If you are not familiar of the PnP Provisioning engine, we would suggest to have a look on following PnP Web Cast as the introduction.
Other techniques demonstrated by the PnP partner pack can be also found as individual samples from the PnP guidance. See following samples around the specific capabilities.
- Branding.InjectResponsiveCSS - How to add responsive capabilities to sites without introducing a custom master page
- Core.QueueWebJobUsage - Demonstration of so called async pattern with Azure Web Jobs
- OD4B.NavLinksInjection - How to add custom navigation without custom master page
- Core.SimpleTimerJob - How to build remote timer jobs with add-in model
- Core.TimerJobs.Samples - How to take advantage of PnP Remote Timer Job framework
What is Office 365 Developer Patterns and Practices (PnP) web cast series?
We have started this weekly Office 365 Developer Patterns and Practices (PnP) web cast series to cover different patterns, practices and topics around development with Office 365 and SharePoint. Majority of the topics are valid for the Office 365 and SharePoint on-premises. We will release new around 30 minute long web cast each Monday with few slides and live demo on the covered topic. All web casts are published at the PnP Channel 9 video blog with additional references on the existing materials.
PnP is community driven open source project where Microsoft and external community members are sharing their learning's around implementation practices for Office 365 and SharePoint on-premises (add-in model). Active development and contributions happen our GitHub project under Dev branch and each month there will be a master merge (monthly release) with more comprehensive testing and communications. Latest activities and future plans are covered in our monthly community calls which are open for anyone from the community. Download invite from http://aka.ms/OfficeDevPnPCall.
This is work done by the community for the community without any actual full time people. It’s been great to find both internal and external people who are willing to assist and share their learning's for the benefit of others. This way we can build on the common knowledge of us all. Currently program is facilitated by Microsoft, but already at this point we have multiple community members as part of the Core team and we are looking to extend the Core team with more community members.
If you have any questions, comments or feedback around PnP program or this blog post, please use the PnP Yammer group at http://aka.ms/OfficeDevPnPYammer.
“Sharing is caring”
Vesa Juvonen, Senior Program Manager, Office 365, Microsoft