Adding supportability statements

Author: jansenbe

docs/transform/modernize-branding.md

@@ -8,6 +8,9 @@ localization_priority: Priority
 
 # Modernize site branding
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 The SharePoint modern user interface handles branding differently from classic SharePoint; in particular, it simply ignores custom master pages or alternate CSS configurations (which are incompatible in the modern user interface). You can opt to leave these configurations in place in your modernized site so that it still applies to a page being shown in a classic user interface, but it's cleaner to switch back the OOB master pages and remove the alternate CSS configuration.
 
 Next to these master pages and alternate CSS settings, you could have used a classic custom theme. These classic custom themes work on both classic and modern pages, but the more future-proof model is the new tenant-controlled SharePoint theme, which obviously applies to both classic and modern pages.

docs/transform/modernize-classic-sites.md

@@ -1,7 +1,7 @@
 ---
 title: Modernize your classic SharePoint sites
 description: Steps to transform your SharePoint classic site into a modern Office 365 group-connected team site or communication site.
-ms.date: 03/04/2019
+ms.date: 10/03/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -17,6 +17,9 @@ All of this is great, but you might ask yourself, *I have lots of classic (team)
 > [!TIP]
 > You can decide which steps to run and the order in which to run them. Although there's no one-size-fits-all process to modernize your site, the following is the recommended approach.
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 > [!IMPORTANT]
 > For publishing portals (sites based upon BLANKINTERNET#0, ENTERWIKI#0, SRCHCEN#0, SRCHCENTERLITE#0, BICENTERSITE#0, POINTPUBLISHINGHUB#0, POINTPUBLISHINGTOPIC#0 or sites using the “Pages” library) it's not currently supported to connect these to an Office 365 group or to use modern pages. If you want to modernize your publishing portal it's recommended to start from a new communication site and configure that one accordingly. For more information, see [Modernize classic publishing portals](modernize-publishing-portal.md).
 

docs/transform/modernize-connect-to-office365-group.md

@@ -20,6 +20,9 @@ In this article, you'll learn how to prepare for such a bulk operation for assoc
 > [!IMPORTANT]
 > It is **not** supported to connect a Communication site to Office 365 group.
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 ## What connecting to a new Office 365 group does to your site
 
 When you connect your site to a new Office 365 group, a number of things happen:

docs/transform/modernize-customizations.md

@@ -8,6 +8,9 @@ localization_priority: Priority
 
 # Modernize customizations
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 An important aspect when modernizing a site is understanding the customizations used on that site because not all existing customizations continue to work after the site is modernized. A classic example that occurs frequently is a site banner that shows some type of company information (such as a legal notice). 
 
 This typically is realized via a user custom action that embeds JavaScript on the page, which in turn is responsible for showing the banner. This banner is visible on all classic pages, but will not be visible on modern pages. To work around this problem, you can implement the banner as a SharePoint Framework Application Customizer extension and deploy that to the tenant/site. 

docs/transform/modernize-publishing-portal.md

@@ -8,6 +8,9 @@ localization_priority: Normal
 
 # Modernize classic publishing portals
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 A classic publishing portal uses publishing functionalities like page layouts, custom branding, page approvals, audience targeting and many more. For most classic publishing portal functionalities there's a modern equivalent enabling you to build a similar modern publishing portal. This modern publishing portal will then take advantage of all the modern capabilities like beautiful pages that work on any device, flexible page approval using Microsoft Flow etc as described in the [Guide to the Modern experience in SharePoint](https://docs.microsoft.com/en-us/sharepoint/guide-to-sharepoint-modern-experience).
 
 ## Modernization approach

docs/transform/modernize-sample-scripts.md

@@ -8,4 +8,7 @@ localization_priority: Priority
 
 # Scripting your modernization tasks
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 You can modernize your sites by using the foreseen user interface options, like for group connect or page transformation (when you've installed the [Page Transformation UI solution](https://aka.ms/sppnp-pagetransformationui)). Using the user interface works great for a limited set of sites, if you have to modernize multiple sites it's recommended to automate the modernization. To help you with that you can find all our modernization tools, script and solutions in the [sp-dev-modernization](https://aka.ms/sppnp-modernization-git) open source repository, including [sample scripts that will help you automate your modernization tasks](https://aka.ms/sppnp-modernization-scripts).

docs/transform/modernize-scanner.md

@@ -22,6 +22,9 @@ This scanner is a key tool to use if you want to prepare for modernizing your cl
 > [!NOTE]
 > The SharePoint modernization scanner only is supported for running against SharePoint Online.
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 ## Step 1: Get the latest version of the SharePoint modernization scanner
 
 Since SharePoint Online continuously evolves and more and more modern capabilities are added it's important to always download the latest version of the scanner. [Download the SharePoint Modernization executable](https://github.com/SharePoint/sp-dev-modernization/blob/dev/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true) and get started. This page contains all information to get you started, but if you want to get more details then checkout the [detailed user guide](https://github.com/SharePoint/sp-dev-modernization/blob/master/Tools/SharePoint.Modernization/Modernization%20Scanner.md).

docs/transform/modernize-userinterface-lists-and-libraries.md

@@ -16,6 +16,9 @@ You can't yet transform all lists and libraries to the modern experience because
 
 - Certain types of lists and libraries can be shown in modern, but are blocked due to an incompatible configuration or customization; you can take action here.
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 ## List templates available in the modern user interface
 
 Following are the most commonly used list template types that SharePoint can currently render in a modern user interface (as of October 2018):

docs/transform/modernize-userinterface-site-pages.md

@@ -16,6 +16,9 @@ The SharePoint PnP Modernization framework ([Nuget](https://www.nuget.org/packag
 > - Page transformation today works for wiki, web part pages and publishing pages.
 > - The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 Page transformation can be used in one or more models and these models can used together:
 
 Model | Technique | Audience | Publishing Page support | Keep/Discard option | Comments

docs/transform/modernize-userinterface.md

@@ -20,6 +20,9 @@ To make the switch to a modern user interface, you need to focus on the followin
 > [!IMPORTANT]
 > The "classic" experience is not being deprecated; both "classic" and "modern" will coexist.
 
+> [!IMPORTANT]
+> Modernization tooling and all other PnP components are open-source tools backed by an active community providing support for them. There is no SLA for open-source tool support from Microsoft support.
+
 Where do you start when you want to modernize the user interface of your sites? What sites should be modernized first? These are very relevant questions and are addressed in the following steps.
 
 ## Step 1: Identify and educate stakeholders