Skip to content

Commit 692b93a

Browse files
authored
Merge pull request #2 from SharePoint/master
merging changes on master to local
2 parents cfb6fda + 01e45c8 commit 692b93a

File tree

4 files changed

+25
-4
lines changed

4 files changed

+25
-4
lines changed

docs/apis/export-amr-api.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ During incremental migration, instead of query everything again, by populating S
120120

121121
Below is a sample of how the *startChangeToken* might work. This example uses the optional feature setting for initial call and the parameter setting for incremental passes.
122122

123-
![AMR flow](media/async-read-api-flow.png)
123+
![Export API process](../images/async-read-api-flow.png)
124124

125125
#### Invalid Value
126126

@@ -153,8 +153,12 @@ This function returns the changeToken associates with this query. By specifying
153153

154154
#### Manifest Output
155155

156-
After the asyncMigrationRead function finishes execution, the final manifest will be placed in the container specified, with naming convention of “<jobid>/<filename>”. Manifest export package structure will be like the *createMigration* Import Package structure. The general output structure is summarized in table below.
156+
After the asyncMigrationRead function finishes execution, the final manifest will be placed in the container specified, under a folder named **JobId**. Manifest export package structure will be like the *createMigration* Import Package structure. The general output structure is summarized in table below.
157157

158+
Below is an example on how to query the folder:
159+
160+
CloudBlobDirectory folder = blobContainerObj.GetDirectoryReference(jobid);
161+
CloudBlockBlob blob = folder.GetBlockBlobReference(manifestFileName);
158162

159163
|**XML file**|**Schema File**|**Description**|
160164
|:-----|:-----|:-----|
@@ -188,7 +192,7 @@ It returns the AES256CBC encryption key used to decrypt the message in azureMani
188192
## Set up Guidelines
189193
The following provides high level guidelines for implementing the asynchronous metadata migration function. This documentation does not go into details on how to interact with SharePoint RESTful service. It is assumed that the ISV has prior knowledge and will be able to access the target website with proper permission. </br>,</br>For more information on how to access the Sharepoint website, refer to [Get to Know the SharePoint Rest Service](https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/get-to-know-the-sharepoint-rest-service).
190194

191-
1. Install and update the latest Microsoft.SharePointOnline.CSOM version. The minimum version requirement is V16.1.8600 or later.
195+
1. Install and update the latest Microsoft.SharePointOnline.CSOM version. The minimum version requirement is V16.1.9119.1200 or later.
192196
2. ISVs figure out the folder, document library or files of interested to be query and issued with CreateSPAsyncReadJob function.
193197
3. Once successfully created, query the job status using the *jobQueueUri*. It provides the job process status and any error logging. After job completion, parse the Manifest to retrieve the metadata.
194198

docs/apis/migration-api-overview.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1438,6 +1438,23 @@ There is no change from current published full 2013 [full 2013 package schema](h
14381438

14391439
There is no change from current published [full 2013 package schema](https://docs.microsoft.com/en-us/sharepoint/dev/schema/content-migration-schemas).
14401440

1441+
## Sample: Using REST to call the API
1442+
1443+
1444+
https://<spam><spam>yourtenanthere.sharepoint.com/sites/importSite/_api/site/CreateMigrationJobEncrypted<spam><spam>
1445+
1446+
{
1447+
"options": {
1448+
"AES256CBCKey": "000000000000000000000000000000000000000000000000000000="
1449+
},
1450+
"gWebId": "00000000-0000-0000-0000-000000000000",
1451+
"azureContainerSourceUri": "https://<spam><spam>tenant.blob.core.windows.net:443/00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000<spam><spam>=rw",
1452+
"azureContainerManifestUri": "https://<spam><spam>tenant.blob.core.windows.net:443/00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000<spam><spam>=rw"
1453+
}
1454+
1455+
For the container
1456+
https://<spam><spam>yourtenanthere.sharepoint.com/sites/importSite/_api/site/ProvisionMigrationContainers<spam><spam>
1457+
14411458

14421459
>[!NOTE]
14431460
>The **Migration API** 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.

docs/apis/migration-isv-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ A new migration API, Asynchronous Metadata Read API (Export API) is currently be
7878

7979
- [Asynchronous Metadata Read (Export API)](https://docs.microsoft.com/en-us/sharepoint/dev/apis/export-amr-api)
8080

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.
81+
The *AsynchronousMetadataRead* helps the ISVs export content from SharePoint and OneDrive.
8282

8383
## Switch to the Microsoft Graph API
8484
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.

docs/images/async-read-api-flow.png

50.9 KB
Loading

0 commit comments

Comments
 (0)