Merge branch 'master' into live

Author: jansenbe

docs/apis/migration-api-whats-new

@@ -0,0 +1,21 @@
+---
+title: "Migration API What's new"
+ms.reviewer: jhendr
+author: JoanneHendrickson
+ms.author: jhendr
+manager: serdars
+ms.date: 05/17/2022
+audience: ITPro
+ms.topic: article
+ms.prod: sharepoint
+localization_priority: Priority
+ms.custom: admindeeplinkSPO
+description: "Learn about the new features and updates to the Migration API."
+---
+# What's new in the Migration API
+
+Check here to see what features or updates have been added to the Migration API. Here's a summary of what's included.  
+
+##  Fixes
+
+- **Changes to how Import API handles users**. As a response to issues arising from broken OneDrive scenarios when importing duplicate users, the API now blocks and detect duplicate user entries in UserGroup.xml. For details see: [Entering user identifiers in UserGroup.xml](/sharepoint/dev/apis/migration-api-overview#entering-user-identifiers-in-usergroup.xml)

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/20/2021
+ms.date: 05/25/2022
 search.app:
   - Flow
 search.appverid: met150
@@ -23,7 +23,7 @@ This article specifically provides guidance about how to plan for transitioning
 
 Classic workflows in SharePoint constitutes two workflow systems namely
 
-- SharePoint 2010 workflow
+- SharePoint 2010 workflow ([deprecated in November 2020](https://support.microsoft.com/en-us/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f))
 - SharePoint 2013 workflow
 
 While both workflow systems allow users to build and publish workflows in SharePoint, see the following key differences:
@@ -33,6 +33,9 @@ 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.
+
 ## Modern workflows with Power Automate flows
 
 Since the release of classic workflows, SharePoint and Microsoft 365 apps have evolved to provide compelling, flexible and more performant experiences. Modern experiences in SharePoint integrate with rest of the Microsoft 365 apps and services driving security, productivity, and collaboration.

docs/toc.yml

@@ -342,7 +342,7 @@
     - name: Deploy web parts to Azure CDN
       href: spfx/web-parts/get-started/deploy-web-part-to-cdn.md
     - name: Deployment options for SPFx solutions & Microsoft Teams
-      href: https://docs.microsoft.com/sharepoint/dev/spfx/deployment-spfx-teams-solutions
+      href: /sharepoint/dev/spfx/deployment-spfx-teams-solutions
     - name: Custom build tasks
       href: spfx/toolchain/integrate-gulp-tasks-in-build-pipeline.md
     - name: Extend Webpack
@@ -449,9 +449,9 @@
     - name: SharePoint 2016 support
       href: spfx/sharepoint-2016-support.md
     - name: Microsoft Teams
-      href: https://docs.microsoft.com/sharepoint/dev/spfx/build-for-teams-overview
+      href: /sharepoint/dev/spfx/build-for-teams-overview
     - name: Microsoft Viva Connections
-      href: https://docs.microsoft.com/sharepoint/dev/spfx/viva/overview-viva-connections
+      href: /sharepoint/dev/spfx/viva/overview-viva-connections
   - name: Release notes & roadmap
     items:
     - name: Overview
@@ -1631,6 +1631,8 @@
       href: transform/modernize-customizations.md
     - name: Modernize site branding
       href: transform/modernize-branding.md
+    - name: Modernize SharePoint 2013 workflow
+      href: transform/modernize-workflows.md
     - name: Connect to a Microsoft 365 group
       items:
       - name: Overview
@@ -2047,6 +2049,8 @@
     href: apis/spod-copy-move-api.md
   - name: SharePoint Migration Guidance
     items:
+    - name: What's new in Migration API
+      href: apis/migration-api-whats-new.md
     - name: Migration Guidance for ISVs
       href: apis/migration-isv-guidance.md
     - name: Migration permission guidance
@@ -2095,9 +2099,9 @@
       - name: Create folder classification request
         href: apis/syntex/rest-createfolderclassificationrequest.md
   - name: PnP Sites Core API reference
-    href: https://docs.microsoft.com/dotnet/api/?term=Officedevpnp
+    href: /dotnet/api/?term=Officedevpnp
   - name: PnP Sites Core API reference - Extension methods
-    href: https://docs.microsoft.com/dotnet/api/?term=microsoft.sharepoint
+    href: /dotnet/api/?term=microsoft.sharepoint
 - name: SharePoint schema reference
   href: schema/schema-reference-for-sharepoint.md
   items:
@@ -5281,4 +5285,4 @@
 - name: Tutorials
   href: training/training.md
 - name: SharePoint Framework API reference
-  href: https://docs.microsoft.com/javascript/api/overview/sharepoint
+  href: /javascript/api/overview/sharepoint

docs/transform/modernize-workflows.md

@@ -0,0 +1,21 @@
+---
+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
+ms.prod: sharepoint
+ms.localizationpriority: high
+---
+
+# Modernize SharePoint 2013 workflows
+
+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. After November 2020, 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.
+
+## Assessing your SharePoint 2013 workflow usage
+
+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.
+
+## 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.