SharePoint · Andrew Connell (andrewconnell) · Aug 7, 2026 · Jul 21, 2026 · Jul 21, 2026 · Jul 22, 2026
diff --git a/...wer-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md b/...wer-automate/guidance/migrate-from-classic-workflows-to-power-automate-flows.md
@@ -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/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. |
-| [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. |
+| [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/solution-guidance/modern-experience-customizations.md b/docs/solution-guidance/modern-experience-customizations.md
@@ -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/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
@@ -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
@@ -8,7 +8,7 @@ ms.service: sharepoint
 
 # Azure ACS retirement in Microsoft 365
 
-Microsoft strives to deliver utmost value to our customers through modern, optimized, secure solutions in this newly evolved world focused on digital transformation. As part of this evolution of Microsoft 365 solutions we will be retiring the use of Azure ACS (Access Control Services) for SharePoint Online auth needs and believe Microsoft 365 customers will be better served by modern auth offered via [Microsoft Entra ID](https://learn.microsoft.com/azure/active-directory/develop/).
+Microsoft strives to deliver utmost value to our customers through modern, optimized, secure solutions in this newly evolved world focused on digital transformation. As part of this evolution of Microsoft 365 solutions we will be retiring the use of Azure ACS (Access Control Services) for SharePoint Online auth needs and believe Microsoft 365 customers will be better served by modern auth offered via [Microsoft Entra ID](/azure/active-directory/develop/).
 
 Azure ACS will stop working for new tenants as of November 1st, 2024 and it will stop working for existing tenants and will be fully retired as of April 2nd, 2026. This applies to all environments including Government Clouds and Department of Defense.
 
@@ -22,7 +22,7 @@ To learn more about how to migrate Azure ACS usage for SharePoint Online and how
 
 Azure ACS is used in SharePoint Online for providing auth for provider hosted SharePoint Add-Ins plus it’s used to grant applications access to SharePoint Online, optionally using application permissions and granular scopes.
 
-To learn more about the provider hosted Add-In use case please check out the respective retirement articles, granting applications access to SharePoint Online will need to be transitioned to [Microsoft Entra ID](https://learn.microsoft.com/azure/active-directory/develop/).
+To learn more about the provider hosted Add-In use case please check out the respective retirement articles, granting applications access to SharePoint Online will need to be transitioned to [Microsoft Entra ID](/azure/active-directory/develop/).
 
 ### Azure ACS usage by SharePoint Server
 
@@ -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