SHARING IS CARING
Collection of tools and guidance meant to help you extend Microsoft 365 to your needs following best practices.
Don't reinvent the wheel -- focus on what truly matters for your organization.
Learn. Reuse. Share.
PATTERNS & PRACTICES COMMUNITY CALLS
BEST PRACTICES, GUIDANCE
Find guidance and best practices to help make your life easier.
SOLUTIONS, TEMPLATES, & STARTER KITS
Samples, ready-to-use solutions, templates, and starter kits.
START BUILDING
Find what you need to get started building your own solutions.
MEET THE TEAM
The PnP team is a virtual team consisting of Microsoft employees and community members focused on helping the community make the best use of Microsoft products.
We believe that by sharing guidance, tools, solutions, and samples, we better both the community itself and the quality of solutions created by the community.
This initiative is not about any one person or group of people: it is about improving things for the greater good of the community.
Want to help others too?
SUPPORTABILITY STATEMENT
Following statements apply across all of the SharePoint PnP assets, including samples, controls, component and solutions, like SharePoint Starter Kit or the PnP Provisioning Service.
The SharePoint Development Community (also known as the SharePoint PnP community) is an open-source initiative coordinated by SharePoint engineering.
This community contributes to development documentation, samples, reusable controls, and other relevant open-source initiatives related to Microsoft 365 usage and development.
Therefore it is not supported by official support channels. If the experienced issue(s) is caused by out-of-the-box API, it falls on the normal support patterns from Microsoft side.
PnP is supported in similar ways as other open source projects done by Microsoft with support from the community by the community.
There are numerous partners that utilize PnP within their solutions for customers. Support for this is provided by the Partner. When PnP material is used in deployments, we recommend being clear with your customer/deployment owner on the support model.