Merge pull request SharePoint#8039 from dereklh7/AbsoluteLink-6-6

Validation: Removed Absolute Links and Updated Descriptions.

Author: andrewconnell

docs/transform/modernize-customizations.md

@@ -1,7 +1,7 @@
 ---
 title: Modernize customizations
 description: Overview of the customizations that are not compatible with the modern user interface in SharePoint, and guidelines on how to remediate them.
-ms.date: 12/13/2018
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -118,9 +118,9 @@ In the introduction, we mentioned the common pattern of adding a site banner by
 
 To learn more about SharePoint Framework Application Customizer extensions, see:
 
-- [Build your first SharePoint Framework Extension](https://docs.microsoft.com/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension)
-- [Migrating user custom actions and ECB menu items to SharePoint Framework Extensions](https://docs.microsoft.com/sharepoint/dev/spfx/extensions/guidance/migrate-user-customactions-to-spfx-extensions)
-- [Migrating from UserCustomAction to SharePoint Framework Extensions tutorial](https://docs.microsoft.com/sharepoint/dev/spfx/extensions/guidance/migrate-from-usercustomactions-to-spfx-extensions)
+- [Build your first SharePoint Framework Extension](/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension)
+- [Migrating user custom actions and ECB menu items to SharePoint Framework Extensions](/sharepoint/dev/spfx/extensions/guidance/migrate-user-customactions-to-spfx-extensions)
+- [Migrating from UserCustomAction to SharePoint Framework Extensions tutorial](/sharepoint/dev/spfx/extensions/guidance/migrate-from-usercustomactions-to-spfx-extensions)
 
 ### Custom menu items in the site actions menu
 

docs/transform/modernize-guidance-support.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint modernization guidance - Support step
 description: MModernization offerings that IT Teams and partners can use with their customers - Support step
-ms.date: 12/06/2019
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -23,5 +23,5 @@ You’ve added a cool extension, fixed a type, fixed a bug…any contribution to
 
 What else can you consider combining with the modernization:
 
-- Make the Teams experience richer by populating the created Teams team with channels and messages. See https://docs.microsoft.com/sharepoint/dev/solution-guidance/pnp-provisioning-tenant-templates on how to get started with PnP Tenant templates that provision Teams content.
-- Create SharePoint Framework based customizations to replace existing, business critical, classic customizations. The customizations can also be hosted in Teams. See https://docs.microsoft.com/sharepoint/dev/spfx/sharepoint-framework-overview to learn more.
+- Make the Teams experience richer by populating the created Teams team with channels and messages. See /sharepoint/dev/solution-guidance/pnp-provisioning-tenant-templates on how to get started with PnP Tenant templates that provision Teams content.
+- Create SharePoint Framework based customizations to replace existing, business critical, classic customizations. The customizations can also be hosted in Teams. See /sharepoint/dev/spfx/sharepoint-framework-overview to learn more.

docs/transform/modernize-publishing-portal-scanner.md

@@ -1,7 +1,7 @@
 ---
 title: "Analyze and use the scanner data: Publishing portal scanner"
 description: Understand and process the publishing portal scanner results to help you prepare the modernization of these portals
-ms.date: 01/27/2021
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: medium
 ---
@@ -38,21 +38,21 @@ Publishing portals in this category do only have one sub site level or no sub si
 
 All the portals in this category also use structural navigation, recommended way forward here is to ensure the needed global navigation elements appear in the hub site navigation and the current navigation entries are defined in the respective communication sites (the ones replacing the sub sites).
 
-See [Planning Navigation for the modern SharePoint experience](https://docs.microsoft.com/sharepoint/plan-navigation-modern-experience) for more information.
+See [Planning Navigation for the modern SharePoint experience](/sharepoint/plan-navigation-modern-experience) for more information.
 
 #### Page layouts and publishing features
 
 All the portals in the  `Simple` complexity category only use out-of-the-box publishing portals layouts. Due to this out-of-the-box usage the future page transformation for publishing portals will be able to help with the transformation of pages based upon these page layouts.
 
 Portals having more advanced publishing features like scheduled publishing or approval workflows are not listed in this category which means that with the basic configuration you get from a communication site you should be set.
 
-See [Moving from Publishing sites to Communication sites](https://docs.microsoft.com/sharepoint/publishing-sites-classic-to-modern-experience) for more information.
+See [Moving from Publishing sites to Communication sites](/sharepoint/publishing-sites-classic-to-modern-experience) for more information.
 
 #### Portal branding
 
 The publishing portal categorization is not taking in account possible branding done via customer master pages and alternate CSS. Branding in a modern portal is fundamentally different which means that it requires work regardless of the portal complexity.
 
-See [Branding your SharePoint Online site](https://docs.microsoft.com/sharepoint/branding-sharepoint-online-sites-modern-experience) for more information.
+See [Branding your SharePoint Online site](/sharepoint/branding-sharepoint-online-sites-modern-experience) for more information.
 
 #### Multi-lingual features
 
@@ -66,21 +66,21 @@ Publishing portals in this category do only have up to three levels of sub sites
 
 Portals in this category can have managed navigation defined for either their global or current navigation. Configuring navigation based upon a termset is currently not supported in communication sites, hence you'll need to use the foreseen navigation options (hub navigation, regular communication site navigation) to reimplement your desired navigation.
 
-See [Planning Navigation for the modern SharePoint experience](https://docs.microsoft.com/sharepoint/plan-navigation-modern-experience) for more information.
+See [Planning Navigation for the modern SharePoint experience](/sharepoint/plan-navigation-modern-experience) for more information.
 
 #### Page layouts and publishing features
 
 Portals in the `Medium` complexity category can have customized page layouts, which is something that you should take over in your new modern page templates.
 
 These portals can also use more advanced publishing capabilities like an approval workflow or scheduled publishing. For the first you do have the option to configure page approval using Microsoft Flow, for the latter there's currently no out-of-the-box equivalent available.
 
-See [Moving from Publishing sites to Communication sites](https://docs.microsoft.com/sharepoint/publishing-sites-classic-to-modern-experience) for more information.
+See [Moving from Publishing sites to Communication sites](/sharepoint/publishing-sites-classic-to-modern-experience) for more information.
 
 #### Portal branding
 
 The publishing portal categorization is not taking in account possible branding done via customer master pages and alternate CSS. Branding in a modern portal is fundamentally different which means that it requires work regardless of the portal complexity.
 
-See [Branding your SharePoint Online site](https://docs.microsoft.com/sharepoint/branding-sharepoint-online-sites-modern-experience) for more information.
+See [Branding your SharePoint Online site](/sharepoint/branding-sharepoint-online-sites-modern-experience) for more information.
 
 #### Multi-lingual features
 
@@ -89,6 +89,6 @@ Portals are only in the `Medium` complexity category if they're not using multi-
 ## See also
 
 - [Modernize your classic SharePoint sites](modernize-classic-sites.md)
-- [Planning Navigation for the modern SharePoint experience](https://docs.microsoft.com/sharepoint/plan-navigation-modern-experience)
-- [Moving from Publishing sites to Communication sites](https://docs.microsoft.com/sharepoint/publishing-sites-classic-to-modern-experience)
-- [Branding your SharePoint Online site](https://docs.microsoft.com/sharepoint/branding-sharepoint-online-sites-modern-experience)
+- [Planning Navigation for the modern SharePoint experience](/sharepoint/plan-navigation-modern-experience)
+- [Moving from Publishing sites to Communication sites](/sharepoint/publishing-sites-classic-to-modern-experience)
+- [Branding your SharePoint Online site](/sharepoint/branding-sharepoint-online-sites-modern-experience)

docs/transform/modernize-publishing-portal.md

@@ -1,7 +1,7 @@
 ---
 title: Modernize classic publishing portals
 description: Modernize your classic publishing portals
-ms.date: 10/10/2019
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: medium
 ---
@@ -11,7 +11,7 @@ ms.localizationpriority: medium
 > [!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 official Microsoft support channels.
 
-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/sharepoint/guide-to-sharepoint-modern-experience). Ensuring the portal you design is healthy and does achieve the performance you desire is important, a recommended read is the [Creating and launching a healthy SharePoint portal](https://docs.microsoft.com/sharepoint/portal-health) documentation.
+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](/sharepoint/guide-to-sharepoint-modern-experience). Ensuring the portal you design is healthy and does achieve the performance you desire is important, a recommended read is the [Creating and launching a healthy SharePoint portal](/sharepoint/portal-health) documentation.
 
 ## Modernization approach
 
@@ -33,13 +33,13 @@ Classic portals typically are using deeply nested site structures as shown below
 
 In modern intranets we recommend using individual communication sites instead of sub sites (you potentially can consolidate/deprecate certain of the sub sites) and then where need create a flexible hub-spoke model by designating some site collections to be a hub and joining other site collections to that hub. Note that in these individual site collections you can still create content types (based on the modern site page) for you page meta data (e.g. using site designs one can get these content types applied to each site joining the hub). Next to content types you can also have modern page templates as a lightweight alternative for the classic page layouts.
 
-![Modern Information architecture](media/modernize/modern information architecture.png)
+![Diagram of modern information architecture, showing the relationship between the Intranet, Finance, and I T.](media/modernize/modern information architecture.png)
 
 As preparation for designing your new information architecture it's useful to understand which publishing features are used and for that you can use the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner). Using this scanner you can scan your complete tenant or a subset of site collections for their readiness in three categories: "Microsoft 365 group connection", "Page transformation" and "Publishing Portal Modernization". You can have the scanner collect all three categories but you can also scope the scan to only get the "Publishing Portal Modernization" information by using the `-m PublishingOnly` option. The result of the scan will be an Excel based dashboard which will allow you to analyze the publishing feature usage of all your portals.
 
 ![publishing portal dashboard](media/modernize/publishingscanner_1.png)
 
 ## See also
 
-- [Guide to the Modern experience in SharePoint](https://docs.microsoft.com/sharepoint/guide-to-sharepoint-modern-experience)
+- [Guide to the Modern experience in SharePoint](/sharepoint/guide-to-sharepoint-modern-experience)
 - [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner)

docs/transform/modernize-scanner-reports-groupconnect.md

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner reports for the Microsoft 365 group connect scanner mode
 description: Explains the Microsoft 365 group connect output created by the modernization scanner
-ms.date: 02/14/2020
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -132,4 +132,4 @@ Load the ModernizationUserCustomActionScanResults.csv into Microsoft Excel and u
 
 Filter | Takeaway
 ---------|----------
-**No filter** | Will give you one row per found incompatible user custom action. You need to assess how important these user custom actions are: if they are business critical it's better to either build an alternative [SharePoint Framework extension](https://docs.microsoft.com/sharepoint/dev/spfx/extensions/overview-extensions) or move the site back to "classic"
+**No filter** | Will give you one row per found incompatible user custom action. You need to assess how important these user custom actions are: if they are business critical it's better to either build an alternative [SharePoint Framework extension](/sharepoint/dev/spfx/extensions/overview-extensions) or move the site back to "classic"

docs/transform/modernize-scanner-reports-lists.md

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner reports for the Lists scanner mode
 description: Explains the lists output created by the modernization scanner
-ms.date: 10/23/2019
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -26,7 +26,7 @@ Column | Description
 **Blocked at site level** | TRUE if the list is blocked because the **site** scoped feature (E3540C7D-6BEA-403C-A224-1A12EAFEE4C4) was enabled.
 **Blocked at web level** | TRUE if the list is blocked because the **web** scoped feature (52E14B6F-B1BB-4969-B89B-C4FAA56745EF) was enabled.
 **Blocked at list level** | TRUE if the user changed the list experience setting to "classic experience".
-**List page render type** | The value of the PageRenderType property as explained in [docs.microsoft.com](https://docs.microsoft.com/sharepoint/dev/solution-guidance/modern-experience-customizations-customize-lists-and-libraries#programmatically-detect-if-your-librarylist-will-be-shown-using-modern-or-classic).
+**List page render type** | The value of the PageRenderType property as explained in [docs.microsoft.com](/sharepoint/dev/solution-guidance/modern-experience-customizations-customize-lists-and-libraries#programmatically-detect-if-your-librarylist-will-be-shown-using-modern-or-classic).
 **List experience** | The set list experience setting: auto (default), modern or classic. 
 **Blocked by not being able to load page** | TRUE if the page associated with the list default view could not be loaded.
 **Blocked by not being able to load page exception** | The error that was triggered when the page could not be loaded.

docs/transform/modernize-scanner-reports.md

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner reports
 description: Explains the output created by the modernization scanner
-ms.date: 02/04/2021
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -34,7 +34,7 @@ After the run you'll find a new sub folder (e.g. 636530041937506713) which conta
 
 Report | Include in following modes | Content
 ---------|----------|----------
-**Microsoft 365 group Connection Readiness.xlsx** | All modes | The report that summarizes the data you need to know to help with assessing the readiness for "Microsoft 365 group connection" also called "Groupify". Checkout [Analyze and use the scanner data](https://docs.microsoft.com/sharepoint/dev/transform/modernize-connect-to-office365-group-scanner) to learn more on how to use the scanner results.
+**Microsoft 365 group Connection Readiness.xlsx** | All modes | The report that summarizes the data you need to know to help with assessing the readiness for "Microsoft 365 group connection" also called "Groupify". Checkout [Analyze and use the scanner data](/sharepoint/dev/transform/modernize-connect-to-office365-group-scanner) to learn more on how to use the scanner results.
 **office 365 List Readiness.xlsx** | Full, ListOnly | An Excel report using PowerQuery and PowerPivot to make it easier for to analyze the lists that will not render in modern.
 **Office 365 Page Transformation Readiness.xlsx** | Full, PageOnly| The report that summarizes the data you need to know to help with assessing the readiness for "Page Transformation" (so transforming from classic pages into modern pages)
 **Office 365 Publishing Portal Transformation Readiness.xlsx** | Full, PublishingOnly, PublishingWithPagesOnly | The report that summarizes the data you need to understand for transforming your classic publishing portals into modern publishing portals

docs/transform/modernize-scanner.md

@@ -1,7 +1,7 @@
 ---
 title: The SharePoint modernization scanner
 description: Gets you started with the SharePoint modernization scanner
-ms.date: 05/20/2022
+ms.date: 06/07/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -21,7 +21,7 @@ This scanner is a key tool to use if you want to prepare for modernizing your cl
 
 > [!NOTE]
 > - Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool), this tool will step by step replace the still relevant features from the modernization scanner
-> - The SharePoint modernization scanner only is supported for running against SharePoint Online. For scanning on-premises SharePoint you can consider using the [SharePoint Migration Assessment Tool](https://docs.microsoft.com/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) (SMAT) or the [Microsoft Consulting Services open source version of the on-premises workflow scanner](https://github.com/microsoft/SP-Server-Workflow-Scanner).
+> - The SharePoint modernization scanner only is supported for running against SharePoint Online. For scanning on-premises SharePoint you can consider using the [SharePoint Migration Assessment Tool](/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) (SMAT) or the [Microsoft Consulting Services open source version of the on-premises workflow scanner](https://github.com/microsoft/SP-Server-Workflow-Scanner).
 >
 > [!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 official Microsoft support channels.