Updated link to scanner

Author: jansenbe

docs/transform/modernize-branding.md

@@ -13,7 +13,7 @@ Next to these master pages and alternate CSS settings, you could have used a cla
 
 ## Detect sites that use master pages or alternate CSS
 
-The recommended approach to find out which sites use a custom master page or use the alternate CSS option is to run the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization). This tool performs a deep analysis of all the sites in your tenant and creates reports that give you details about sites that still have incompatible master pages or alternate CSS settings. Based on the scanner output, you can remediate these sites.
+The recommended approach to find out which sites use a custom master page or use the alternate CSS option is to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner). This tool performs a deep analysis of all the sites in your tenant and creates reports that give you details about sites that still have incompatible master pages or alternate CSS settings. Based on the scanner output, you can remediate these sites.
 
 ### Revert back to the default configuration
 

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

@@ -7,7 +7,7 @@ ms.prod: sharepoint
 
 # Analyze and use the scanner data
 
-To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your sites for being connected to an Office 365 group. The scanner, as of version 1.5, will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
+To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://aka.ms/sppnp-modernizationscanner) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your sites for being connected to an Office 365 group. The scanner, as of version 1.5, will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
 
 ## Using the "Office 365 Group Connection Readiness" report
 

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

@@ -55,7 +55,7 @@ Getting familiar with what group-connection does to your site is important, and
 
 The user interface option shown in the previous section is not suitable if you want to group-connect hundreds of site collections. At that point, using an API to programmatically do this makes a lot of sense. But before doing that, it's best to verify which sites are ready to be group-connected because not all sites are suitable for this.
 
-To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. This link contains all the details needed to run the scanner. After you've run the scanner go the [Understand and process the scanner results](modernize-connect-to-office365-group-scanner.md) article to analyze the scan results.
+To help you understand which sites are ready to be group-connected, you can use the [SharePoint Modernization Scanner](https://aka.ms/sppnp-modernizationscanner) to analyze your environment. This link contains all the details needed to run the scanner. After you've run the scanner go the [Understand and process the scanner results](modernize-connect-to-office365-group-scanner.md) article to analyze the scan results.
 
 ### Step 3: Modernize your sites
 

docs/transform/modernize-customizations.md

@@ -17,7 +17,7 @@ This article gives an overview of the customizations that are not compatible wit
 
 This section focuses on customizations that you might have implemented in your lists and libraries. SharePoint automatically falls back to the classic list and library user interface when it detects an incompatible customization. Therefore, it's important to address these customizations if you want to get a 100% modern experience.
 
-To get an understanding of the modern user interface compatibility of your lists and libraries, use the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization).
+To get an understanding of the modern user interface compatibility of your lists and libraries, use the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner).
 
 ### JSLink
 

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

@@ -7,7 +7,7 @@ ms.prod: sharepoint
 
 # Analyze and use the scanner data
 
-To help you with the modernization of your classic publishing portals, you can use the [SharePoint Modernization Scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to help with the modernization of your publishing portals. The scanner, as of version 1.6, will generate an Excel report plus several CSV files containing classic publishing portal information. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
+To help you with the modernization of your classic publishing portals, you can use the [SharePoint Modernization Scanner](https://aka.ms/sppnp-modernizationscanner) to analyze your environment. Use this article to understand how you can use the scanner output to help with the modernization of your publishing portals. The scanner, as of version 1.6, will generate an Excel report plus several CSV files containing classic publishing portal information. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
 
 ## Using the "Office 365 Publishing Portal Transformation Readiness" report
 

docs/transform/modernize-publishing-portal.md

@@ -9,11 +9,11 @@ ms.prod: sharepoint
 
 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 to Modern experience in SharePoint](https://docs.microsoft.com/en-us/sharepoint/guide-to-sharepoint-modern-experience).
 
-Before modernizing your classic publishing portals it's useful to understand which publishing features are used and for that you can use the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization). Using this scanner you can scan your complete tenant or a subset of site collections for their readiness in three categories: "Office 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.
+Before modernizing your classic publishing portals 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: "Office 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 to Modern experience in SharePoint](https://docs.microsoft.com/en-us/sharepoint/guide-to-sharepoint-modern-experience)
-- [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization)
+- [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner)

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

@@ -11,12 +11,12 @@ The modern list and library experience is enabled by default and for most custom
 
 ## Approach 1: the default approach
 
-In this approach we leave the modern list and library experience active at tenant level but do run the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to understand which lists are not yet ready for the modern experience. If a site contains multiple of these lists or if the users of a given site are not yet ready for modern you can selectively disable the modern experience for that site. This gives you the needed time to remediate the lists or to educate the users so that later on you can enable the modern experience again.
+In this approach we leave the modern list and library experience active at tenant level but do run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) to understand which lists are not yet ready for the modern experience. If a site contains multiple of these lists or if the users of a given site are not yet ready for modern you can selectively disable the modern experience for that site. This gives you the needed time to remediate the lists or to educate the users so that later on you can enable the modern experience again.
 
 ![The default approach](media/modernize/modernuirollout_1.png)
 
 ## Approach 2: the "full control" approach
 
-If you want to only enable the modern list and library experience after you've ensured the lists and your users are ready for it you can opt for this "full control" approach. You start with disabling the modern list experience at tenant level (you probably already did this) and then enable the modern experience site level blocking feature. Once you've blocked the modern experience for all sites you can enable modern at tenant level. At this point all sites will still use the classic list experience but it does allow you to run the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) and remediate the needed lists. Once the lists and your users are ready you can selectively again disable the modern experience site level blocking feature. Recommended is to do this work in a number of waves until all sites are using the modern list and library experience.
+If you want to only enable the modern list and library experience after you've ensured the lists and your users are ready for it you can opt for this "full control" approach. You start with disabling the modern list experience at tenant level (you probably already did this) and then enable the modern experience site level blocking feature. Once you've blocked the modern experience for all sites you can enable modern at tenant level. At this point all sites will still use the classic list experience but it does allow you to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) and remediate the needed lists. Once the lists and your users are ready you can selectively again disable the modern experience site level blocking feature. Recommended is to do this work in a number of waves until all sites are using the modern list and library experience.
 
 ![The full control approach](media/modernize/modernuirollout_2.png)

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

@@ -7,7 +7,7 @@ ms.prod: sharepoint
 
 # Analyze and use the scanner data
 
-To help you understand which lists are not ready to use the modern list and library user interface, you can use the  [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your lists for getting the most out of the modern list and library experience. The scanner will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
+To help you understand which lists are not ready to use the modern list and library user interface, you can use the  [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) to analyze your environment. Use this article to understand how you can use the scanner output to prepare your lists for getting the most out of the modern list and library experience. The scanner will generate an Excel report plus several CSV files. It's recommended to use the Excel based dashboard to review the scanner data and when needed use the CSV data for more in depth data.
 
 ## Using the "Modern UI List readiness" report
 

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

@@ -39,7 +39,7 @@ In this section you'll learn how to identify lists which are not showing as a mo
 
 ## Detect lists and libraries not available in the modern user interface
 
-The recommended approach to detect which lists and libraries are not available in the modern user interface is to run the [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization). This tool performs a deep analysis of all the lists and libraries in your tenant, and creates reports that give you details about which lists and libraries do not show in modern, and more importantly, why that happens. Based on the scanner output, you can unblock lists and libraries by remediating them, which is covered in the next section.
+The recommended approach to detect which lists and libraries are not available in the modern user interface is to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner). This tool performs a deep analysis of all the lists and libraries in your tenant, and creates reports that give you details about which lists and libraries do not show in modern, and more importantly, why that happens. Based on the scanner output, you can unblock lists and libraries by remediating them, which is covered in the next section.
 
 ## Unblock lists and libraries
 

docs/transform/modernize-userinterface.md

@@ -34,7 +34,7 @@ With the right teams looped in and educated, you can continue to the next step.
 
 ## Step 2: Analyze your site collections
 
-Your tenant might contain thousands of site collections, so which of these site collections are good candidates to modernize and which aren't? To help you understand the readiness of your existing sites, Microsoft has built a scanner: The [SharePoint Modernization scanner](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.Modernization) provides a detailed analysis of your site's readiness for connecting to an Office 365 group, helps you get a deep understanding of the modern user interface compatibility of your lists and libraries and also performs a detailed analysis of the wiki and web part pages in your environment to prepare you for a page modernization. These outcomes can be used initially to drive remediation work, followed later on by migration work. If your focus is to **transform your site pages**,  to **transform your lists and libraries** or to **connect your sites to an Office 365 group** then use this scanner.
+Your tenant might contain thousands of site collections, so which of these site collections are good candidates to modernize and which aren't? To help you understand the readiness of your existing sites, Microsoft has built a scanner: The [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) provides a detailed analysis of your site's readiness for connecting to an Office 365 group, helps you get a deep understanding of the modern user interface compatibility of your lists and libraries and also performs a detailed analysis of the wiki and web part pages in your environment to prepare you for a page modernization. These outcomes can be used initially to drive remediation work, followed later on by migration work. If your focus is to **transform your site pages**,  to **transform your lists and libraries** or to **connect your sites to an Office 365 group** then use this scanner.
 
 **Office 365 Group connection readiness** |
 :---------|