From 5c25eaa1380099bf8848657ac26dadb663c4575e Mon Sep 17 00:00:00 2001 From: titao Date: Tue, 21 Jul 2026 17:49:27 +0800 Subject: [PATCH 1/8] Archive legacy modernization scanner guidance Make Microsoft 365 Assessment the active modernization assessment entry, retain the legacy Scanner documentation under Archive, and update scenario references according to current capability coverage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/community/open-source-projects.md | 4 +- docs/features/groupify/groupify-overview.md | 4 +- docs/scenario-guidance/Branding.md | 10 +- .../modern-experience-customizations.md | 4 +- docs/toc.yml | 176 +++++++++--------- docs/transform/modernize-blogs.md | 4 +- docs/transform/modernize-branding.md | 4 +- ...nize-connect-to-office365-group-scanner.md | 4 +- .../modernize-connect-to-office365-group.md | 4 +- docs/transform/modernize-customizations.md | 4 +- .../modernize-guidance-assessment.md | 4 +- docs/transform/modernize-guidance.md | 6 +- .../modernize-publishing-portal-scanner.md | 4 +- docs/transform/modernize-publishing-portal.md | 6 +- docs/transform/modernize-scanner-faq.yml | 9 +- .../modernize-scanner-reports-blogs.md | 4 +- ...dernize-scanner-reports-customizedforms.md | 4 +- .../modernize-scanner-reports-groupconnect.md | 4 +- .../modernize-scanner-reports-infopath.md | 4 +- .../modernize-scanner-reports-lists.md | 4 +- .../modernize-scanner-reports-pages.md | 4 +- ...rnize-scanner-reports-publishingportals.md | 4 +- .../modernize-scanner-reports-workflow.md | 4 +- docs/transform/modernize-scanner-reports.md | 4 +- docs/transform/modernize-scanner.md | 43 +++-- ...serinterface-lists-and-libraries-optout.md | 4 +- ...erinterface-lists-and-libraries-rollout.md | 6 +- ...erinterface-lists-and-libraries-scanner.md | 4 +- ...rnize-userinterface-lists-and-libraries.md | 4 +- ...dernize-userinterface-site-pages-dotnet.md | 4 +- docs/transform/modernize-userinterface.md | 6 +- .../modernization-scanner-legacy.md | 2 + 32 files changed, 194 insertions(+), 162 deletions(-) create mode 100644 includes/snippets/open-source/modernization-scanner-legacy.md diff --git a/docs/community/open-source-projects.md b/docs/community/open-source-projects.md index e3f81365e0..afa1832c9d 100644 --- a/docs/community/open-source-projects.md +++ b/docs/community/open-source-projects.md @@ -1,7 +1,7 @@ --- title: SharePoint Developer Community open source projects description: Open-source projects coordinated by the SharePoint PnP initiative -ms.date: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: high --- @@ -17,7 +17,7 @@ There are numerous open-source projects that are coordinated by the SharePoint P | [Office 365 Developer PnP Core Component](https://github.com/SharePoint/PnP-Sites-Core) | An extension component that encapsulates commonly used remote CSOM/REST operations as reusable extension methods on out-of-the box CSOM objects. | | [PnP PowerShell cmdlets](/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets) | Allow you to perform complex provisioning and artifact management actions for SharePoint. The commands use CSOM and can work against both SharePoint Online as well as SharePoint on-premises. | | [PnP remote provisioning schema](https://github.com/SharePoint/PnP-provisioning-schema) | Designed to be used as remote creation instructions for the remote provisioning engine for Office 365. | -| [SharePoint Modernization tooling and guidance](https://github.com/SharePoint/sp-dev-modernization) | Tools like page transformation (classic page to modern page) and a modernization scanner do make it easy to move your classic sites into the modern SharePoint world. | +| [PnP modernization tooling and guidance](https://github.com/pnp/modernization) | Legacy SharePoint modernization tools and scripts. For new assessment work, see [Assess SharePoint modernization](../transform/assess-sharepoint-modernization.md). | | [PnPjs](https://pnp.github.io/pnpjs/) | A fluent JavaScript API for consuming SharePoint and Office 365 REST APIs in a type-safe way. | | [PnP SPFx Yeoman Generator](https://pnp.github.io/generator-spfx/) | Open-source Yeoman generator which extends out-of-the-box Yeoman generator. | | [SharePoint Framework reusable property pane controls](https://sharepoint.github.io/sp-dev-fx-property-controls) | Can be used in SharePoint Framework (SPFx) solutions. | diff --git a/docs/features/groupify/groupify-overview.md b/docs/features/groupify/groupify-overview.md index dfe641b20c..7b1ab2b422 100644 --- a/docs/features/groupify/groupify-overview.md +++ b/docs/features/groupify/groupify-overview.md @@ -1,7 +1,7 @@ --- title: Overview of the Connect to new Microsoft 365 group feature description: Augment your team site collaboration capabilities with the benefits of other group services such as Outlook, Planner, and Microsoft Teams. -ms.date: 06/28/2022 +ms.date: 07/21/2026 ms.localizationpriority: high --- @@ -33,6 +33,6 @@ After your site is connected to a Microsoft 365 group, it behaves like a modern ## See also - [Connect a classic SharePoint team site to a new Microsoft 365 group](../../transform/modernize-connect-to-office365-group.md) -- [SharePoint Modernization scanner tool](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) +- [Legacy SharePoint Modernization Scanner](../../transform/modernize-scanner.md) - [PowerShell cmdlet to connect a SharePoint team site to a new Microsoft 365 group](/powershell/module/sharepoint-online/Set-SPOSiteOffice365Group) - [Modernize your classic SharePoint sites](../../transform/modernize-classic-sites.md) diff --git a/docs/scenario-guidance/Branding.md b/docs/scenario-guidance/Branding.md index 92023d4297..3c25664eec 100644 --- a/docs/scenario-guidance/Branding.md +++ b/docs/scenario-guidance/Branding.md @@ -1,7 +1,7 @@ --- title: Scenario Guidance - Branding description: Scenario guidance on branding options with SharePoint. -ms.date: 06/28/2022 +ms.date: 07/21/2026 ms.localizationpriority: high --- # Branding @@ -53,7 +53,7 @@ In 2016, the SharePoint Online team released "modern" collaboration sites. These ### Solutions - [SharePoint Framework Extension samples](https://github.com/SharePoint/sp-dev-fx-extensions) -- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) +- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) ### Videos @@ -79,7 +79,7 @@ The classic SharePoint user experience is based on ASP.NET master pages and page ### Solutions - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive) -- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) +- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) - [PnP Starter Intranet for SharePoint 2013/2016 and SharePoint Online](https://github.com/pnp/PnP/tree/master/Solutions/Business.StarterIntranet) ### Videos @@ -160,7 +160,7 @@ Because Microsoft SharePoint is built on top of Microsoft ASP.NET, it supports m ### Solutions -- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) +- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) - [PnP PowerShell branding cmdlets](/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets#branding) - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction) @@ -194,7 +194,7 @@ Cascading style sheet (CSS) plays a large role in SharePoint branding. To succes - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive) - [Activate the PnP Responsive UI Add-on using PnP PowerShell](https://msdn.microsoft.com/pnp_powershell/enablepnpresponsiveui) - [CSS Injection Pattern sample](https://github.com/SharePoint/PnP/tree/master/Samples/Branding.CustomCSS) -- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) +- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction) ### Samples diff --git a/docs/solution-guidance/modern-experience-customizations.md b/docs/solution-guidance/modern-experience-customizations.md index 4533aebd5d..bf705a2024 100644 --- a/docs/solution-guidance/modern-experience-customizations.md +++ b/docs/solution-guidance/modern-experience-customizations.md @@ -1,7 +1,7 @@ --- title: Customizing the "modern" experiences in SharePoint Online description: An overview to get you started using the "modern" experiences in SharePoint Online. -ms.date: 06/13/2022 +ms.date: 07/21/2026 ms.localizationpriority: high --- @@ -27,7 +27,7 @@ The "modern" experiences in SharePoint Online are: If you have existing customizations that are business critical for your deployment, we recommend using the following process for adopting the "modern" experiences: 1. **Readiness**: Understand the "modern" experiences, know what features they offer, but equally important, understand which features are not (yet) available. -1. **Assess**: Assess to what extent your current customizations can work within the "modern" experience. Also assess which of your sites have customizations or features that will not work within the "modern" experiences. These sites and their customizations should be updated or need to stay in "classic". However, other sites should work just fine using the "modern" experiences. The best way to assess your compatibility with the "modern" experiences is by using the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernuiscanner). +1. **Assess**: Assess to what extent your current customizations can work within the "modern" experience. Also assess which of your sites have customizations or features that will not work within the "modern" experiences. These sites and their customizations should be updated or need to stay in "classic". However, other sites should work just fine using the "modern" experiences. Start with the [Microsoft 365 Assessment tool](../transform/assess-sharepoint-modernization.md) to evaluate the relevant modernization scenarios. 1. **Solution planning**: Plan the work required for both custom solutions and sites to prepare them to be used with the "modern" experiences. 1. **Develop and test**: Apply the needed changes to your customizations and test them. 1. **Deploy**: Roll out the updated changes to your SharePoint Online environment. diff --git a/docs/toc.yml b/docs/toc.yml index 77a5d00922..427141e568 100644 --- a/docs/toc.yml +++ b/docs/toc.yml @@ -1108,6 +1108,32 @@ items: - name: Overview href: general-development/sharepoint-development-overview.md + - name: SharePoint Modernization scanner + items: + - name: Which assessment tool should I use? + href: transform/modernize-scanner.md + - name: Understand the legacy scanner reports + items: + - name: Overview + href: transform/modernize-scanner-reports.md + - name: Microsoft 365 group connect report + href: transform/modernize-scanner-reports-groupconnect.md + - name: Modern list and libraries report + href: transform/modernize-scanner-reports-lists.md + - name: Page modernization report + href: transform/modernize-scanner-reports-pages.md + - name: Publishing portal modernization report + href: transform/modernize-scanner-reports-publishingportals.md + - name: Workflow usage report + href: transform/modernize-scanner-reports-workflow.md + - name: InfoPath usage report + href: transform/modernize-scanner-reports-infopath.md + - name: Blog usage report + href: transform/modernize-scanner-reports-blogs.md + - name: SharePoint Designer customized forms report + href: transform/modernize-scanner-reports-customizedforms.md + - name: Legacy scanner FAQ + href: transform/modernize-scanner-faq.yml - name: What's new in SharePoint Server 2019 href: general-development/sharepoint-2019-development-platform.md - name: Programming models @@ -1829,67 +1855,67 @@ href: general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md - name: Back up and restore a search service application href: general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md -- name: Scenario guidance +- name: Assess and transform classic pages + href: transform/assess-sharepoint-modernization.md items: - - name: Overview - href: solution-guidance/Office-365-development-patterns-and-practices-solution-guidance.md - - name: Assess and transform classic pages - href: transform/assess-sharepoint-modernization.md + - name: Assess classic pages + href: transform/assessment-tool-classic-pages.md items: - - name: Assess classic pages - href: transform/assessment-tool-classic-pages.md + - name: Requirements + href: transform/assessment-tool-classic-pages-requirements.md + - name: Run the assessment + href: transform/assessment-tool-classic-pages-run.md + - name: Interpret and prioritize + href: transform/assessment-tool-classic-pages-report.md + - name: Publishing page readiness + href: transform/assessment-tool-publishing-coverage.md + - name: Reference items: - - name: Requirements - href: transform/assessment-tool-classic-pages-requirements.md - - name: Run the assessment - href: transform/assessment-tool-classic-pages-run.md - - name: Interpret and prioritize - href: transform/assessment-tool-classic-pages-report.md - - name: Publishing page readiness - href: transform/assessment-tool-publishing-coverage.md - - name: Reference - items: - - name: Classic pages CSV files - href: transform/assessment-tool-classic-pages-csv.md - - name: Common CSV files - href: transform/assessment-tool-common-reports.md - - name: Transform classic pages - href: transform/modernize-userinterface-site-pages.md + - name: Classic pages CSV files + href: transform/assessment-tool-classic-pages-csv.md + - name: Common CSV files + href: transform/assessment-tool-common-reports.md + - name: Transform classic pages + href: transform/modernize-userinterface-site-pages.md + items: + - name: Transform with PnP PowerShell + href: transform/modernize-userinterface-site-pages-powershell.md + - name: Validate transformed pages + href: transform/modernize-userinterface-site-pages-validation.md + - name: Reference items: - - name: Transform with PnP PowerShell - href: transform/modernize-userinterface-site-pages-powershell.md - - name: Validate transformed pages - href: transform/modernize-userinterface-site-pages-validation.md - - name: Reference - items: - - name: Page wave script reference - href: transform/modernize-userinterface-site-pages-wave-scripts.md - - name: In-place versus cross-site transformation - href: transform/modernize-userinterface-site-pages-approach.md - - name: Security requirements - href: transform/modernize-userinterface-site-pages-security.md - - name: Configuration options - href: transform/modernize-userinterface-site-pages-configuration.md - - name: Classic Web Part mappings - href: transform/modernize-userinterface-site-pages-webparts.md - - name: Page transformation model - href: transform/modernize-userinterface-site-pages-model.md - - name: Publishing page transformation model - href: transform/modernize-userinterface-site-pages-model-publishing.md - - name: Functions and selectors - href: transform/modernize-userinterface-site-pages-api.md - - name: User mapping - href: transform/modernize-userinterface-site-pages-usermapping.md - - name: URL mapping - href: transform/modernize-userinterface-site-pages-urlmapping.md - - name: Term mapping - href: transform/modernize-userinterface-site-pages-termmapping.md - - name: Layout transformation - href: transform/modernize-userinterface-site-pages-layout.md - - name: .NET integration - href: transform/modernize-userinterface-site-pages-dotnet.md - - name: Videos - href: transform/modernize-userinterface-site-pages-videos.md + - name: Page wave script reference + href: transform/modernize-userinterface-site-pages-wave-scripts.md + - name: In-place versus cross-site transformation + href: transform/modernize-userinterface-site-pages-approach.md + - name: Security requirements + href: transform/modernize-userinterface-site-pages-security.md + - name: Configuration options + href: transform/modernize-userinterface-site-pages-configuration.md + - name: Classic Web Part mappings + href: transform/modernize-userinterface-site-pages-webparts.md + - name: Page transformation model + href: transform/modernize-userinterface-site-pages-model.md + - name: Publishing page transformation model + href: transform/modernize-userinterface-site-pages-model-publishing.md + - name: Functions and selectors + href: transform/modernize-userinterface-site-pages-api.md + - name: User mapping + href: transform/modernize-userinterface-site-pages-usermapping.md + - name: URL mapping + href: transform/modernize-userinterface-site-pages-urlmapping.md + - name: Term mapping + href: transform/modernize-userinterface-site-pages-termmapping.md + - name: Layout transformation + href: transform/modernize-userinterface-site-pages-layout.md + - name: .NET integration + href: transform/modernize-userinterface-site-pages-dotnet.md + - name: Videos + href: transform/modernize-userinterface-site-pages-videos.md +- name: Scenario guidance + items: + - name: Overview + href: solution-guidance/Office-365-development-patterns-and-practices-solution-guidance.md - name: Modernizing your classic SharePoint sites items: - name: Overview @@ -1901,45 +1927,17 @@ - name: Maximize use of modern lists and libraries href: transform/modernize-userinterface-lists-and-libraries.md items: - - name: Analyze and use the scanner data + - name: Analyze legacy scanner data href: transform/modernize-userinterface-lists-and-libraries-scanner.md - name: Rollout approaches href: transform/modernize-userinterface-lists-and-libraries-rollout.md - name: Opting out from modern href: transform/modernize-userinterface-lists-and-libraries-optout.md - - name: Assess and transform classic pages - href: transform/assess-sharepoint-modernization.md - - name: SharePoint Modernization scanner - items: - - name: Overview - href: transform/modernize-scanner.md - - name: Understand the created reports - items: - - name: Overview - href: transform/modernize-scanner-reports.md - - name: Microsoft 365 group connect report - href: transform/modernize-scanner-reports-groupconnect.md - - name: Modern list and libraries report - href: transform/modernize-scanner-reports-lists.md - - name: Page modernization report - href: transform/modernize-scanner-reports-pages.md - - name: Publishing portal modernization report - href: transform/modernize-scanner-reports-publishingportals.md - - name: Workflow usage report - href: transform/modernize-scanner-reports-workflow.md - - name: InfoPath usage report - href: transform/modernize-scanner-reports-infopath.md - - name: Blog usage report - href: transform/modernize-scanner-reports-blogs.md - - name: SharePoint Designer customized forms report - href: transform/modernize-scanner-reports-customizedforms.md - - name: Scanner FAQ - href: transform/modernize-scanner-faq.yml - name: SharePoint modernization guidance items: - name: Overview href: transform/modernize-guidance.md - - name: Assessment + - name: Legacy assessment delivery guidance href: transform/modernize-guidance-assessment.md - name: Strategy href: transform/modernize-guidance-strategy.md @@ -1961,7 +1959,7 @@ items: - name: Overview href: transform/modernize-connect-to-office365-group.md - - name: Analyze and use the scanner data + - name: Analyze legacy scanner data href: transform/modernize-connect-to-office365-group-scanner.md - name: Subsites versus Microsoft 365 group connection href: transform/modernize-connect-to-office365-group-subsites.md @@ -1973,7 +1971,7 @@ items: - name: Overview href: transform/modernize-publishing-portal.md - - name: Analyze and use the scanner data + - name: Analyze legacy scanner data href: transform/modernize-publishing-portal-scanner.md - name: Modernize classic blogs href: transform/modernize-blogs.md diff --git a/docs/transform/modernize-blogs.md b/docs/transform/modernize-blogs.md index 4e3639ce5e..bc2b7f2631 100644 --- a/docs/transform/modernize-blogs.md +++ b/docs/transform/modernize-blogs.md @@ -1,7 +1,7 @@ --- title: Modernize Delve blogs and classic blogs description: Modernize your Delve blogs and classic blogs -ms.date: 02/09/2023 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- @@ -24,7 +24,7 @@ Before you can start modernizing your blog sites it's important to answer these - Where are the blog sites in my tenant? Getting insight in the blog sites will help you assess the possible modernization impact - Which blog sites are still actively used? It makes sense to (initially) only modernize actively maintained blog sites -The best approach to get an answer to the above questions in running the [SharePoint Modernization Scanner](./modernize-scanner.md): when you run this scanner you'll get a [report detailing the classic blog sites](./modernize-scanner-reports-blogs.md). +Run the [Microsoft 365 Assessment tool's Classic SharePoint Pages Assessment](assess-sharepoint-modernization.md) to discover classic blog pages and review their usage. If you need to interpret output from an existing SharePoint Modernization Scanner run, see the [legacy blog report documentation](modernize-scanner-reports-blogs.md). ## Step 2: Prepare a target communication site to receive the modernized blog pages diff --git a/docs/transform/modernize-branding.md b/docs/transform/modernize-branding.md index 3d649d9d58..72ca67314b 100644 --- a/docs/transform/modernize-branding.md +++ b/docs/transform/modernize-branding.md @@ -1,7 +1,7 @@ --- title: Modernize site branding description: Guidance on moving to modern customization experiences within SharePoint, including how to handle the custom master pages and alternate CSS configurations. -ms.date: 06/05/2020 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -17,7 +17,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://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. +Use the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md) Classic assessment and include the Extensibility component to identify sites that use custom master pages, alternate CSS, or incompatible user custom actions. Use the assessment output to plan remediation. ### Revert back to the default configuration diff --git a/docs/transform/modernize-connect-to-office365-group-scanner.md b/docs/transform/modernize-connect-to-office365-group-scanner.md index 52cf9abcbc..260fbf8e12 100644 --- a/docs/transform/modernize-connect-to-office365-group-scanner.md +++ b/docs/transform/modernize-connect-to-office365-group-scanner.md @@ -1,13 +1,15 @@ --- title: "Analyze and use the scanner data: Connect to Office 365" description: Understand and process the scanner results to help your sites be in optimal shape for connecting a Microsoft 365 group to them. -ms.date: 01/27/2021 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- # Analyze and use the scanner data: Connect to Office 365 +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + 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 a Microsoft 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 "Microsoft 365 group Connection Readiness" report diff --git a/docs/transform/modernize-connect-to-office365-group.md b/docs/transform/modernize-connect-to-office365-group.md index 7913464fdd..85a1603734 100644 --- a/docs/transform/modernize-connect-to-office365-group.md +++ b/docs/transform/modernize-connect-to-office365-group.md @@ -1,7 +1,7 @@ --- title: Connect to a Microsoft 365 group description: Connect a Microsoft 365 group to an existing SharePoint site to modernize it and have it benefit from all other group-connected services such as Microsoft Teams and Planner. -ms.date: 01/14/2021 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -63,7 +63,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://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. +Microsoft 365 group connection readiness isn't currently available in the Microsoft 365 Assessment tool. To analyze which sites are ready to be group-connected, use the [legacy SharePoint Modernization Scanner](modernize-scanner.md). After the scan completes, see [Understand and process the scanner results](modernize-connect-to-office365-group-scanner.md). ### Step 3: Modernize your sites diff --git a/docs/transform/modernize-customizations.md b/docs/transform/modernize-customizations.md index 5e5fbb1c9e..67d89389c7 100644 --- a/docs/transform/modernize-customizations.md +++ b/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: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -21,7 +21,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://aka.ms/sppnp-modernizationscanner). +To understand the modern user interface compatibility of your lists, libraries, and classic extensibility, use the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md). ### JSLink diff --git a/docs/transform/modernize-guidance-assessment.md b/docs/transform/modernize-guidance-assessment.md index d1eefa34e4..3cf6939dd9 100644 --- a/docs/transform/modernize-guidance-assessment.md +++ b/docs/transform/modernize-guidance-assessment.md @@ -1,13 +1,15 @@ --- title: SharePoint modernization guidance - Assessment description: Modernization offerings that IT Teams and partners can use with their customers - assessment step -ms.date: 12/06/2019 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # Assessment +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + Understanding which sites are candidates to be modernized is essential to understand the scope of the work. You can either follow the steps described in the [delivery guide](https://github.com/SharePoint/sp-dev-modernization/blob/dev/Modernization%20partner%20guidance/Microsoft%20Teamwork%20Transformation%20Delivery%20Guide.pptx?raw=true) or follow below steps. ## Download the scanner diff --git a/docs/transform/modernize-guidance.md b/docs/transform/modernize-guidance.md index 33e6259291..18cbe17a25 100644 --- a/docs/transform/modernize-guidance.md +++ b/docs/transform/modernize-guidance.md @@ -1,7 +1,7 @@ --- title: SharePoint modernization guidance description: Modernization offerings that IT Teams can use with their customers -ms.date: 04/25/2022 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -17,9 +17,9 @@ The used approach is structured around 4 steps which are described in great deta ## Step 1: Assessment -Understanding which sites are candidates to be modernized is needed to understand the scope of the work. During the assessment phase you'll learn how to run the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner). +Understanding which sites are candidates to be modernized is needed to understand the scope of the work. Start with [Assess SharePoint modernization](assess-sharepoint-modernization.md) to select the appropriate assessment tool. If you're following this legacy four-step delivery workflow, also run the legacy Groupify assessment because the execution step consumes its Microsoft 365 group connection reports. -Check the [Assessment page](modernize-guidance-assessment.md) to learn more. +See the [legacy assessment delivery guidance](modernize-guidance-assessment.md) for the additional Groupify scan. ## Step 2: Strategy diff --git a/docs/transform/modernize-publishing-portal-scanner.md b/docs/transform/modernize-publishing-portal-scanner.md index c77e708ad6..83052f794b 100644 --- a/docs/transform/modernize-publishing-portal-scanner.md +++ b/docs/transform/modernize-publishing-portal-scanner.md @@ -1,13 +1,15 @@ --- 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: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- # Analyze and use the scanner data: Publishing portal scanner +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + 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 diff --git a/docs/transform/modernize-publishing-portal.md b/docs/transform/modernize-publishing-portal.md index fbdce08e31..22c785b6b5 100644 --- a/docs/transform/modernize-publishing-portal.md +++ b/docs/transform/modernize-publishing-portal.md @@ -1,7 +1,7 @@ --- title: Modernize classic publishing portals description: Modernize your classic publishing portals -ms.date: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- @@ -35,11 +35,11 @@ In modern intranets we recommend using individual communication sites instead of ![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. +The Microsoft 365 Assessment tool provides classic publishing page discovery and portal-level summaries, but it doesn't yet include every field from the legacy Publishing Portal scan. If you need the complete legacy inventory, including detailed publishing web configuration, use the [legacy SharePoint Modernization Scanner](modernize-scanner.md) with the `PublishingOnly` or `PublishingWithPagesOnly` mode. The generated Excel dashboard helps you analyze publishing feature usage across your portals. ![publishing portal dashboard](media/modernize/publishingscanner_1.png) ## See also - [Guide to the Modern experience in SharePoint](/sharepoint/guide-to-sharepoint-modern-experience) -- [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) +- [Choose a SharePoint modernization assessment tool](modernize-scanner.md) diff --git a/docs/transform/modernize-scanner-faq.yml b/docs/transform/modernize-scanner-faq.yml index e54502e87e..86d09b1200 100644 --- a/docs/transform/modernize-scanner-faq.yml +++ b/docs/transform/modernize-scanner-faq.yml @@ -1,12 +1,13 @@ ### YamlMime:FAQ metadata: - title: The SharePoint modernization scanner FAQ - description: he SharePoint modernization scanner FAQ - ms.date: 07/22/2020 + title: The legacy SharePoint modernization scanner FAQ + description: Frequently asked questions for the legacy SharePoint modernization scanner. + ms.date: 07/21/2026 ms.localizationpriority: high -title: Frequently Asked Questions +title: Legacy scanner frequently asked questions summary: | + The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For new assessments, use the Microsoft 365 Assessment tool when it supports your scenario. This FAQ is retained for customers who continue an established scanner workflow or need a scanner-only capability. sections: - name: Ignored diff --git a/docs/transform/modernize-scanner-reports-blogs.md b/docs/transform/modernize-scanner-reports-blogs.md index 9be01f526c..d6cae017b7 100644 --- a/docs/transform/modernize-scanner-reports-blogs.md +++ b/docs/transform/modernize-scanner-reports-blogs.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the blog scanner mode description: Explains the blog output created by the modernization scanner -ms.date: 02/04/2021 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Blog reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + ## Excel dashboard ![Blog dashboard](media/modernize/excel_blogusage.png) diff --git a/docs/transform/modernize-scanner-reports-customizedforms.md b/docs/transform/modernize-scanner-reports-customizedforms.md index b4ee69235c..0c34aa9caa 100644 --- a/docs/transform/modernize-scanner-reports-customizedforms.md +++ b/docs/transform/modernize-scanner-reports-customizedforms.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the customized forms scanner mode description: Explains the customized forms output created by the modernization scanner -ms.date: 02/04/2021 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Customized Forms reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + ## Understanding the ModernizationCustomizedFormsScanResults.csv file This report contains the following columns: diff --git a/docs/transform/modernize-scanner-reports-groupconnect.md b/docs/transform/modernize-scanner-reports-groupconnect.md index 1e0a0bd461..a672670545 100644 --- a/docs/transform/modernize-scanner-reports-groupconnect.md +++ b/docs/transform/modernize-scanner-reports-groupconnect.md @@ -1,13 +1,15 @@ --- 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: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Microsoft 365 group Connect reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + The Microsoft 365 group connect (mode `GroupifyOnly`) is always run as this mode is responsible for creating the main Site and Web reports. ## Excel dashboard diff --git a/docs/transform/modernize-scanner-reports-infopath.md b/docs/transform/modernize-scanner-reports-infopath.md index 5cd10cb059..eb97bd5a60 100644 --- a/docs/transform/modernize-scanner-reports-infopath.md +++ b/docs/transform/modernize-scanner-reports-infopath.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the InfoPath scanner mode description: Explains the InfoPath output created by the modernization scanner -ms.date: 05/30/2023 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: InfoPath reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + > [!Note] > Assessing your InfoPath usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) diff --git a/docs/transform/modernize-scanner-reports-lists.md b/docs/transform/modernize-scanner-reports-lists.md index fc3c43b68a..a14a2b7729 100644 --- a/docs/transform/modernize-scanner-reports-lists.md +++ b/docs/transform/modernize-scanner-reports-lists.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the Lists scanner mode description: Explains the lists output created by the modernization scanner -ms.date: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: List reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + ## Excel dashboard ![Lists dashboard](media/modernize/excel_listmodernization.png) diff --git a/docs/transform/modernize-scanner-reports-pages.md b/docs/transform/modernize-scanner-reports-pages.md index 058a0d2bac..e5395d7491 100644 --- a/docs/transform/modernize-scanner-reports-pages.md +++ b/docs/transform/modernize-scanner-reports-pages.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the pages scanner mode description: Explains the pages output created by the modernization scanner -ms.date: 01/17/2020 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Pages reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + ## Excel dashboard ![Pages dashboard](media/modernize/excel_pagetransformation.png) diff --git a/docs/transform/modernize-scanner-reports-publishingportals.md b/docs/transform/modernize-scanner-reports-publishingportals.md index 2ec0c5308a..bb810d7478 100644 --- a/docs/transform/modernize-scanner-reports-publishingportals.md +++ b/docs/transform/modernize-scanner-reports-publishingportals.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the publishing portal scanner mode description: Explains the publishing portal output created by the modernization scanner -ms.date: 10/23/2019 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Publishing Portal reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + ## Excel dashboard ![Publishing portal dashboard](media/modernize/excel_publishingportal.png) diff --git a/docs/transform/modernize-scanner-reports-workflow.md b/docs/transform/modernize-scanner-reports-workflow.md index c08f87c8f5..7acd7a1bbb 100644 --- a/docs/transform/modernize-scanner-reports-workflow.md +++ b/docs/transform/modernize-scanner-reports-workflow.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports for the workflow scanner mode description: Explains the workflow output created by the modernization scanner -ms.date: 10/23/2019 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports: Workflow reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + > [!Note] > Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) diff --git a/docs/transform/modernize-scanner-reports.md b/docs/transform/modernize-scanner-reports.md index 2eb5b1bbe6..f5fa1b13d5 100644 --- a/docs/transform/modernize-scanner-reports.md +++ b/docs/transform/modernize-scanner-reports.md @@ -1,13 +1,15 @@ --- title: The SharePoint modernization scanner reports description: Explains the output created by the modernization scanner -ms.date: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- # SharePoint Modernization scanner reports +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + The output of a SharePoint Modernization Scanner run is a series of reports (CSV files and Excel dashboards). Using these outputs you can better understand what classic usage there is in your tenant, assess whether it's still relevant for you and get informed on potential remediation's needed before you can modernize. You would typically use the Microsoft Excel based dashboards to inspect the data and build up an understanding of the scan results. If you later on want to modernize sites, lists, etc you can use the CSV files as input for (PowerShell based) automation. > [!Note] diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md index 7e52175f04..d39456b010 100644 --- a/docs/transform/modernize-scanner.md +++ b/docs/transform/modernize-scanner.md @@ -1,33 +1,39 @@ --- -title: The SharePoint modernization scanner -description: Gets you started with the SharePoint modernization scanner -ms.date: 11/26/2025 +title: Which SharePoint modernization assessment tool should I use? +description: Choose between the Microsoft 365 Assessment tool and the legacy SharePoint Modernization Scanner. +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- -# Getting started with the SharePoint modernization scanner +# Which SharePoint modernization assessment tool should I use? -Using the SharePoint Modernization scanner, you can prepare your classic sites for modernization. The scanner will help you prepare for the following modernization efforts: +For new SharePoint Online modernization assessments, use the [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) when it supports your scenario. It is the actively developed assessment platform and includes the current classic pages assessment. -- Optimizing the usage of modern lists and libraries -- Connecting these sites to a Microsoft 365 group -- Modernizing the wiki and web part pages by creating modern site pages -- Rebuilding classic publishing portals as modern publishing portals -- Understanding the usage of classic blog pages +The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. Its documentation remains available for customers who already use the scanner, need to interpret existing scanner reports, or need a capability that isn't yet available in the Microsoft 365 Assessment tool. -This scanner is a key tool to use if you want to prepare for modernizing your classic sites, as it will give you factual data about how easy it is to modernize your sites. Using the dashboards generated by the scanner, you'll be able to drill down on the "modernization readiness" of your sites and plan the needed remediation work where needed. +| Scenario | Recommended tool | +| --- | --- | +| Start a new SharePoint modernization assessment | [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) | +| Assess classic SharePoint pages | [Microsoft 365 Assessment tool - Classic SharePoint Pages](https://pnp.github.io/pnpassessment/classic/readme.html) | +| Review output from an existing SharePoint Modernization Scanner run | Use the legacy scanner report documentation in this archive | +| Continue an established scanner workflow or use a scanner-only capability | Use the legacy scanner documentation and validate that the capability still works in your environment | +| Assess SharePoint Server or another on-premises environment | Use the [SharePoint Migration Assessment Tool](/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) or another scenario-specific assessment tool | -> [!NOTE] -> - Assessing your workflow 2013 and InfoPath Forms Services 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 supports 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. +> The legacy scanner is retained as-is for existing users. Its authentication flows, dependencies, and command examples might no longer represent current recommended practices. Test the scanner in a nonproduction environment before relying on it. + +## Legacy scanner documentation + +- [Understand the reports created by the legacy scanner](modernize-scanner-reports.md) +- [Legacy scanner FAQ](modernize-scanner-faq.yml) +- [Download the legacy SharePoint Modernization Scanner executable](https://github.com/pnp/modernization/blob/master/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true) -## Step 1: Get the latest version of the SharePoint modernization scanner +The following sections document the legacy SharePoint Modernization Scanner for customers who still need it. -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 Scanner 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 and the other pages linked to it contain all the information to get you started, and also all the report details and an FAQ. +## Step 1: Download the legacy SharePoint modernization scanner + +Download the [legacy SharePoint Modernization Scanner executable](https://github.com/pnp/modernization/blob/master/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true). The scanner is no longer actively maintained, so validate its behavior and authentication model before using it. ## Step 2: Preparing for a scan @@ -347,4 +353,3 @@ https://contoso-admin.contoso.com -u spadmin@contoso.com -p pwd --help Display this help screen. ``` - diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-optout.md b/docs/transform/modernize-userinterface-lists-and-libraries-optout.md index 5ad3e834cd..635c332e8b 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-optout.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-optout.md @@ -1,7 +1,7 @@ --- title: Opting out of the modern list and library experience description: Explains how to correctly opt out from modern list and libraries -ms.date: 06/05/2020 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- @@ -73,7 +73,7 @@ Invoke-PnPQuery Opting out of the modern experience is only needed in certain cases, as described in this article's introduction. Previous chapter showed you how to perform an opt out, but how do know which lists and libraries are candidates to be opted out from the modern experience? -The [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) will give you the needed answers: if you run the scanner in "Full scan" or in "Modern list experience readiness" mode the scanner will collect all the data about your lists. Using the generated **Modern UI List Readiness** Excel report you can find the lists having customizations as explained in the [Analyze and use the scanner data](modernize-userinterface-lists-and-libraries-scanner.md) article. +For new assessments, use the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md) Classic assessment with the Lists component to identify incompatible lists. If you're following an existing SharePoint Modernization Scanner-based bulk opt-out process, the legacy scanner's Full or `ListOnly` mode produces the **Modern UI List Readiness** report described in [Analyze and use the scanner data](modernize-userinterface-lists-and-libraries-scanner.md). The found lists will already present themselves in classic, due to SharePoint's classic fallback mechanism. If you however want to offer a full classic user experience, than you might want to opt out the complete site collection from modern lists and libraries. To make that easy, the scanner generates a CSV file named **SitesWithCustomizations.csv** listing all site collections that contain one or more lists that could be opted out. diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md b/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md index 399f09ef93..9c675e3db1 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md @@ -1,7 +1,7 @@ --- title: Rollout approaches for the modern list and library experience description: Understand which approach you can take to do a controlled rollout of the modern list and library user interface -ms.date: 03/04/2019 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- @@ -12,12 +12,12 @@ The modern list and library experience is enabled by default and for most custom ## Approach 1: recommended, the default approach -In this approach we 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. +In this approach, run the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md) Classic assessment with the Lists component to understand which lists aren't ready for the modern experience. If a site contains multiple of these lists or if the users of a given site aren't yet ready for modern, you can selectively disable the modern experience for that site. This gives you time to remediate the lists or educate users before enabling the modern experience again. ![The default approach](media/modernize/modernuirollout_1_update.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 site collection level by enabling the modern experience site level blocking feature. 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. +If you want to enable the modern list and library experience only after you've ensured that the lists and users are ready, you can opt for this "full control" approach. Start by disabling the modern list experience at the site collection level with the modern experience site-level blocking feature. While sites continue to use the classic list experience, run the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md) and remediate the affected lists. When the lists and users are ready, selectively disable the blocking feature in waves until all sites use the modern list and library experience. ![The full control approach](media/modernize/modernuirollout_2_update.png) diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md b/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md index 3818a1bf9e..207fe6c435 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md @@ -1,13 +1,15 @@ --- title: "Analyze and use the scanner data: Modernize lists & libraries" description: Understand and process the scanner results to help your sites to get the most out of the modern list and library experience -ms.date: 06/07/2022 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- # Analyze and use the scanner data: Modernize lists & libraries +[!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] + 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 diff --git a/docs/transform/modernize-userinterface-lists-and-libraries.md b/docs/transform/modernize-userinterface-lists-and-libraries.md index 67f6c062d4..6b0fb82990 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries.md @@ -1,7 +1,7 @@ --- title: Maximize use of modern lists and libraries description: Get the maximum number of lists and libraries when using the SharePoint modern user interface. -ms.date: 04/29/2021 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -44,7 +44,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://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. +Use the [Microsoft 365 Assessment tool](assess-sharepoint-modernization.md) Classic assessment and include the Lists component to identify lists and libraries that aren't available in the modern user interface and understand the reasons they fall back to classic. Use the assessment output to plan the remediation covered in the next section. ## Unblock lists and libraries diff --git a/docs/transform/modernize-userinterface-site-pages-dotnet.md b/docs/transform/modernize-userinterface-site-pages-dotnet.md index 559d63da31..28218be318 100644 --- a/docs/transform/modernize-userinterface-site-pages-dotnet.md +++ b/docs/transform/modernize-userinterface-site-pages-dotnet.md @@ -1,7 +1,7 @@ --- title: Transform classic pages to modern pages using .NET description: Explains how to transform classic wiki and web part pages into modern modern pages using the SharePoint .NET -ms.date: 04/29/2021 +ms.date: 07/21/2026 ms.localizationpriority: medium ms.service: sharepoint --- @@ -250,7 +250,7 @@ using (var cc = am.GetSharePointOnlineAuthenticatedContextTenant(siteUrl)) ### Modern site pages don't work on the site I want to transform pages in -By default the modern site page capability is enabled on most sites but maybe it was turned off afterwards. If that's the case the [SharePoint Modernization scanner](https://aka.ms/sppnp-modernizationscanner) will tell you which sites have turned of the modern page feature. To remediate this use below sample PnP PowerShell script: +By default, the modern site page capability is enabled on most sites, but it might have been turned off. The [legacy SharePoint Modernization Scanner](modernize-scanner.md) can identify sites where the modern page feature is disabled. To remediate this, use the following PnP PowerShell script: ```PowerShell $minimumVersion = New-Object System.Version("1.3.0") diff --git a/docs/transform/modernize-userinterface.md b/docs/transform/modernize-userinterface.md index 3bc16866a0..0a7e423f52 100644 --- a/docs/transform/modernize-userinterface.md +++ b/docs/transform/modernize-userinterface.md @@ -1,7 +1,7 @@ --- title: Modernize the user interface description: Make the switch to a modern user interface by updating your SharePoint lists and libraries and site pages. -ms.date: 04/23/2018 +ms.date: 07/21/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -38,7 +38,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://aka.ms/sppnp-modernizationscanner) provides a detailed analysis of your site's readiness for connecting to a Microsoft 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 a Microsoft 365 group** then use this scanner. +Your tenant might contain thousands of site collections, so which ones are good candidates to modernize? Start with [Assess SharePoint modernization](assess-sharepoint-modernization.md). Use the Microsoft 365 Assessment tool for classic pages, lists, and extensibility. Microsoft 365 group connection readiness isn't currently available in that tool, so established Groupify assessments still require the legacy SharePoint Modernization Scanner. **Microsoft 365 group connection readiness** | :---------| @@ -63,7 +63,7 @@ After you analyze the sites that you want to modernize, you can continue with th - **[Enabling lists and libraries to show in the modern user interface](modernize-userinterface-lists-and-libraries.md)** by replacing customizations, removing incompatible columns from the used views, or (as a last resort) moving data into a modern user interface-compatible list type. - **[Connecting your site to a Microsoft 365 group](modernize-connect-to-office365-group.md)**, which gives your site a modern home page and enables your site to use, for example, a mailbox or Microsoft Planner, which then enables you to use a modern version of a calendar and task list. - - **[Creating modern pages](modernize-classic-sites.md)** and configuring these to be "similar" to your key classic wiki and web part pages. Programmatic page transformation should be done for the key pages of your sites; transforming all pages is resource-intensive and often not needed. To assist in this triage, the SharePoint Modernization scanner can give you usage information about the current wiki and web part pages. + - **[Creating modern pages](modernize-classic-sites.md)** and configuring these to be "similar" to your key classic wiki and web part pages. Programmatic page transformation should be done for the key pages of your sites; transforming all pages is resource-intensive and often not needed. The Microsoft 365 Assessment tool's Classic SharePoint Pages Assessment provides page inventory and usage data to support this triage. - **Communicate to your end users about the completed changes**; the site will work differently in a modern version, so your users need to be aware of that. diff --git a/includes/snippets/open-source/modernization-scanner-legacy.md b/includes/snippets/open-source/modernization-scanner-legacy.md new file mode 100644 index 0000000000..7d11b8c934 --- /dev/null +++ b/includes/snippets/open-source/modernization-scanner-legacy.md @@ -0,0 +1,2 @@ +> [!IMPORTANT] +> The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For new assessments, use the [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) when it supports your scenario. Continue to use the legacy scanner only for an established scanner workflow or a capability that isn't yet available in the Microsoft 365 Assessment tool. For more information, see [Which SharePoint modernization assessment tool should I use?](/sharepoint/dev/transform/modernize-scanner). From 59991a0919f62bdaf1c0ad53b93d10a57064bbdf Mon Sep 17 00:00:00 2001 From: titao Date: Tue, 21 Jul 2026 18:01:59 +0800 Subject: [PATCH 2/8] Preserve legacy modernization repository links Keep the existing SharePoint/sp-dev-modernization URLs because GitHub redirects them to the canonical pnp/modernization repository. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/community/open-source-projects.md | 2 +- docs/features/groupify/groupify-overview.md | 2 +- docs/scenario-guidance/Branding.md | 8 ++++---- docs/transform/modernize-scanner.md | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/community/open-source-projects.md b/docs/community/open-source-projects.md index afa1832c9d..a05580c3a6 100644 --- a/docs/community/open-source-projects.md +++ b/docs/community/open-source-projects.md @@ -17,7 +17,7 @@ There are numerous open-source projects that are coordinated by the SharePoint P | [Office 365 Developer PnP Core Component](https://github.com/SharePoint/PnP-Sites-Core) | An extension component that encapsulates commonly used remote CSOM/REST operations as reusable extension methods on out-of-the box CSOM objects. | | [PnP PowerShell cmdlets](/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets) | Allow you to perform complex provisioning and artifact management actions for SharePoint. The commands use CSOM and can work against both SharePoint Online as well as SharePoint on-premises. | | [PnP remote provisioning schema](https://github.com/SharePoint/PnP-provisioning-schema) | Designed to be used as remote creation instructions for the remote provisioning engine for Office 365. | -| [PnP modernization tooling and guidance](https://github.com/pnp/modernization) | Legacy SharePoint modernization tools and scripts. For new assessment work, see [Assess SharePoint modernization](../transform/assess-sharepoint-modernization.md). | +| [SharePoint Modernization tooling and guidance](https://github.com/SharePoint/sp-dev-modernization) | Legacy SharePoint modernization tools and scripts. For new assessment work, see [Assess SharePoint modernization](../transform/assess-sharepoint-modernization.md). | | [PnPjs](https://pnp.github.io/pnpjs/) | A fluent JavaScript API for consuming SharePoint and Office 365 REST APIs in a type-safe way. | | [PnP SPFx Yeoman Generator](https://pnp.github.io/generator-spfx/) | Open-source Yeoman generator which extends out-of-the-box Yeoman generator. | | [SharePoint Framework reusable property pane controls](https://sharepoint.github.io/sp-dev-fx-property-controls) | Can be used in SharePoint Framework (SPFx) solutions. | diff --git a/docs/features/groupify/groupify-overview.md b/docs/features/groupify/groupify-overview.md index 7b1ab2b422..c34a79232d 100644 --- a/docs/features/groupify/groupify-overview.md +++ b/docs/features/groupify/groupify-overview.md @@ -33,6 +33,6 @@ After your site is connected to a Microsoft 365 group, it behaves like a modern ## See also - [Connect a classic SharePoint team site to a new Microsoft 365 group](../../transform/modernize-connect-to-office365-group.md) -- [Legacy SharePoint Modernization Scanner](../../transform/modernize-scanner.md) +- [SharePoint Modernization scanner tool](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) - [PowerShell cmdlet to connect a SharePoint team site to a new Microsoft 365 group](/powershell/module/sharepoint-online/Set-SPOSiteOffice365Group) - [Modernize your classic SharePoint sites](../../transform/modernize-classic-sites.md) diff --git a/docs/scenario-guidance/Branding.md b/docs/scenario-guidance/Branding.md index 3c25664eec..c20692d5cf 100644 --- a/docs/scenario-guidance/Branding.md +++ b/docs/scenario-guidance/Branding.md @@ -53,7 +53,7 @@ In 2016, the SharePoint Online team released "modern" collaboration sites. These ### Solutions - [SharePoint Framework Extension samples](https://github.com/SharePoint/sp-dev-fx-extensions) -- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) +- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) ### Videos @@ -79,7 +79,7 @@ The classic SharePoint user experience is based on ASP.NET master pages and page ### Solutions - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive) -- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) +- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) - [PnP Starter Intranet for SharePoint 2013/2016 and SharePoint Online](https://github.com/pnp/PnP/tree/master/Solutions/Business.StarterIntranet) ### Videos @@ -160,7 +160,7 @@ Because Microsoft SharePoint is built on top of Microsoft ASP.NET, it supports m ### Solutions -- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) +- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) - [PnP PowerShell branding cmdlets](/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets#branding) - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction) @@ -194,7 +194,7 @@ Cascading style sheet (CSS) plays a large role in SharePoint branding. To succes - [SharePoint 2013/2016/Online Responsive UI](https://github.com/SharePoint/PnP-Tools/tree/master/Solutions/SharePoint.UI.Responsive) - [Activate the PnP Responsive UI Add-on using PnP PowerShell](https://msdn.microsoft.com/pnp_powershell/enablepnpresponsiveui) - [CSS Injection Pattern sample](https://github.com/SharePoint/PnP/tree/master/Samples/Branding.CustomCSS) -- [Legacy SharePoint Modernization Scanner](../transform/modernize-scanner.md) +- [SharePoint Modernization scanner](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization) - [Transformation tool](https://github.com/SharePoint/PnP-Transformation/tree/master/Transformation%20Tool%20-%20CSOM#introduction) ### Samples diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md index d39456b010..88d6948cee 100644 --- a/docs/transform/modernize-scanner.md +++ b/docs/transform/modernize-scanner.md @@ -27,13 +27,13 @@ The SharePoint Modernization Scanner is a legacy tool and is no longer actively - [Understand the reports created by the legacy scanner](modernize-scanner-reports.md) - [Legacy scanner FAQ](modernize-scanner-faq.yml) -- [Download the legacy SharePoint Modernization Scanner executable](https://github.com/pnp/modernization/blob/master/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true) +- [Download the legacy SharePoint Modernization Scanner executable](https://github.com/SharePoint/sp-dev-modernization/blob/dev/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true) The following sections document the legacy SharePoint Modernization Scanner for customers who still need it. ## Step 1: Download the legacy SharePoint modernization scanner -Download the [legacy SharePoint Modernization Scanner executable](https://github.com/pnp/modernization/blob/master/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true). The scanner is no longer actively maintained, so validate its behavior and authentication model before using it. +Download the [legacy SharePoint Modernization Scanner executable](https://github.com/SharePoint/sp-dev-modernization/blob/dev/Tools/SharePoint.Modernization/Releases/SharePoint.Modernization.Scanner.exe?raw=true). The scanner is no longer actively maintained, so validate its behavior and authentication model before using it. ## Step 2: Preparing for a scan From 5158a32b5452c52d380f49e49d6131da9951db04 Mon Sep 17 00:00:00 2001 From: titao Date: Wed, 22 Jul 2026 09:28:53 +0800 Subject: [PATCH 3/8] Remove date-only documentation changes Restore the original dates on files whose link changes were reverted, keeping the PR focused on meaningful content updates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/features/groupify/groupify-overview.md | 2 +- docs/scenario-guidance/Branding.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/groupify/groupify-overview.md b/docs/features/groupify/groupify-overview.md index c34a79232d..dfe641b20c 100644 --- a/docs/features/groupify/groupify-overview.md +++ b/docs/features/groupify/groupify-overview.md @@ -1,7 +1,7 @@ --- title: Overview of the Connect to new Microsoft 365 group feature description: Augment your team site collaboration capabilities with the benefits of other group services such as Outlook, Planner, and Microsoft Teams. -ms.date: 07/21/2026 +ms.date: 06/28/2022 ms.localizationpriority: high --- diff --git a/docs/scenario-guidance/Branding.md b/docs/scenario-guidance/Branding.md index c20692d5cf..92023d4297 100644 --- a/docs/scenario-guidance/Branding.md +++ b/docs/scenario-guidance/Branding.md @@ -1,7 +1,7 @@ --- title: Scenario Guidance - Branding description: Scenario guidance on branding options with SharePoint. -ms.date: 07/21/2026 +ms.date: 06/28/2022 ms.localizationpriority: high --- # Branding From dc9b7723e588fbfe16b5684ab6d2ad3ecc6f9f04 Mon Sep 17 00:00:00 2001 From: titao Date: Fri, 31 Jul 2026 10:11:34 +0800 Subject: [PATCH 4/8] Make Microsoft Learn the primary assessment entry Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/toc.yml | 2 +- docs/transform/modernize-scanner.md | 21 ++++++++++++------- .../modernization-scanner-legacy.md | 2 +- 3 files changed, 15 insertions(+), 10 deletions(-) diff --git a/docs/toc.yml b/docs/toc.yml index 427141e568..44c82afbc6 100644 --- a/docs/toc.yml +++ b/docs/toc.yml @@ -1110,7 +1110,7 @@ href: general-development/sharepoint-development-overview.md - name: SharePoint Modernization scanner items: - - name: Which assessment tool should I use? + - name: Where should I start? href: transform/modernize-scanner.md - name: Understand the legacy scanner reports items: diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md index 88d6948cee..655d79ee14 100644 --- a/docs/transform/modernize-scanner.md +++ b/docs/transform/modernize-scanner.md @@ -1,21 +1,26 @@ --- -title: Which SharePoint modernization assessment tool should I use? -description: Choose between the Microsoft 365 Assessment tool and the legacy SharePoint Modernization Scanner. -ms.date: 07/21/2026 +title: Where should I start a SharePoint modernization assessment? +description: Start classic page modernization on Microsoft Learn, find another Assessment module, or review an archived Scanner workflow. +ms.date: 07/31/2026 ms.localizationpriority: high ms.service: sharepoint --- -# Which SharePoint modernization assessment tool should I use? +# Where should I start a SharePoint modernization assessment? -For new SharePoint Online modernization assessments, use the [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) when it supports your scenario. It is the actively developed assessment platform and includes the current classic pages assessment. +For a new classic page assessment and transformation project, start with [Assess and transform classic SharePoint pages](assess-sharepoint-modernization.md) on Microsoft Learn. The guidance includes requirements, application setup, assessment execution, report interpretation, CSV reference, publishing-page readiness, PnP PowerShell transformation, and validation. + +After reviewing the Microsoft Learn classic-page workflow, use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) for release downloads, configuration options, and implementation details. + +For another supported Assessment module, start directly with the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html). The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. Its documentation remains available for customers who already use the scanner, need to interpret existing scanner reports, or need a capability that isn't yet available in the Microsoft 365 Assessment tool. -| Scenario | Recommended tool | +| Scenario | Start here | | --- | --- | -| Start a new SharePoint modernization assessment | [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) | -| Assess classic SharePoint pages | [Microsoft 365 Assessment tool - Classic SharePoint Pages](https://pnp.github.io/pnpassessment/classic/readme.html) | +| Assess and transform classic SharePoint pages | Start with the [self-contained Microsoft Learn workflow](assess-sharepoint-modernization.md) | +| Download or configure the Microsoft 365 Assessment tool | Use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) | +| Use another supported Assessment module | Use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) | | Review output from an existing SharePoint Modernization Scanner run | Use the legacy scanner report documentation in this archive | | Continue an established scanner workflow or use a scanner-only capability | Use the legacy scanner documentation and validate that the capability still works in your environment | | Assess SharePoint Server or another on-premises environment | Use the [SharePoint Migration Assessment Tool](/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) or another scenario-specific assessment tool | diff --git a/includes/snippets/open-source/modernization-scanner-legacy.md b/includes/snippets/open-source/modernization-scanner-legacy.md index 7d11b8c934..3faf15d2bf 100644 --- a/includes/snippets/open-source/modernization-scanner-legacy.md +++ b/includes/snippets/open-source/modernization-scanner-legacy.md @@ -1,2 +1,2 @@ > [!IMPORTANT] -> The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For new assessments, use the [Microsoft 365 Assessment tool](https://pnp.github.io/pnpassessment/index.html) when it supports your scenario. Continue to use the legacy scanner only for an established scanner workflow or a capability that isn't yet available in the Microsoft 365 Assessment tool. For more information, see [Which SharePoint modernization assessment tool should I use?](/sharepoint/dev/transform/modernize-scanner). +> The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For classic pages, start with [Assess and transform classic SharePoint pages](/sharepoint/dev/transform/assess-sharepoint-modernization) on Microsoft Learn. For another supported Assessment module, use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html). Use the archived scanner guidance only to interpret existing Scanner output, continue an established Scanner workflow, or use a scanner-only capability. For routing, see [Where should I start a SharePoint modernization assessment?](/sharepoint/dev/transform/modernize-scanner). From 7fc148c9b6d82bd1e0660ef7da01181e006256b7 Mon Sep 17 00:00:00 2001 From: titao Date: Fri, 31 Jul 2026 10:56:09 +0800 Subject: [PATCH 5/8] Route assessment links through Microsoft Learn Keep direct PnP Assessment references within the Learn Assessment articles and preserve current workflow retirement guidance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- ...from-classic-workflows-to-power-automate-flows.md | 4 ++-- .../add-ins-and-azure-acs-retirements-faq.md | 2 +- .../retirement-announcement-for-add-ins.md | 4 ++-- .../retirement-announcement-for-azure-acs.md | 2 +- docs/transform/modernize-scanner-reports-infopath.md | 3 --- docs/transform/modernize-scanner-reports-workflow.md | 4 ++-- docs/transform/modernize-scanner-reports.md | 4 ++-- docs/transform/modernize-scanner.md | 12 +++--------- .../modernize-userinterface-site-pages-powershell.md | 2 -- docs/transform/modernize-workflows.md | 12 ++++++------ .../open-source/modernization-scanner-legacy.md | 2 +- 11 files changed, 20 insertions(+), 31 deletions(-) diff --git a/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md b/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md index c2a03fc9ce..34739dd785 100644 --- a/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md +++ b/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md @@ -1,7 +1,7 @@ --- title: Guidance - Migrate from classic workflows to Power Automate flows in SharePoint description: This article specifically provides guidance about how to plan for transitioning from classic SharePoint Workflows to Power Automate flows. -ms.date: 05/12/2023 +ms.date: 07/31/2026 ms.service: power-automate search.app: - Flow @@ -35,7 +35,7 @@ While both workflow systems allow users to build and publish workflows in ShareP Users primarily use SharePoint Designer to author and publish workflows in SharePoint, while professional developers, looking to extend and build workflows, use Visual Studio to build and publish workflows in SharePoint. > [!Important] -> After August 1, 2020, new Microsoft 365 customers can use SharePoint 2013 workflows or Power Automate. However, SharePoint 2013 workflows will follow a similar retirement path in the future, so it's highly recommended to use Power Automate or other supported solutions. If you want to learn more about the SharePoint 2013 workflow usage inside your tenant you can use the [Workflow 2013 Assessment tool](https://aka.ms/microsoft365assessmenttool). This tool will assess your tenant on SharePoint 2013 workflow usage and generates a Power BI report with the findings. +> SharePoint 2013 workflows were turned off for new Microsoft 365 tenants on April 2, 2024, and were fully retired for existing tenants on April 2, 2026. Use Power Automate or another supported solution. Inventory any workflow definitions, owners, dependencies, and business processes that still require replacement before planning migration. >[!Note] >The SharePoint Migration Tool (SPMT) lets you migrate SharePoint Server 2010 out-of-the-box workflows and SharePoint Designer 2010 & 2013 workflows to Power Automate. [Learn more about migrating your SharePoint Server and SharePoint Designer workflows with SPMT.](/sharepointmigration/spmt-workflow-overview) diff --git a/docs/sp-add-ins/add-ins-and-azure-acs-retirements-faq.md b/docs/sp-add-ins/add-ins-and-azure-acs-retirements-faq.md index fcbf754324..8e6d47b856 100644 --- a/docs/sp-add-ins/add-ins-and-azure-acs-retirements-faq.md +++ b/docs/sp-add-ins/add-ins-and-azure-acs-retirements-faq.md @@ -77,7 +77,7 @@ No, both CSOM (client-side object model) and JSOM (JavaScript object model) will ## When I use appregnew.aspx the created ACS principals show up in Entra -As of December 2024 we've streamlined the app creation flow and as a result ACS principals created using appregnew.aspx now show are created as "regular" Entra app principal versus previously service principals with `legacyServicePrincipal` property set to `Legacy`. These app principals are detected by the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool), however you need version 1.10.0 to ensure the principal validity is correctly reported. Note, if you want to renew the secret of these principals ensure you're using the right approach as described in [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in.md). +As of December 2024 we've streamlined the app creation flow and as a result ACS principals created using appregnew.aspx now show are created as "regular" Entra app principal versus previously service principals with `legacyServicePrincipal` property set to `Legacy`. Microsoft 365 Assessment tool version 1.10.0 or later can detect these principals and report their validity. Note, if you want to renew the secret of these principals ensure you're using the right approach as described in [Replace an expiring client secret in a SharePoint Add-in](replace-an-expiring-client-secret-in-a-sharepoint-add-in.md). ## Do I need to delete Azure ACS principals that are not needed anymore? diff --git a/docs/sp-add-ins/retirement-announcement-for-add-ins.md b/docs/sp-add-ins/retirement-announcement-for-add-ins.md index daac5d6a81..488b6cf0d4 100644 --- a/docs/sp-add-ins/retirement-announcement-for-add-ins.md +++ b/docs/sp-add-ins/retirement-announcement-for-add-ins.md @@ -43,13 +43,13 @@ Project Online is an extension on top of SharePoint Online and SharePoint Add-In ### Microsoft 365 Assessment tool -To understand if your organization is using SharePoint Add-Ins or begin planning migration to SharePoint Framework based solutions or alternatives, we recommend that customers run the [Microsoft 365 Assessment tool](https://aka.ms/assessment/addinsacs) to scan their tenants for SharePoint Add-In usage. Using the Power BI [SharePoint Add-In Report](https://aka.ms/assessment/addinsacsreport) generated by the scanner tool, you can: +To understand if your organization is using SharePoint Add-Ins or begin planning migration to SharePoint Framework based solutions or alternatives, we recommend that customers run the Microsoft 365 Assessment tool to scan their tenants for SharePoint Add-In usage. Using the Power BI **SharePoint Add-In Report** generated by the scanner tool, you can: - Identify all SharePoint Add-Ins in the tenant and per site - Evaluate the SharePoint Add-In source (marketplace, app catalog) and who installed the Add-In - For provider hosted Add-Ins get details for the used Azure ACS principal, including it’s validity and requested permission scopes -Using the [SharePoint Add-In Report](https://aka.ms/assessment/addinsacsreport) along with site information, tenant administrators together with developers can plan the migration of SharePoint Add-Ins with minimal impact to the users. +Using the **SharePoint Add-In Report** along with site information, tenant administrators together with developers can plan the migration of SharePoint Add-Ins with minimal impact to the users. ### Migrate business relevant SharePoint Add-Ins by using newer SharePoint development models diff --git a/docs/sp-add-ins/retirement-announcement-for-azure-acs.md b/docs/sp-add-ins/retirement-announcement-for-azure-acs.md index 8e9147e2d7..08395f6819 100644 --- a/docs/sp-add-ins/retirement-announcement-for-azure-acs.md +++ b/docs/sp-add-ins/retirement-announcement-for-azure-acs.md @@ -36,7 +36,7 @@ Project Online is an extension on top of SharePoint Online and Project Online cu ### Microsoft 365 Assessment tool -To understand if your organization is using Azure ACS or begin planning transition to Microsoft Entra ID, we recommend that customers run the [Microsoft 365 Assessment tool](https://aka.ms/assessment/addinsacs) to scan their tenants for Azure ACS usage. Using the Power BI [Azure ACS Report](https://aka.ms/assessment/addinsacsreport) generated by the scanner tool, you can: +To understand if your organization is using Azure ACS or begin planning transition to Microsoft Entra ID, we recommend that customers run the Microsoft 365 Assessment tool to scan their tenants for Azure ACS usage. Using the Power BI **Azure ACS Report** generated by the scanner tool, you can: - Identify all used Azure ACS application principals with their key properties such as permission scopes and whether app-only was allowed or not - For each identified Azure ACS application principal see a list of all sites that can be accessed via the Azure ACS application principal diff --git a/docs/transform/modernize-scanner-reports-infopath.md b/docs/transform/modernize-scanner-reports-infopath.md index eb97bd5a60..68ded2d250 100644 --- a/docs/transform/modernize-scanner-reports-infopath.md +++ b/docs/transform/modernize-scanner-reports-infopath.md @@ -10,9 +10,6 @@ ms.service: sharepoint [!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] -> [!Note] -> Assessing your InfoPath usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) - ## Excel dashboard ![InfoPath dashboard](media/modernize/excel_infopathusage.png) diff --git a/docs/transform/modernize-scanner-reports-workflow.md b/docs/transform/modernize-scanner-reports-workflow.md index 7acd7a1bbb..f8a5345445 100644 --- a/docs/transform/modernize-scanner-reports-workflow.md +++ b/docs/transform/modernize-scanner-reports-workflow.md @@ -10,8 +10,8 @@ ms.service: sharepoint [!INCLUDE [legacy-modernization-scanner](../../includes/snippets/open-source/modernization-scanner-legacy.md)] -> [!Note] -> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) +> [!NOTE] +> For current workflow migration guidance, see [Migrate from classic workflows to Power Automate flows](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md). ## Excel dashboard diff --git a/docs/transform/modernize-scanner-reports.md b/docs/transform/modernize-scanner-reports.md index f5fa1b13d5..6d11e5d620 100644 --- a/docs/transform/modernize-scanner-reports.md +++ b/docs/transform/modernize-scanner-reports.md @@ -12,8 +12,8 @@ ms.service: sharepoint The output of a SharePoint Modernization Scanner run is a series of reports (CSV files and Excel dashboards). Using these outputs you can better understand what classic usage there is in your tenant, assess whether it's still relevant for you and get informed on potential remediation's needed before you can modernize. You would typically use the Microsoft Excel based dashboards to inspect the data and build up an understanding of the scan results. If you later on want to modernize sites, lists, etc you can use the CSV files as input for (PowerShell based) automation. -> [!Note] -> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) +> [!NOTE] +> For current workflow migration guidance, see [Migrate from classic workflows to Power Automate flows](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md). ## Overview of the scanner output diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md index 655d79ee14..483a15b555 100644 --- a/docs/transform/modernize-scanner.md +++ b/docs/transform/modernize-scanner.md @@ -1,6 +1,6 @@ --- title: Where should I start a SharePoint modernization assessment? -description: Start classic page modernization on Microsoft Learn, find another Assessment module, or review an archived Scanner workflow. +description: Start classic page modernization on Microsoft Learn or review an archived SharePoint Modernization Scanner workflow. ms.date: 07/31/2026 ms.localizationpriority: high ms.service: sharepoint @@ -10,17 +10,11 @@ ms.service: sharepoint For a new classic page assessment and transformation project, start with [Assess and transform classic SharePoint pages](assess-sharepoint-modernization.md) on Microsoft Learn. The guidance includes requirements, application setup, assessment execution, report interpretation, CSV reference, publishing-page readiness, PnP PowerShell transformation, and validation. -After reviewing the Microsoft Learn classic-page workflow, use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) for release downloads, configuration options, and implementation details. - -For another supported Assessment module, start directly with the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html). - The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. Its documentation remains available for customers who already use the scanner, need to interpret existing scanner reports, or need a capability that isn't yet available in the Microsoft 365 Assessment tool. | Scenario | Start here | | --- | --- | | Assess and transform classic SharePoint pages | Start with the [self-contained Microsoft Learn workflow](assess-sharepoint-modernization.md) | -| Download or configure the Microsoft 365 Assessment tool | Use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) | -| Use another supported Assessment module | Use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html) | | Review output from an existing SharePoint Modernization Scanner run | Use the legacy scanner report documentation in this archive | | Continue an established scanner workflow or use a scanner-only capability | Use the legacy scanner documentation and validate that the capability still works in your environment | | Assess SharePoint Server or another on-premises environment | Use the [SharePoint Migration Assessment Tool](/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) or another scenario-specific assessment tool | @@ -234,8 +228,8 @@ Mode | Description `BlogOnly` | Includes the Blog scan + includes the Microsoft 365 group connection readiness component `CustomizedFormsOnly` | Includes the Customized Forms scan + includes the Microsoft 365 group connection readiness component -> [!Note] -> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool) +> [!NOTE] +> For current workflow migration guidance, see [Migrate from classic workflows to Power Automate flows](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md). ### Command-line parameter overview diff --git a/docs/transform/modernize-userinterface-site-pages-powershell.md b/docs/transform/modernize-userinterface-site-pages-powershell.md index 64a636ecd0..ceafb1514c 100644 --- a/docs/transform/modernize-userinterface-site-pages-powershell.md +++ b/docs/transform/modernize-userinterface-site-pages-powershell.md @@ -43,8 +43,6 @@ The signed-in user's site permissions also apply. The application's delegated sc With `AllSites.Manage`, add `-SkipItemLevelPermissionCopyToClientSidePage` so the generated page inherits permissions from its library. Use `AllSites.FullControl` only when the page's unique permissions must be retained. -See [Migrate classic pages with the least permission possible](https://pnp.github.io/pnpassessment/classic/migrate-minimal-permissions.html). - ## Install or update PnP PowerShell PnP PowerShell requires PowerShell 7.4.0 or later. diff --git a/docs/transform/modernize-workflows.md b/docs/transform/modernize-workflows.md index 76bef46145..3a1ffbeabe 100644 --- a/docs/transform/modernize-workflows.md +++ b/docs/transform/modernize-workflows.md @@ -1,7 +1,7 @@ --- title: Modernize SharePoint 2013 workflows -description: Make the switch to Power Automate instead of SharePoint 2013 workflow for your business processes. -ms.date: 05/25/2022 +description: Plan the transition from retired SharePoint 2013 workflows to Power Automate for your business processes. +ms.date: 07/31/2026 ms.localizationpriority: high ms.service: sharepoint --- @@ -10,12 +10,12 @@ ms.service: sharepoint Modern business processes are essential for transforming organizational productivity in Microsoft 365. Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond with Microsoft Power Automate. Power Automate connects to all Microsoft 365 services and over 220 other services to let an enterprise build custom workflows. -With the continued investment in Power Automate as the universal solution to workflow orchestration, SharePoint 2010 workflows are retired as of November 2020. SharePoint 2013 workflow has been deprecated since April 2023 and will be turned off for new tenants as of April 2, 2024. It will be removed from existing tenants and will be fully retired as of April 2, 2026. If you’re using SharePoint 2013 workflow, we recommend migrating to Power Automate or other supported solutions. For more info, see [SharePoint 2013 workflow retirement in Microsoft 365](https://aka.ms/sp-workflows-2013support). +With the continued investment in Power Automate as the universal solution to workflow orchestration, SharePoint 2010 workflows were retired in November 2020. SharePoint 2013 workflow was deprecated in April 2023, turned off for new tenants on April 2, 2024, and fully retired for existing tenants on April 2, 2026. If your organization still has workflow definitions or business processes that depended on SharePoint 2013 workflow, migrate them to Power Automate or another supported solution. For more information, see [SharePoint 2013 workflow retirement in Microsoft 365](https://aka.ms/sp-workflows-2013support). -## Assessing your SharePoint 2013 workflow usage +## Plan migration from SharePoint 2013 workflows -Before you can plan to migrate your SharePoint 2013 workflows to Power Automate you first need to understand how many SharePoint 2013 workflows there are in your tenant, and for that you can use the [Workflow 2013 Assessment tool](https://aka.ms/microsoft365assessmenttool). This tool will assess your tenant on SharePoint 2013 workflow usage and generates a Power BI report with the findings. This assessment tool allows you to not only identify the SharePoint 2013 workflows active in your tenant but it also evaluates if they should be migrated to a Power Automate flow before SharePoint 2013 workflows are retired. +Identify the workflow definitions, business owners, dependencies, and processes that still require replacement. If you retained output from an earlier SharePoint Modernization Scanner run, use the [archived workflow report reference](modernize-scanner-reports-workflow.md) to interpret it. Then see [Migrate from classic workflows to Power Automate flows](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md) for migration planning guidance. ## Migrating from SharePoint 2013 workflow to Power Automate -Once you've defined a list of SharePoint 2013 workflows to migrate to Power Automate you use the [Migrate from classic workflows to Power Automate flows in SharePoint](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md) article to get guidance. +After you define the workflows to replace, use [Migrate from classic workflows to Power Automate flows in SharePoint](../business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md) for guidance. diff --git a/includes/snippets/open-source/modernization-scanner-legacy.md b/includes/snippets/open-source/modernization-scanner-legacy.md index 3faf15d2bf..d1d8bd183f 100644 --- a/includes/snippets/open-source/modernization-scanner-legacy.md +++ b/includes/snippets/open-source/modernization-scanner-legacy.md @@ -1,2 +1,2 @@ > [!IMPORTANT] -> The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For classic pages, start with [Assess and transform classic SharePoint pages](/sharepoint/dev/transform/assess-sharepoint-modernization) on Microsoft Learn. For another supported Assessment module, use the [Microsoft 365 Assessment tool project documentation](https://pnp.github.io/pnpassessment/index.html). Use the archived scanner guidance only to interpret existing Scanner output, continue an established Scanner workflow, or use a scanner-only capability. For routing, see [Where should I start a SharePoint modernization assessment?](/sharepoint/dev/transform/modernize-scanner). +> The SharePoint Modernization Scanner is a legacy tool and is no longer actively maintained. For classic pages, start with [Assess and transform classic SharePoint pages](/sharepoint/dev/transform/assess-sharepoint-modernization) on Microsoft Learn. Use the archived scanner guidance only to interpret existing Scanner output, continue an established Scanner workflow, or use a scanner-only capability. For routing, see [Where should I start a SharePoint modernization assessment?](/sharepoint/dev/transform/modernize-scanner). From 424ada1b5db651aa772dc6e1634718116eae4b9b Mon Sep 17 00:00:00 2001 From: titao Date: Fri, 31 Jul 2026 11:54:31 +0800 Subject: [PATCH 6/8] Place classic page workflow before Archive Keep the active assessment and transformation workflow ahead of the archived documentation in the root navigation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/toc.yml | 114 +++++++++++++++++++++++++-------------------------- 1 file changed, 57 insertions(+), 57 deletions(-) diff --git a/docs/toc.yml b/docs/toc.yml index 44c82afbc6..66814b6fbf 100644 --- a/docs/toc.yml +++ b/docs/toc.yml @@ -1104,6 +1104,63 @@ href: sp-add-ins-modernize/publishing-modern-sharepoint-apps-on-appsource.md - name: Modern provisioning of artifacts and information architecture href: sp-add-ins-modernize/modern-provisioning.md +- name: Assess and transform classic pages + href: transform/assess-sharepoint-modernization.md + items: + - name: Assess classic pages + href: transform/assessment-tool-classic-pages.md + items: + - name: Requirements + href: transform/assessment-tool-classic-pages-requirements.md + - name: Run the assessment + href: transform/assessment-tool-classic-pages-run.md + - name: Interpret and prioritize + href: transform/assessment-tool-classic-pages-report.md + - name: Publishing page readiness + href: transform/assessment-tool-publishing-coverage.md + - name: Reference + items: + - name: Classic pages CSV files + href: transform/assessment-tool-classic-pages-csv.md + - name: Common CSV files + href: transform/assessment-tool-common-reports.md + - name: Transform classic pages + href: transform/modernize-userinterface-site-pages.md + items: + - name: Transform with PnP PowerShell + href: transform/modernize-userinterface-site-pages-powershell.md + - name: Validate transformed pages + href: transform/modernize-userinterface-site-pages-validation.md + - name: Reference + items: + - name: Page wave script reference + href: transform/modernize-userinterface-site-pages-wave-scripts.md + - name: In-place versus cross-site transformation + href: transform/modernize-userinterface-site-pages-approach.md + - name: Security requirements + href: transform/modernize-userinterface-site-pages-security.md + - name: Configuration options + href: transform/modernize-userinterface-site-pages-configuration.md + - name: Classic Web Part mappings + href: transform/modernize-userinterface-site-pages-webparts.md + - name: Page transformation model + href: transform/modernize-userinterface-site-pages-model.md + - name: Publishing page transformation model + href: transform/modernize-userinterface-site-pages-model-publishing.md + - name: Functions and selectors + href: transform/modernize-userinterface-site-pages-api.md + - name: User mapping + href: transform/modernize-userinterface-site-pages-usermapping.md + - name: URL mapping + href: transform/modernize-userinterface-site-pages-urlmapping.md + - name: Term mapping + href: transform/modernize-userinterface-site-pages-termmapping.md + - name: Layout transformation + href: transform/modernize-userinterface-site-pages-layout.md + - name: .NET integration + href: transform/modernize-userinterface-site-pages-dotnet.md + - name: Videos + href: transform/modernize-userinterface-site-pages-videos.md - name: Archive items: - name: Overview @@ -1855,63 +1912,6 @@ href: general-development/how-to-back-up-and-restore-sharepoint-using-a-vss-requestor.md - name: Back up and restore a search service application href: general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md -- name: Assess and transform classic pages - href: transform/assess-sharepoint-modernization.md - items: - - name: Assess classic pages - href: transform/assessment-tool-classic-pages.md - items: - - name: Requirements - href: transform/assessment-tool-classic-pages-requirements.md - - name: Run the assessment - href: transform/assessment-tool-classic-pages-run.md - - name: Interpret and prioritize - href: transform/assessment-tool-classic-pages-report.md - - name: Publishing page readiness - href: transform/assessment-tool-publishing-coverage.md - - name: Reference - items: - - name: Classic pages CSV files - href: transform/assessment-tool-classic-pages-csv.md - - name: Common CSV files - href: transform/assessment-tool-common-reports.md - - name: Transform classic pages - href: transform/modernize-userinterface-site-pages.md - items: - - name: Transform with PnP PowerShell - href: transform/modernize-userinterface-site-pages-powershell.md - - name: Validate transformed pages - href: transform/modernize-userinterface-site-pages-validation.md - - name: Reference - items: - - name: Page wave script reference - href: transform/modernize-userinterface-site-pages-wave-scripts.md - - name: In-place versus cross-site transformation - href: transform/modernize-userinterface-site-pages-approach.md - - name: Security requirements - href: transform/modernize-userinterface-site-pages-security.md - - name: Configuration options - href: transform/modernize-userinterface-site-pages-configuration.md - - name: Classic Web Part mappings - href: transform/modernize-userinterface-site-pages-webparts.md - - name: Page transformation model - href: transform/modernize-userinterface-site-pages-model.md - - name: Publishing page transformation model - href: transform/modernize-userinterface-site-pages-model-publishing.md - - name: Functions and selectors - href: transform/modernize-userinterface-site-pages-api.md - - name: User mapping - href: transform/modernize-userinterface-site-pages-usermapping.md - - name: URL mapping - href: transform/modernize-userinterface-site-pages-urlmapping.md - - name: Term mapping - href: transform/modernize-userinterface-site-pages-termmapping.md - - name: Layout transformation - href: transform/modernize-userinterface-site-pages-layout.md - - name: .NET integration - href: transform/modernize-userinterface-site-pages-dotnet.md - - name: Videos - href: transform/modernize-userinterface-site-pages-videos.md - name: Scenario guidance items: - name: Overview From 89b7e81e425dd4151f6e4a8482c92901524ada42 Mon Sep 17 00:00:00 2001 From: titao Date: Tue, 4 Aug 2026 13:31:40 +0800 Subject: [PATCH 7/8] Rename classic page modernization navigation Update only the root TOC label while preserving the landing page title, file name, and Learn URL. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- docs/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/toc.yml b/docs/toc.yml index 66814b6fbf..babd742dbf 100644 --- a/docs/toc.yml +++ b/docs/toc.yml @@ -1104,7 +1104,7 @@ href: sp-add-ins-modernize/publishing-modern-sharepoint-apps-on-appsource.md - name: Modern provisioning of artifacts and information architecture href: sp-add-ins-modernize/modern-provisioning.md -- name: Assess and transform classic pages +- name: Modernizing classic SharePoint pages href: transform/assess-sharepoint-modernization.md items: - name: Assess classic pages From 81e3f8530119491967260d09768320d1e9584e4e Mon Sep 17 00:00:00 2001 From: titao Date: Tue, 4 Aug 2026 18:02:08 +0800 Subject: [PATCH 8/8] Restore original article dates Revert every ms.date edit requested in review while preserving the documentation and navigation changes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: a7db0d98-be53-48c2-9488-9a226f457144 --- .../migrate-from-classic-workflows-to-power-automate-flows.md | 2 +- docs/community/open-source-projects.md | 2 +- docs/solution-guidance/modern-experience-customizations.md | 2 +- docs/transform/modernize-blogs.md | 2 +- docs/transform/modernize-branding.md | 2 +- docs/transform/modernize-connect-to-office365-group-scanner.md | 2 +- docs/transform/modernize-connect-to-office365-group.md | 2 +- docs/transform/modernize-customizations.md | 2 +- docs/transform/modernize-guidance-assessment.md | 2 +- docs/transform/modernize-guidance.md | 2 +- docs/transform/modernize-publishing-portal-scanner.md | 2 +- docs/transform/modernize-publishing-portal.md | 2 +- docs/transform/modernize-scanner-reports-blogs.md | 2 +- docs/transform/modernize-scanner-reports-customizedforms.md | 2 +- docs/transform/modernize-scanner-reports-groupconnect.md | 2 +- docs/transform/modernize-scanner-reports-infopath.md | 2 +- docs/transform/modernize-scanner-reports-lists.md | 2 +- docs/transform/modernize-scanner-reports-pages.md | 2 +- docs/transform/modernize-scanner-reports-publishingportals.md | 2 +- docs/transform/modernize-scanner-reports-workflow.md | 2 +- docs/transform/modernize-scanner-reports.md | 2 +- docs/transform/modernize-scanner.md | 2 +- .../modernize-userinterface-lists-and-libraries-optout.md | 2 +- .../modernize-userinterface-lists-and-libraries-rollout.md | 2 +- .../modernize-userinterface-lists-and-libraries-scanner.md | 2 +- docs/transform/modernize-userinterface-lists-and-libraries.md | 2 +- docs/transform/modernize-userinterface-site-pages-dotnet.md | 2 +- docs/transform/modernize-userinterface.md | 2 +- docs/transform/modernize-workflows.md | 2 +- 29 files changed, 29 insertions(+), 29 deletions(-) diff --git a/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md b/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md index 34739dd785..3c6b7851bc 100644 --- a/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md +++ b/docs/business-apps/power-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md @@ -1,7 +1,7 @@ --- title: Guidance - Migrate from classic workflows to Power Automate flows in SharePoint description: This article specifically provides guidance about how to plan for transitioning from classic SharePoint Workflows to Power Automate flows. -ms.date: 07/31/2026 +ms.date: 05/12/2023 ms.service: power-automate search.app: - Flow diff --git a/docs/community/open-source-projects.md b/docs/community/open-source-projects.md index a05580c3a6..b1215f9f46 100644 --- a/docs/community/open-source-projects.md +++ b/docs/community/open-source-projects.md @@ -1,7 +1,7 @@ --- title: SharePoint Developer Community open source projects description: Open-source projects coordinated by the SharePoint PnP initiative -ms.date: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: high --- diff --git a/docs/solution-guidance/modern-experience-customizations.md b/docs/solution-guidance/modern-experience-customizations.md index bf705a2024..b400f94bce 100644 --- a/docs/solution-guidance/modern-experience-customizations.md +++ b/docs/solution-guidance/modern-experience-customizations.md @@ -1,7 +1,7 @@ --- title: Customizing the "modern" experiences in SharePoint Online description: An overview to get you started using the "modern" experiences in SharePoint Online. -ms.date: 07/21/2026 +ms.date: 06/13/2022 ms.localizationpriority: high --- diff --git a/docs/transform/modernize-blogs.md b/docs/transform/modernize-blogs.md index bc2b7f2631..9688a4918c 100644 --- a/docs/transform/modernize-blogs.md +++ b/docs/transform/modernize-blogs.md @@ -1,7 +1,7 @@ --- title: Modernize Delve blogs and classic blogs description: Modernize your Delve blogs and classic blogs -ms.date: 07/21/2026 +ms.date: 02/09/2023 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-branding.md b/docs/transform/modernize-branding.md index 72ca67314b..f56a649302 100644 --- a/docs/transform/modernize-branding.md +++ b/docs/transform/modernize-branding.md @@ -1,7 +1,7 @@ --- title: Modernize site branding description: Guidance on moving to modern customization experiences within SharePoint, including how to handle the custom master pages and alternate CSS configurations. -ms.date: 07/21/2026 +ms.date: 06/05/2020 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-connect-to-office365-group-scanner.md b/docs/transform/modernize-connect-to-office365-group-scanner.md index 260fbf8e12..f785d32e20 100644 --- a/docs/transform/modernize-connect-to-office365-group-scanner.md +++ b/docs/transform/modernize-connect-to-office365-group-scanner.md @@ -1,7 +1,7 @@ --- title: "Analyze and use the scanner data: Connect to Office 365" description: Understand and process the scanner results to help your sites be in optimal shape for connecting a Microsoft 365 group to them. -ms.date: 07/21/2026 +ms.date: 01/27/2021 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-connect-to-office365-group.md b/docs/transform/modernize-connect-to-office365-group.md index 85a1603734..c74070ebcc 100644 --- a/docs/transform/modernize-connect-to-office365-group.md +++ b/docs/transform/modernize-connect-to-office365-group.md @@ -1,7 +1,7 @@ --- title: Connect to a Microsoft 365 group description: Connect a Microsoft 365 group to an existing SharePoint site to modernize it and have it benefit from all other group-connected services such as Microsoft Teams and Planner. -ms.date: 07/21/2026 +ms.date: 01/14/2021 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-customizations.md b/docs/transform/modernize-customizations.md index 67d89389c7..cc38888012 100644 --- a/docs/transform/modernize-customizations.md +++ b/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: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-guidance-assessment.md b/docs/transform/modernize-guidance-assessment.md index 3cf6939dd9..2885efb61a 100644 --- a/docs/transform/modernize-guidance-assessment.md +++ b/docs/transform/modernize-guidance-assessment.md @@ -1,7 +1,7 @@ --- title: SharePoint modernization guidance - Assessment description: Modernization offerings that IT Teams and partners can use with their customers - assessment step -ms.date: 07/21/2026 +ms.date: 12/06/2019 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-guidance.md b/docs/transform/modernize-guidance.md index 18cbe17a25..f65d245fb8 100644 --- a/docs/transform/modernize-guidance.md +++ b/docs/transform/modernize-guidance.md @@ -1,7 +1,7 @@ --- title: SharePoint modernization guidance description: Modernization offerings that IT Teams can use with their customers -ms.date: 07/21/2026 +ms.date: 04/25/2022 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-publishing-portal-scanner.md b/docs/transform/modernize-publishing-portal-scanner.md index 83052f794b..4f5ed1a332 100644 --- a/docs/transform/modernize-publishing-portal-scanner.md +++ b/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: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-publishing-portal.md b/docs/transform/modernize-publishing-portal.md index 22c785b6b5..b7df2b635e 100644 --- a/docs/transform/modernize-publishing-portal.md +++ b/docs/transform/modernize-publishing-portal.md @@ -1,7 +1,7 @@ --- title: Modernize classic publishing portals description: Modernize your classic publishing portals -ms.date: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-blogs.md b/docs/transform/modernize-scanner-reports-blogs.md index d6cae017b7..6fe6298429 100644 --- a/docs/transform/modernize-scanner-reports-blogs.md +++ b/docs/transform/modernize-scanner-reports-blogs.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the blog scanner mode description: Explains the blog output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 02/04/2021 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-customizedforms.md b/docs/transform/modernize-scanner-reports-customizedforms.md index 0c34aa9caa..e125c3ee07 100644 --- a/docs/transform/modernize-scanner-reports-customizedforms.md +++ b/docs/transform/modernize-scanner-reports-customizedforms.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the customized forms scanner mode description: Explains the customized forms output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 02/04/2021 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-groupconnect.md b/docs/transform/modernize-scanner-reports-groupconnect.md index a672670545..79cf9c0583 100644 --- a/docs/transform/modernize-scanner-reports-groupconnect.md +++ b/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: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-infopath.md b/docs/transform/modernize-scanner-reports-infopath.md index 68ded2d250..53e726cb6b 100644 --- a/docs/transform/modernize-scanner-reports-infopath.md +++ b/docs/transform/modernize-scanner-reports-infopath.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the InfoPath scanner mode description: Explains the InfoPath output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 05/30/2023 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-lists.md b/docs/transform/modernize-scanner-reports-lists.md index a14a2b7729..f35f55c0fe 100644 --- a/docs/transform/modernize-scanner-reports-lists.md +++ b/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: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-pages.md b/docs/transform/modernize-scanner-reports-pages.md index e5395d7491..57d3ab0bd5 100644 --- a/docs/transform/modernize-scanner-reports-pages.md +++ b/docs/transform/modernize-scanner-reports-pages.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the pages scanner mode description: Explains the pages output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 01/17/2020 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-publishingportals.md b/docs/transform/modernize-scanner-reports-publishingportals.md index bb810d7478..b06df04d08 100644 --- a/docs/transform/modernize-scanner-reports-publishingportals.md +++ b/docs/transform/modernize-scanner-reports-publishingportals.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the publishing portal scanner mode description: Explains the publishing portal output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 10/23/2019 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports-workflow.md b/docs/transform/modernize-scanner-reports-workflow.md index f8a5345445..f48f86e4c9 100644 --- a/docs/transform/modernize-scanner-reports-workflow.md +++ b/docs/transform/modernize-scanner-reports-workflow.md @@ -1,7 +1,7 @@ --- title: The SharePoint modernization scanner reports for the workflow scanner mode description: Explains the workflow output created by the modernization scanner -ms.date: 07/21/2026 +ms.date: 10/23/2019 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner-reports.md b/docs/transform/modernize-scanner-reports.md index 6d11e5d620..25684ab4c7 100644 --- a/docs/transform/modernize-scanner-reports.md +++ b/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: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-scanner.md b/docs/transform/modernize-scanner.md index 483a15b555..f01749c04f 100644 --- a/docs/transform/modernize-scanner.md +++ b/docs/transform/modernize-scanner.md @@ -1,7 +1,7 @@ --- title: Where should I start a SharePoint modernization assessment? description: Start classic page modernization on Microsoft Learn or review an archived SharePoint Modernization Scanner workflow. -ms.date: 07/31/2026 +ms.date: 11/26/2025 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-optout.md b/docs/transform/modernize-userinterface-lists-and-libraries-optout.md index 635c332e8b..a8f397b39e 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-optout.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-optout.md @@ -1,7 +1,7 @@ --- title: Opting out of the modern list and library experience description: Explains how to correctly opt out from modern list and libraries -ms.date: 07/21/2026 +ms.date: 06/05/2020 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md b/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md index 9c675e3db1..ac27a93441 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-rollout.md @@ -1,7 +1,7 @@ --- title: Rollout approaches for the modern list and library experience description: Understand which approach you can take to do a controlled rollout of the modern list and library user interface -ms.date: 07/21/2026 +ms.date: 03/04/2019 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md b/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md index 207fe6c435..849d71032e 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries-scanner.md @@ -1,7 +1,7 @@ --- title: "Analyze and use the scanner data: Modernize lists & libraries" description: Understand and process the scanner results to help your sites to get the most out of the modern list and library experience -ms.date: 07/21/2026 +ms.date: 06/07/2022 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface-lists-and-libraries.md b/docs/transform/modernize-userinterface-lists-and-libraries.md index 6b0fb82990..64daf60ce0 100644 --- a/docs/transform/modernize-userinterface-lists-and-libraries.md +++ b/docs/transform/modernize-userinterface-lists-and-libraries.md @@ -1,7 +1,7 @@ --- title: Maximize use of modern lists and libraries description: Get the maximum number of lists and libraries when using the SharePoint modern user interface. -ms.date: 07/21/2026 +ms.date: 04/29/2021 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface-site-pages-dotnet.md b/docs/transform/modernize-userinterface-site-pages-dotnet.md index 28218be318..b0c248c361 100644 --- a/docs/transform/modernize-userinterface-site-pages-dotnet.md +++ b/docs/transform/modernize-userinterface-site-pages-dotnet.md @@ -1,7 +1,7 @@ --- title: Transform classic pages to modern pages using .NET description: Explains how to transform classic wiki and web part pages into modern modern pages using the SharePoint .NET -ms.date: 07/21/2026 +ms.date: 04/29/2021 ms.localizationpriority: medium ms.service: sharepoint --- diff --git a/docs/transform/modernize-userinterface.md b/docs/transform/modernize-userinterface.md index 0a7e423f52..df4f24e29c 100644 --- a/docs/transform/modernize-userinterface.md +++ b/docs/transform/modernize-userinterface.md @@ -1,7 +1,7 @@ --- title: Modernize the user interface description: Make the switch to a modern user interface by updating your SharePoint lists and libraries and site pages. -ms.date: 07/21/2026 +ms.date: 04/23/2018 ms.localizationpriority: high ms.service: sharepoint --- diff --git a/docs/transform/modernize-workflows.md b/docs/transform/modernize-workflows.md index 3a1ffbeabe..31fdba75a0 100644 --- a/docs/transform/modernize-workflows.md +++ b/docs/transform/modernize-workflows.md @@ -1,7 +1,7 @@ --- title: Modernize SharePoint 2013 workflows description: Plan the transition from retired SharePoint 2013 workflows to Power Automate for your business processes. -ms.date: 07/31/2026 +ms.date: 05/25/2022 ms.localizationpriority: high ms.service: sharepoint ---