Master (SharePoint#8007)

* Cleanup throttling docs

* cleanup the throttling sample code

* Update migration-api-overview.md

resubmitting updates from previous PR March 29th that didn't go live.  Adding section Entering user identifiers in UseGroup.xml

* fix markdown errors & update doc timestamp

- updated doc timestamp to show when doc updated
- fixed incorrect indentation of code blocks in bullet lists
- removed empty lines before/after code blocks
- closed unclosed fenced code

* Plugging the Microsoft 365 Assessment tool for workflow scanning

* Create migration-api-whats-new (SharePoint#7966)

* Create migration-api-whats-new

creation of new what's new file in response to ISV requests.

* fix date format

Co-authored-by: Andrew Connell <[email protected]>

* Update toc.yml (SharePoint#7967)

* Update toc.yml

update toc to include What's new in MigrationAPI

* Update toc.yml

corrected path (left off the extension) to What's new article   line 2013:  apis/migraton-api-whats-new.md

* remove relative URL references

fixing automated checks

Co-authored-by: Andrew Connell <[email protected]>

* Workflow 2013 modernization and assessment updates

Co-authored-by: Bert Jansen <[email protected]>
Co-authored-by: JoanneHendrickson <[email protected]>
Co-authored-by: Andrew Connell <[email protected]>

Author: 4 people

docs/apis/migration-api-overview.md

@@ -1,7 +1,8 @@
 ---
 title: "SharePoint Online Import Migration API"
 ms.prod: sharepoint
-ms.date: 04/19/2022
+
+ms.date: 05/19/2022
 ms.author: jhendr
 author: JoanneHendrickson
 manager: serdars
@@ -17,12 +18,12 @@ The following API description is based upon use of the SharePoint Client Side Ob
 
 You can find latest version of the SharePoint Online Client Side Object Model (CSOM) package from the [NuGet gallery](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/). Use the ID `Microsoft.SharePointOnline.CSOM`.
 
->[!Important]
+> [!Important]
 > Files larger than 15 GB must now create the required checksum using [QuickXorHash](/onedrive/developer/code-snippets/quickxorhash). We have provided an example [here](#what-is-stored-in-those-azure-blob-containers).
 > 
->The QuickXorHash/Checksum has to be computed for the original file **before** encryption (if the file is being encrypted). This is different from the MD5hash requirement.
+> The QuickXorHash/Checksum has to be computed for the original file **before** encryption (if the file is being encrypted). This is different from the MD5hash requirement.
 >
->The previous method of MD5Hash is still required for files smaller than 2 GB; however this requirement will be removed at some point in the future.
+> The previous method of MD5Hash is still required for files smaller than 2 GB; however this requirement will be removed at some point in the future.
 
 
 ## Methods
@@ -452,8 +453,8 @@ Even if the API support 15GB files, we recommend package sizes of up to 250 MB O
 
 ### File size
 
->[!Note]
->The Migration API supports individual files over **15 GB**. The maximum size is current to that set by SharePoint Online.
+> [!Note]
+> The Migration API supports individual files over **15 GB**. The maximum size is current to that set by SharePoint Online.
 
 ### Only un-compressed packages are supported
 
@@ -492,6 +493,51 @@ The import pipeline is using Azure Blob Storage security model as is. This means
 ### Events and event handlers
 
 The import pipeline allows event handlers to be referenced on list items but doesn’t allow defining event handlers at the list level at this time. The import pipeline does not fire events as items are imported, so existing event handlers will not fire due to the import event.
+### Entering user identifiers in UserGroup.XML
+
+Follow these guidelines when generating the **UserGroup.XML** in the submitted package:
+
+- A person can be identified only once in a single package
+- The 'login' attribute of the user identifier requires a UPN. **Do not** enter a non-UPN email address.
+
+
+> [!Important]
+> As of March 2, 2022, the Migration API now validates and enforces a maximum of one identifier per user in a single package. 
+>
+> While using a non-UPN email won't result in a failed job, it may bring unexpected results in SharePoint Online.
+
+**Examples**
+
+The following examples show the correct and incorrect ways of entering the user identifier in UserGroup.XML.
+
+In this case, the user has the following identifiers:
+
+- **UPN**: [email protected]
+- **Email**: [email protected]. 
+
+
+**Correct**
+
+- In this example, the user is entered only once, using a UPN email address.
+
+    ```xml
+    <User Id="1" Login="i:0#.f|membership|[email protected]" …/>
+    ```
+
+**Incorrect**
+
+- **Example 1:** This example uses a non-UPN email address and incorrectly includes more than identifier for a single user.
+
+    ```xml
+    <User Id="1" Login="i:0#.f|membership|[email protected]" …/>
+    <User Id="2" Login="i:0#.f|membership|[email protected]" …/>
+    ```
+
+- **Example 2:** This example incorrectly uses a non-UPN email address.
+
+    ```xml
+    <User Id="2" Login="i:0#.f|membership|[email protected]" …/>
+    ```
 
 ### Resolving Users
 
@@ -500,7 +546,7 @@ If the Migration API was unable to resolve a user using the login provided in th
 1. This user will be replaced by “System Account” in the associated metadata within the package ( author, editor etc.).
 1. A warning will be reported in the ImportLogs –  “Failed to ensure user '[email protected]'”
 
-If the migration API was unable to resolve a user using the login provided in the UserGroup.xml and the System ID is provided (which is the SID for the user in the on-premises AD), then:
+    If the migration API was unable to resolve a user using the login provided in the UserGroup.xml and the System ID is provided (which is the SID for the user in the on-premises AD), then:
 
 1. A new deleted user with the provided login and SystemId is created and is used in the associated metadata within the package.
 1. A warning will be reported in the ImportLogs- “Failed to retrieve user '[email protected]' attributes from the SiteUsers; falling back to passed in values”

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/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md

@@ -1,7 +1,7 @@
 ---
 title: Avoid getting throttled or blocked in SharePoint Online
 description: Find out about throttling in SharePoint Online, and learn how to avoid being throttled or blocked. Includes sample client-side object model (CSOM) and REST code you can use to make your task easier.
-ms.date: 07/07/2021
+ms.date: 05/11/2022
 ms.prod: sharepoint
 ms.assetid: 33ed8106-d850-42b1-8d7f-5ba83901149c
 ms.localizationpriority: high
@@ -183,17 +183,16 @@ HttpWebResponse endpointResponse = (HttpWebResponse)endpointRequest.GetResponse(
 Add this extension method in a static class and use `ExecuteQueryWithIncrementalRetry` instead of `ExecuteQuery` to make your code handle throttling requests.
 
 ```csharp
-public static void ExecuteQueryWithIncrementalRetry(this ClientContext clientContext, int retryCount, int delay)
+public static void ExecuteQueryWithIncrementalRetry(this ClientContext clientContext, int retryCount)
 {
   int retryAttempts = 0;
-  int backoffInterval = delay;
   int retryAfterInterval = 0;
   bool retry = false;
   ClientRequestWrapper wrapper = null;
   if (retryCount <= 0)
+  {
     throw new ArgumentException("Provide a retry count greater than zero.");
-  if (delay <= 0)
-    throw new ArgumentException("Provide a delay greater than zero.");
+  }
 
   // Do while retry attempt is less than retry count
   while (retryAttempts < retryCount)
@@ -234,25 +233,11 @@ public static void ExecuteQueryWithIncrementalRetry(this ClientContext clientCon
           wrapper = (ClientRequestWrapper)ex.Data["ClientRequest"];
           retry = true;
 
-          // Determine the retry after value - use the `Retry-After` header when available
-          string retryAfterHeader = response.GetResponseHeader("Retry-After");
-          if (!string.IsNullOrEmpty(retryAfterHeader))
-          {
-            if (!Int32.TryParse(retryAfterHeader, out retryAfterInterval))
-            {
-              retryAfterInterval = backoffInterval;
-            }
-          }
-          else
-          {
-            retryAfterInterval = backoffInterval;
-          }
+          // Determine the retry after value - use the `Retry-After` header
+          retryAfterInterval = Int32.Parse(response.GetResponseHeader("Retry-After"));
 
           // Delay for the requested seconds
           Thread.Sleep(retryAfterInterval * 1000);
-
-          // Increase counters
-          backoffInterval = backoffInterval * 2;
         }
         else
         {

docs/solution-guidance/Handle-SharePoint-Online-throttling-by-using-exponential-back-off.md

@@ -344,7 +344,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
@@ -451,9 +451,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
@@ -1637,6 +1637,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
@@ -1821,8 +1823,6 @@
       href: solution-guidance/Extending-SharePoint-Online-for-Germany-China-USGovernment-environments.md
     - name: Avoid getting throttled or blocked in SharePoint Online
       href: general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md
-    - name: Handle SharePoint Online throttling
-      href: solution-guidance/Handle-SharePoint-Online-throttling-by-using-exponential-back-off.md
     - name: Set up app-only access to SharePoint
       href: solution-guidance/security-apponly.md
       items:
@@ -2055,6 +2055,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
@@ -2103,9 +2105,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:
@@ -5289,4 +5291,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/toc.yml

@@ -8,6 +8,9 @@ ms.localizationpriority: high
 
 # SharePoint Modernization scanner reports: Workflow reports
 
+> [!Note]
+> Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool)
+
 ## Excel dashboard
 
 ![Workflow dashboard](media/modernize/excel_workflowusage.png)

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

@@ -10,6 +10,9 @@ ms.localizationpriority: high
 
 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)
+
 ## Overview of the scanner output
 
 The output you'll depends on the chosen scan mode. Below table lists the available scan modes: