|
| 1 | +--- |
| 2 | +title: "Migration guide for ISVs" |
| 3 | +ms.reviewer: |
| 4 | +ms.author: jhendr |
| 5 | +author: JoanneHendrickson |
| 6 | +manager: pamgreen |
| 7 | +audience: Dev |
| 8 | +ms.topic: article |
| 9 | +ms.prod: sharepoint-server-itpro |
| 10 | +localization_priority: Priority |
| 11 | +ms.collection: |
| 12 | +- IT_Sharepoint_Server_Top |
| 13 | +- SPMigration |
| 14 | +- M365-collaboration |
| 15 | +search.appverid: MET150 |
| 16 | +ROBOTS: NOINDEX, NOFOLLOW |
| 17 | +ms.custom: |
| 18 | +ms.assetid: |
| 19 | +--- |
| 20 | +# Migration guidance for ISVs |
| 21 | + |
| 22 | +This document provides guidance for ISVs to deliver a fast and reliable migration experience to customers. It has the latest Microsoft migration practices and addresses common concerns or questions raised by ISV. The page will be updated on regular basis and the priority of the guidance is listed in the order of publication. |
| 23 | + |
| 24 | +## Use app-based authentication |
| 25 | +There are different usage patterns between end user traffic and an application doing background activities such as migration. It is important to identify user traffic versus application traffic. |
| 26 | + |
| 27 | +To provide a stable platform and more reliable service, Microsoft is requesting that ISVs transition from using a user-based authentication to app-based authentication to provide greater reliability to our end users and partners. |
| 28 | + |
| 29 | +Migration is a background task application and should **not** be run in user mode. By transitioning to app-based authentication, you will benefit from the elastic capability of off-peak time to have more resources. |
| 30 | + |
| 31 | +> [!Note] |
| 32 | +>Microsoft will soon begin enforcing the proper usage roles. Vendors who continue to run migration in user roles can expect to experience increasing throttling and poor performance. |
| 33 | +
|
| 34 | +To learn more on how to register an app ID and how to implement app-based authentication see: |
| 35 | + |
| 36 | +- [How to register an app ID](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevelop%2Factive-directory-v2-registration-portal&data=04%7C01%7CWan.Wu%40microsoft.com%7C7c98484b20de4fc80fb308d6da3e3509%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636936358039977299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=L%2BObRVyCBKPwvvY7MUUsWX%2B8yEIbzqaTkBjcmNjc1vk%3D&reserved=0) |
| 37 | +- [Microsoft Graph Auth guidance](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fauth%2F&data=04%7C01%7CWan.Wu%40microsoft.com%7C7c98484b20de4fc80fb308d6da3e3509%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636936358039977299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=ZrFqXsLT3BtT8ynnlLQH9w7JZIOw07zu2X3EYbBmfD4%3D&reserved=0): Includes an informative video, basics, how to register your app and getting access scenarios |
| 38 | +- [Don’t get throttled! SharePoint and OneDrive guide to staying below the limits](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmyignite.techcommunity.microsoft.com%2Fsessions%2F65661&data=04%7C01%7CWan.Wu%40microsoft.com%7C7c98484b20de4fc80fb308d6da3e3509%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636936358039987303%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C-1&sdata=%2FVCt7P794Lwn0hvpaa4bQicVeqHIPuOM8Vg58nkL16A%3D&reserved=0) |
| 39 | + |
| 40 | +### App-based authentication migration guidance |
| 41 | + |
| 42 | +#### Permission settings |
| 43 | +Azure Active Directory (AAD) provides two type of permission : delegated permission and application permissions. For official AAD guidance please see: |
| 44 | + |
| 45 | +- [Permissions and consent in the Azure Active Directory v1.0 endpoint](https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-permissions-and-consent). |
| 46 | + |
| 47 | +For Sharepoint and Onedrive migration scenarios, the guidance is to follow the AAD permission specification. |
| 48 | + |
| 49 | +For migration tool that relies on end user signed in and presence, delegated permission is recommended. |
| 50 | + |
| 51 | +For service-based migration tool that run without a signed-in user present such as app that runs as background service, application permission is recommended. |
| 52 | + |
| 53 | +#### Number of App IDs |
| 54 | + |
| 55 | +Questions have been raised by ISV on whether to have a single App ID covering all migration offering products or having multiple App ID per software offering. There is no specific guidance where the ISVs can identify all of their App IDs. Please contact Microsoft for any corner case scenarios. |
| 56 | + |
| 57 | +>[!Note] |
| 58 | +> Please register all your migration app IDs with Microsoft to ensure that you receive adequate throughput for your migration jobs. |
| 59 | +
|
| 60 | + |
| 61 | +## Use the Migration API |
| 62 | +For migration jobs, the first guidance is to use existing published migration APIs. |
| 63 | + |
| 64 | +### Import API (CreateMigrationJob) |
| 65 | + |
| 66 | +The *CreateMigrationJob* helps the ISVs to import to SharePoint and OneDrive faster and more reliably. |
| 67 | + |
| 68 | +- [Create Migration Job (Import API)](https://docs.microsoft.com/en-us/sharepoint/dev/apis/migration-api-overview) |
| 69 | + |
| 70 | +The lastest supported features are: |
| 71 | + |
| 72 | +- Migrate web parts using the Migration API |
| 73 | + |
| 74 | + |
| 75 | +### Export API (Asynchronous Metadata Read) |
| 76 | + |
| 77 | +A new migration API, Asynchronous Metadata Read API (Export API) is currently being made available to ISVs for testing. If you are interested, please contact Microsoft with your test tenant information. |
| 78 | + |
| 79 | +- [Asynchronous Metadata Read (Export API)](https://docs.microsoft.com/en-us/sharepoint/dev/apis/export-amr-api) |
| 80 | + |
| 81 | +The *AsynchronousMetadataRead* helps the ISVs export content from SharePoint and OneDrive. Once the new API becomes available, we recommend that you transition to the new API to avoid throttling. |
| 82 | + |
| 83 | +## Switch to the Microsoft Graph API |
| 84 | +If a feature is not supported by the migration API, we recommend that you use the Graph API. If the Graph API does not support the needed migration feature, then use CSOM. However, using CSOM increases the likelihood of being throttled. |
| 85 | + |
| 86 | +- [Graph Guidance: Best practices for discovering files and detecting changes at scale](https://docs.microsoft.com/en-us/onedrive/developer/rest-api/concepts/scan-guidance?view=odsp-graph-online) |
| 87 | + |
| 88 | +### CSOM Guidance (fallback only) |
| 89 | + |
| 90 | +The following provides guidance on specific CSOM implementation scenarios to help improve migration performance with Sharepoint and OneDrive. |
| 91 | + |
| 92 | +#### Enumeration Query Ordering guidance |
| 93 | +There are two kinds of enumeration queries, assuming the client intends to read every item with no server-side filtering. |
| 94 | + |
| 95 | +To query for every item in the list, recursively – in other words, the order does not depend on which folder(s) the items are contained in – the query should sort by ID. |
| 96 | + |
| 97 | + <OrderBy Override="TRUE"><FieldRef name="ID"/></OrderBy> |
| 98 | + |
| 99 | +To query for every item in a specific folder, the query should sort by the filename, **FileLeafRef**. |
| 100 | + |
| 101 | + <OrderBy Override="TRUE"><FieldRef name="FileLeafRef"/></OrderBy> |
| 102 | + |
| 103 | + |
| 104 | +## For migrations over 100TB |
| 105 | + |
| 106 | +For customers migrating greater than 100TB of data, please follow the instructions on how to create a support ticket to help the product team to prepare the backend for the customers. |
| 107 | + |
| 108 | +• [Best practices for improving SharePoint and OneDrive migration performance](https://docs.microsoft.com/en-us/sharepointmigration/sharepoint-online-and-onedrive-migration-speed). |
| 109 | + |
| 110 | +## Escalation and throttling |
| 111 | + |
| 112 | +The primary reason speed is impacted, and throttling occurs, is due to the load that gets generated by calling CSOM and REST APIs. As a result of this load, throttling rules fire that impact the speed, reliability and predictability of the migration. Throttling is used to protect the database and to ensure a good user experience for our customers. |
| 113 | + |
| 114 | +To read the official throttling guidance, see: |
| 115 | + |
| 116 | +- [Avoid getting throttled or blocked in SharePoint Online](https://myignite.techcommunity.microsoft.com/sessions/65661) |
| 117 | + |
| 118 | +We continue to work to identify issues and improve the API. The asynchronous metadata read API is a direct result of ISV feedback. As an ISV/partner, we value your feedback. Please contact Microsoft if you have further questions. |
| 119 | + |
0 commit comments