You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/apis/migration-api-overview.md
+43-13Lines changed: 43 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,27 @@
1
1
---
2
2
title: "SharePoint Online Import Migration API"
3
-
ms.date: 10/09/2020
3
+
ms.prod: sharepoint
4
+
ms.date: 01/06/2021
4
5
ms.author: jhendr
5
6
author: JoanneHendrickson
6
7
manager: serdars
7
8
search.appverid: MET150
8
-
description: "This document is to give more in depth information about how to use the SPO Migration API."
9
+
description: "This article provides in depth information on how to use the SPO Migration API."
9
10
localization_priority: Priority
10
11
---
11
12
# SharePoint Import Migration API (CreationMigrationJob)
12
13
13
14
## API Documention
14
15
15
-
The following API description is based upon use of the SharePoint Client Side Object Model (CSOM). We do recommend using NuGet packages when you reference CSOM in your solution. You can find latest version of the SharePoint Online CSOM package from the NuGet library using id of `Microsoft.SharePointOnline.CSOM`.
16
+
The following API description is based upon use of the SharePoint Client Side Object Model (CSOM). We do recommend using NuGet packages when you reference CSOM in your solution.
16
17
17
-
> [!NOTE]
18
-
> You can find latest version of the SharePoint Online Client Side Object Model from [NuGet gallery](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/).
18
+
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`.
19
+
20
+
>[!Important]
21
+
> **Pending change:** Files larger than 15 GB must now create the required checksum using [QuickXorHash](https://docs.microsoft.com/onedrive/developer/code-snippets/quickxorhash?view=odsp-graph-online). We have provided an example [here](#what-is-stored-in-those-azure-blob-containers).
22
+
>
23
+
>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.
19
24
20
-
> [!NOTE]
21
-
> The **SharePoint Migration Tool** is not available for users of Office 365 operated by 21Vianet in China. It is also not available for users of Office 365 with the German cloud using the data trustee, *German Telekom*. However, it is supported for users in Germany whose data ___location is not in the German data center.
22
25
23
26
## Methods
24
27
@@ -84,6 +87,7 @@ The valid URL including SAS token for accessing the user provided Azure Queue us
Once accepted, the job ID will be written to the notification queue if it was provided and access is valid. The notification queue can be used for multiple migration jobs at the same time, as each job will identify itself in values sent back to the notification queue.
88
92
89
93
The following are examples of all event types logged into the Azure reporting queue:
@@ -384,11 +388,13 @@ Several log types can be included such as the full import log, along with warnin
384
388
385
389
## Changes for those using the "Ship Disk" option
386
390
387
-
To use the Migration API, you must have a temporary storage container in Azure. When uploading files into the temporary storage, an MD5 is required as a property on every file. However, when shipping the data on hard drives this MD5 property doesn’t get assigned automatically. As a work around, we have adapted the Migration API to allow the MD5 to be passed for every file as part of the manifest. This also applies for IV values when encrypting the data.
391
+
To use the Migration API, you must have a temporary storage container in Azure. When uploading files into the temporary storage, a checksum is required as a property on every file. For files larger than 15GB, this is done using QuickXorHash (see example below). For files 2 GB or smaller, MD5 is required as a property on every file.
392
+
393
+
However, when shipping the data on hard drives this property doesn’t get assigned automatically. As a work around, we have adapted the Migration API to allow the checksum to be passed for every file as part of the manifest. This also applies for IV values when encrypting the data.
388
394
389
395
Since the MD5 is generated at the source instead of at the upload time in Azure, Microsoft can confirm the integrity of the file directly against the source MD5.
390
396
391
-
###What is stored in those Azure Blob Containers?
397
+
## What is stored in those Azure Blob Containers?
392
398
393
399
The Migration API requires the Azure Container for content passing and also for log and queue reporting. It can be split down as a summary as follows:<br>
394
400
@@ -398,15 +404,40 @@ The Migration API requires the Azure Container for content passing and also for
398
404
399
405
There are two new optional parameters in manifest.xml:
400
406
407
+
- QuickXorHash
401
408
- MD5Hash
402
409
- InitializationVector
403
410
404
-
####Preparing the package
411
+
### Preparing the package
405
412
The method for calling the migration job doesn’t change; only the package generation needs to be changed.
406
413
407
-
In the Manifest container one file is named Manifest.xml. There are 2 optional attributes added to the file node: *MD5Hash* and *InitializationVector*. <br>
414
+
In the Manifest container one file is named Manifest.xml. There are 2 optional attributes added to the file node: *QuickXorHash*,*MD5Hash* and *InitializationVector*. <br>
@@ -472,7 +503,6 @@ If the migration API was unable to resolve a user using the login provided in th
472
503
1. A new deleted user with the provided login and SystemId is created and is used in the associated metadata within the package.
473
504
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”
Copy file name to clipboardExpand all lines: docs/general-development/advanced-scenarios-and-additional-samples.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Advanced Scenarios and Additional Samples
3
-
ms.date: 11/23/2020
3
+
ms.date: 01/14/2021
4
4
ms.prod: sharepoint
5
5
ms.assetid: 110bcc88-2b55-4d80-ab5c-dc3b9658e48d
6
6
localization_priority: Normal
@@ -22,12 +22,12 @@ The [Using Advanced REST Functionality with the Excel Services Gadget](https://
22
22
23
23
## Embedding Workbook Data
24
24
25
-
The [Excel Services REST API Examples](https://www.microsoft.com/microsoft-365/blog/2009/11/09/excel-services-in-sharepoint-2010-rest-api-examples/) sample shows you how to use the REST API to embed workbook data in interesting ways.
25
+
The [Excel Services REST API Examples](https://www.microsoft.com/en-us/microsoft-365/blog/2009/11/09/excel-services-in-sharepoint-2010-rest-api-examples/) sample shows you how to use the REST API to embed workbook data in interesting ways.
26
26
27
27
## More REST API Syntax Examples
28
28
29
29
The [Excel Services REST API Syntax](https://www.microsoft.com/en-us/microsoft-365/blog/2009/11/05/excel-services-in-sharepoint-2010-rest-api-syntax/) blog entry provides additional Excel Services REST API syntax examples.
30
30
31
31
## Ideas About How to Take Advantage of the REST API
32
32
33
-
The [Excel Services REST API Examples](https://www.microsoft.com/microsoft-365/blog/2009/11/04/simple-access-to-spreadsheet-data-using-the-excel-services-2010-rest-api/) blog entry provides additional ideas about what you can do with the REST API in Excel Services.
33
+
The [Excel Services REST API Examples](https://www.microsoft.com/en-us/microsoft-365/blog/2009/11/04/simple-access-to-spreadsheet-data-using-the-excel-services-2010-rest-api/) blog entry provides additional ideas about what you can do with the REST API in Excel Services.
0 commit comments