Pn p provisioning updates (SharePoint#4841)

* Added PnP Provisioning Engine Updates

* fixed typo

Author: erwinvanhunen

docs/solution-guidance/Introducing-the-PnP-Provisioning-Engine.md

@@ -0,0 +1,70 @@
+---
+title: Configurating the PnP Provisioning Engine
+description: 
+ms.date: 10/29/2019
+localization_priority: Priority
+---
+
+# Configuring the PnP Provisioning Engine
+
+Sometimes you do not want to extract all artifacts from a site, or only even a specific list. For that the PnP Provisioning Engine uses a JSON formatted configuration file which gives you detailed control over the process. 
+
+## Extraction Configuration
+
+There is a JSON schema available at https://aka.ms/sppnp-extract-configuration-schema. We will automatically update the schema referred to by that URL to a later version if new functionality comes available. 
+If you create a JSON file use a modern editor, like Visual Studio Code, and you reference this schema will there willl be intellisense and descriptions of all the properties you can set.
+
+Let's have a look at the following sample configuration
+
+```json
+{
+    "$schema":"https://aka.ms/sppnp-extract-configuration-schema",
+    "handlers": [
+        "Lists",
+        "WebSettings",
+        "Pages"
+    ]
+}
+```
+
+This will tell the engine to only extract lists, the web settings (which includes the title, logo etc.), and the home page.
+
+For some of the handlers we can specify more detail configuration options:
+
+```json
+{
+    "$schema":"https://aka.ms/sppnp-extract-configuration-schema",
+    "persistAssetFiles": true,
+    "handlers": [
+        "Lists",
+        "WebSettings",
+        "Pages"
+    ],
+    "lists": {
+        "lists": [
+            {
+                "title": "My Test List",
+                "includeItems": true,
+                "query": {
+                    "includeAttachments": true
+                }
+            }
+        ]
+    },
+    "pages": {
+        "includeAllClientSidePages": true
+    }
+}
+```
+
+Using the configuration above we limit the extraction of lists to only include the list called "My Test List". We're telling the engine that we do want to export list items to the template (they will show up as DataRow elements), and we tell the engine also to include any attachments if present. However, the engine will not download those attachments unless you set the ```persistAssetFiles``` property to ```true```.
+
+Notice that you can specify more configuration options for lists, and we advice you to explore the schema further.
+
+By default the engine only exports the home page if you specify the ```Pages``` handler. If you want to include all pages, set the ```includeAllClientSidePages``` property in the ```pages``` section to true.
+
+## See also
+
+- [SharePoint Patterns and Practices](https://github.com/SharePoint/PnP/)
+- [SharePoint Developer Group at Microsoft Tech Community](https://techcommunity.microsoft.com/t5/SharePoint-Developer/bd-p/SharePointDev) 
+- [PnP remote provisioning](pnp-remote-provisioning.md)

docs/solution-guidance/configuring-the-pnp-provisioning-engine.md

@@ -11,9 +11,6 @@ The PnP provisioning engine is the heart of the provisioning framework, and at i
 
 Comprised of extension methods on the SharePoint CSOM/REST object model, the Core library enables provisioning tasks such as enumerating and getting provisioning templates as well as storing and then applying templates to new and existing sites. It also allows you to automate provisioning tasks and to introduce coded logic into your provisioning routines.
 
-> [!NOTE]
-> Office 365 CLI is an open-source tool with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
-
 > [!NOTE] 
 > To see a video walkthrough of creating, persisting, and applying a provisioning template, go to [Getting Started with PnP provisioning engine](https://channel9.msdn.com/blogs/OfficeDevPnP/Getting-Started-with-PnP-Provisioning-Engine).
 
@@ -27,34 +24,47 @@ You can use one of two approaches for extracting your site design as a provision
 
 ### Using Windows PowerShell scripting to extract a provisioning template
 
-To use Windows PowerShell scripts with the provisioning engine, you first must download and install the PnP PowerShell cmdlets. Everything you need to run Windows PowerShell, including download and installation instructions as well as the Windows PowerShell command documentation, is available in the [SharePointPnP.PowerShell Commands](https://github.com/SharePoint/PnP-PowerShell) repository on GitHub.
+To use Windows PowerShell scripts with the provisioning engine, you first must download and install the PnP PowerShell cmdlets. Everything you need to run Windows PowerShell, including download and installation instructions as well as the Windows PowerShell command documentation, is available in the [PnP PowerShell Commands](https://github.com/SharePoint/PnP-PowerShell) repository on GitHub.
 
 > [!NOTE] 
-> The SharePointPnP.PowerShell Commands repository contains three versions of the Windows PowerShell commands MSI. Two are for on-premises use (one for SharePoint 2013 and one for SharePoint 2016), and the third one is for SharePoint Online.
+> The PnP PowerShell Commands repository contains four versions: one for SharePoint 2013, one for SharePoint 2016, one for SharePoint 2019 and one for SharePoint Online. 
+
+The recommended way to install the cmdlet is by using the PowerShell gallery:
+
+```powershell
+Install-Module -Name SharePointPnPPowerShellOnline
+```
+
+In case you want to install a version for SharePoint on-premises, substitute 'online' in the name with the respective version of SharePoint. 
+
+These are the links to the latest versions:
+
+* [SharePoint 2013](https://www.powershellgallery.com/packages/SharePointPnPPowerShell2019)
+* [SharePoint 2016](https://www.powershellgallery.com/packages/SharePointPnPPowerShell2019)
+* [SharePoint 2019](https://www.powershellgallery.com/packages/SharePointPnPPowerShell2019)
+* [SharePoint Online](https://www.powershellgallery.com/packages/SharePointPnPPowerShellOnline)
 
-The SharePointPnP.PowerShell Commands repository contains contents that enable you to build a library of Windows PowerShell commands that target SharePoint Online. The commands use CSOM and can work against both SharePoint Online and SharePoint on-premises, depending on which MSI package you install.
 
-Additionally, there is a short Channel 9 video, [Introduction to PnP PowerShell Cmdlets](https://channel9.msdn.com/blogs/OfficeDevPnP/Introduction-to-PnP-PowerShell-Cmdlets), that discusses installing the Windows PowerShell package and connecting to your Office 365 site. In addition to installation and connection activities, the video covers other valuable information about using Windows PowerShell for remote provisioning.
 
 ### Using CSOM code to extract a provisioning template
 
 To employ CSOM/REST code to extract a provisioning template, you simply create a development project by using Visual Studio or another development environment. Create any type of project—for example, a console or Windows application, or a SharePoint Add-in. After you create a development project, you must then install the Core library, which is available as a NuGet package.
 
 > [!NOTE] 
-> Instructions for locating and installing the Core library NuGet package, and a walkthrough for a remote provisioning sample console application, are available in [Provisioning console application sample](provisioning-console-application-sample.md). Note that the Core library comes in two versions: one targets SharePoint Online, SharePoint, and Office 365; and one targets SharePoint on-premises.
+> Instructions for locating and installing the Core library NuGet package, and a walkthrough for a remote provisioning sample console application, are available in [Provisioning console application sample](provisioning-console-application-sample.md). Note that the Core library comes in two versions: one targets SharePoint Online and one targets SharePoint on-premises.
 
 While detailed instructions for using CSOM are in the provisioning console application sample, the general overview is like this:
 
-1. Create a connection to Office 365.
+1. Create a connection to SharePoint Online.
 
 2. Create a **ClientContext** instance and retrieve a reference to a **Web** object.
 
 3. Use the Core library's extension method, **GetProvisioningTemplate**, to extract a **ProvisioningTemplate** object.
 
 4. Save the provisioning template instance to a file ___location of your choice by using a template provider and serialization formatter.
 
-	> [!NOTE] 
-  > Because the template provider and the serialization formatter objects can be customized, you can implement whatever persistence storage and serialization format you like. Out-of-the-box, the PnP provisioning engine provides support for file system, SharePoint, and Azure Blob storage template providers. It also supports XML and JSON serialization formatters.
+> [!NOTE] 
+> Because the template provider and the serialization formatter objects can be customized, you can implement whatever persistence storage and serialization format you like. Out-of-the-box, the PnP provisioning engine provides support for file system, SharePoint, and Azure Blob storage template providers. It also supports XML and JSON serialization formatters.
 
 You can see an example of the XML serialization output and learn more about the XML serialization schema in the [PnP provisioning schema](pnp-provisioning-schema.md) article. You also can get the schema and its documentation on GitHub: [SharePoint/PnP-Provisioning-Schema](https://github.com/SharePoint/PnP-Provisioning-Schema/). The Channel 9 video [Deep dive into PnP provisioning engine schema](https://channel9.msdn.com/blogs/OfficeDevPnP/Deep-dive-to-PnP-provisioning-engine-schema) introduces and discusses the schema.
 
@@ -85,8 +95,6 @@ ProvisioningTemplate template = ctx.Web.GetProvisioningTemplate(ptci);
 
 ### Apply the provisioning template
 
-As with extracting the provisioning template, you can apply your customized **ProvisioningTemplate** object instance by using either CSOM/REST code or Windows PowerShell commands. You can download the [SharePointPnP.PowerShell Commands](https://github.com/SharePoint/PnP-PowerShell) from the repository on GitHub.
-
 If applying the provisioning template by using extension methods of the Core library, you have a code block similar to the example here. In the example, the template is applied to the target site by using the **ApplyProvisioningTemplate** extension method of the **Web** type.
 
 ```csharp
@@ -118,16 +126,6 @@ using (var context = new ClientContext(destinationUrl))
 }
 ```
 
-<br/>
-
-After you have created a connection to SharePoint Online by using the Windows PowerShell commands, employ the **Apply-PnPProvisioningTemplate** cmdlet as shown here.
-
-```powershell
-Apply-PnPProvisioningTemplate -Path "PnP-Provisioning-File.xml"
-```
-
-Note that the `-Path` argument refers to the file path to the provisioning template file that you persisted to the file system. In the code block above, the persisted file is an XML file, but these template files can be persisted in any serialized format that you wish.
-
 ## PnP Core library
 
 The Core library (OfficeDevPnP.Core) is a CSOM/REST object model that supports the PnP provisioning framework and enables the PnP provisioning engine. It consists of several namespaces, including a set of [extension methods](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/extension-methods). These methods extend the SharePoint object model to support remote provisioning as well as objects for handling entities, timer jobs, provisioning templates, and the entirety of the provisioning framework. Table 1 lists namespaces in the Core library.

docs/solution-guidance/media/Introducing-the-PnP-Provisioning-Engine/Figure-1-SiteTemplate01.png

@@ -9,10 +9,6 @@ localization_priority: Priority
 
 The PnP provisioning framework provides a code-centric and template-based platform for provisioning your site collections. The new provisioning engine allows you to persist and reuse provisioning models in Office 365 and SharePoint Online as well as on-premises site collections.
 
-> [!NOTE]
-> Office 365 CLI is an open-source tool with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
-
-
 ## Why the new approach?
 
 With the introduction of SharePoint Add-ins and the add-in model (formerly known as the "app model"), Microsoft has moved away from sandboxed and full-trust solutions in favor of provider-hosted add-ins and on-premises solutions. These innovations have driven a retooling of the provisioning model and the introduction of a new provisioning engine.