Provisioning documentation polishing and adding two new articles to TOC

Author: VesaJuvonen

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

@@ -9,6 +9,9 @@ localization_priority: Priority
 
 This article introduces the PnP provisioning engine, which was originally released in April 2015 within the [OfficeDev PnP](../community/community.md) project, and which is updated on a monthly basis in alignment with the release schedule of the Office Dev PnP Core Library. 
 
+> [!NOTE] 
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 <a name="thegoal"> </a>
 
 ## The goal

docs/solution-guidance/pnp-provisioning-engine-and-the-core-library.md

@@ -7,7 +7,11 @@ localization_priority: Priority
 
 # PnP provisioning engine and the Core library
 
-The PnP provisioning engine is the heart of the provisioning framework, and at its foundation is the OfficeDevPnP.Core library. The provisioning engine is part of the Core library and it leverages the Core library extensions in the implementation of provisioning tasks. 
+The PnP provisioning engine is the heart of the provisioning framework, and at its foundation is the OfficeDevPnP.Core library. The provisioning engine is part of the Core library and it leverages the Core library extensions in the implementation of provisioning tasks.
+
+> [!NOTE] 
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 
 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.
 

docs/solution-guidance/pnp-provisioning-framework.md

@@ -9,6 +9,9 @@ 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] 
+> PnP remote provisioning is an open-source solution 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.

docs/solution-guidance/pnp-provisioning-schema.md

@@ -9,6 +9,9 @@ localization_priority: Priority
 
 As you learned in [PnP provisioning framework](pnp-provisioning-framework.md) and elsewhere, the format for provisioning templates has been decoupled from the persistence format so that you can use any format you prefer. Nevertheless, because using the XML provisioning schema for persisting templates is such a common scenario, we're providing some additional information about how to use the XML schema to serialize and save your provisioning templates.
 
+> [!NOTE] 
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 > [!IMPORTANT] 
 > While the provisioning schema obviously supports XML serialization of provisioning templates, it also provides the structure for serialization in JSON format. More generally, the schema provides the model for defining provisioning structures.
 

docs/solution-guidance/pnp-provisioning-tenant-templates.md

@@ -9,10 +9,12 @@ localization_priority: Priority
 
 Think of Tenant Templates as an extension on top of PnP Provisioning or Site Templates. Instead of just provisioning artifacts to a site, you can now create sites, create teams, provision Azure AD entries, provision taxonomy etc.
 
+> [!NOTE]
+> PnP Provisioning Tenant Templates is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 > [!NOTE] 
 > A good resource for tenant templates is the [PnP Provisioning Templates Repository](https://github.com/sharepoint/sp-dev-provisioning-templates) which contains all the templates used in the lookbook service at https://lookbook.microsoft.com. You'll find a tenant folder, and in there several folders, each containing a template. In the subfolders you will find a source folder. In the source folder you'll find a template.xml file which is a tenant template.
 
-
 ## The Sequence
 
 A sequence is a driver to create site collections and optional subsites. Notice that a sequence is only able to create so-called 'modern site': a communication site, a modern team site with a connected O365 group or a modern team without a connected O365 group.
@@ -73,7 +75,7 @@ You can easily configure a team to be created:
 
   The above sample creates a team, adds a channel, and adds 2 tabs to the channel.
 
-  ## See also
+## 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) 

docs/solution-guidance/pnp-remote-provisioning.md

@@ -9,6 +9,9 @@ localization_priority: Priority
 
 The current recommendation when it comes to provisioning artifacts like sites, lists, content types, pages is to use something called "remote provisioning". In a nutshell, remote provisioning means that you utilize one of the available APIs (SharePoint REST, the SharePoint Client Side Object Model or the Microsoft Graph) to create those artifacts. Your code runs on your own machine or on a separate server.
 
+> [!NOTE]
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 In order for you to create a repeatable process, with known parameters, the [SharePoint Developer Community](../community/community.md) created an engine, called the PnP Provisioning Engine, which allows you to easily create templates and apply those templates to sites or your tenant. The PnP Provisioning Engine can be called from C# code or by using PnP PowerShell.
 
 See the following resources for more information:

docs/solution-guidance/provisioning-console-application-sample.md

@@ -12,12 +12,15 @@ To support the new add-in model, the Office 365 Developer Patterns and Practices
 - Persist the model as a provisioning template. 
 - Apply the custom template to new or existing site collections as needed.
 
+> [!NOTE] 
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 In this sample, we create a basic console application that implements classes in the provisioning PnP Core library to enable the PnP provisioning engine to complete these essential provisioning tasks: 
 
 - Design and model your site customization. This can be a new site design, or you can point to an existing site and save it as a provisioning template.
 - Save and persist the site model as a provisioning template so that you can reuse it.
 - Apply the provisioning template to a new or existing site collection.
-    
+
 > [!NOTE] 
 > This sample walkthrough is a companion to a sample currently available on GitHub at [Getting Started with the PnP provisioning engine](https://github.com/SharePoint/PnP/tree/master/Samples/Provisioning.Framework.Console). The code (Program.cs) and solution files for the sample are available for download. There also is a 20-minute video presentation of this process (with slightly different code) available on the Microsoft Channel 9 site, [Getting Started with the PnP provisioning engine](https://channel9.msdn.com/blogs/OfficeDevPnP/Getting-Started-with-PnP-Provisioning-Engine).
 

docs/solution-guidance/the-pnp-office-open-xml-file-format.md

@@ -9,6 +9,9 @@ localization_priority: Priority
 
 If you have a template which contains file references (through the ```<pnp:Files />``` element) you will have to distribute both the xml file _and_ the files that are referred to. While this of course works, it is very easy to miss files when copying them to another ___location.
 
+> [!NOTE] 
+> PnP remote provisioning is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.
+
 For this reason we introduced a specific Office Open XML format called a 'pnp file'. Effectively it is a zip file with a specific structure in it. If you rename the .pnp file to have a .zip extension you can simply open the file and have a look in it.
 
 ![Contents of a PnP file](./media/the-pnp-office-open-xml-file-format/figure1-contents-of-file.png)

docs/toc.yml

@@ -1752,8 +1752,12 @@
       href: solution-guidance/pnp-provisioning-framework.md
     - name: PnP provisioning engine and the Core library
       href: solution-guidance/pnp-provisioning-engine-and-the-core-library.md
+    - name: Provisioning Tenant Templates
+      href: solution-guidance/pnp-provisioning-tenant-templates.md
+    - name: PnP Open XML File format
+      href: solution-guidance/the-pnp-office-open-xml-file-format.md
     - name: PnP provisioning schema
-      href: solution-guidance/pnp-provisioning-schema.md
+      href: solution-guidance/pnp-provisioning-schema.md      
     - name: Provisioning console application sample
       href: solution-guidance/provisioning-console-application-sample.md
   - name: PnP remote timer job framework