On This Page

Overview

DryvIQ connections to the OneDrive for Business platform can be made by using an administrator account with the proper privileges to manage OneDrive configurations. DryvIQ can create this connection using the OAuth 2.0 flow to simplify login and connection management.

Creating a Connection

1. Expand the Manage section in the left navigation menu.

2. Click Connections.

3. Click Add connection.

4. Select Microsoft OneDrive for Business as the platform on the Add connection modal.

5. Enter the connection information. Reference the table below for details about each field.

6. Click Sign in with Microsoft OneDrive for Business.

7. Enter the email for the account being used to create the connection and click Next. You must use an admin account with the proper privileges to manage OneDrive for Business configurations.

8. Enter the password for the account and click Sign in.

9. You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)

10. Click Done to finish creating the connection.

Add Connection Modal for Microsoft OneDrive for Business

Microsoft Login

Features and Limitations 

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations. 

File and Folder Name Restrictions

The following are restricted file/folder names.

• _vti_test

• CON

• PRN

• AUX

• NUL

• COM0

• COM1

• COM2

• COM3

• COM4

• COM5

• COM6

• COM7

• COM8

• COM9

• LPT0

• LPT1

• LPT2

• LPT3

• LPT4

• LPT5

• LPT6

• LPT7

• LPT8

• LPT9

For more information on OneDrive for Business restrictions, see Microsoft’s official documentation.

Connection Pooling

Microsoft Office 365 connections using OAuth 2 authentication may experience bandwidth throttling from Microsoft when using connection pooling.

Delta Job Runs

After the initial transfer of an item using a Microsoft SharePoint connection, DryvIQ will leverage Microsoft’s change tracking API on delta job runs to identify changes. This results in fewer Graph API requests and shorter job execution times.

HTML Files

SharePoint online does not support uploading HTML files larger than 256 MB. If your migration includes HTML files that exceed this limit, the file transfer will fail, and an entry will be logged in the audit with the following message: "Unable to interpret the contents of this page because it exceeds the maximum page size of 268435456 bytes.”

Impersonation with Batch Mode

When using Impersonation with Batch Mode, SharePoint Online shows “System Account” in the activity rather than the impersonated user. This is expected behavior for batch mode/bulk migration API. With batch mode off, the impersonated user will display in the activity panel.

Invalid Characters and Spaces

DryvIQ verifies file and folder names to identify unsupported characters based on the platform. Invalid characters are handled according to the Allow unsupported file names to be changed setting for the job.

If the setting is disabled, DryvIQ will throw an exception when it encounters a file or folder that cannot be migrated due to an unsupported character in the name.

If enabled, DyvIQ will replace invalid characters with an underscore (_) or UTF8 encoding based on the option selected. This will allow the files and folders to be transferred. The logic includes leading and trailing spaces in file and folder names. DryvIQ replaces the space rather than trimming it because trimming the space could cause duplicate file names. Adding the underscore ensures the name remains unique.

DryvIQ will sanitize file names that contain combined Unicode characters by replacing the characters with an underscore (_).

Language Translation

DryvIQ does not support translation when migrating between SharePoint sites that have different default language configurations.

Link Remediation

When remediating links from Microsoft OneDrive for Business or Microsoft Office 365, only links in the following format are supported:

Lock Events

Graph API does not support lock event detection without the use of a separate API call, which will slow down change detection. The workaround is to disable native event detection to transfer locks in each job run or to use a soft reset to transfer locks as needed. 

Mapping

When creating CSV mapping files for import, the usernames must be lowercase to properly adhere to the search requirements for the connector.

Metadata Mapping

If a library requires specific metadata but the metadata is missing from a file being copied into the library, the file will be flagged and will not transfer on subsequent jobs runs. If you have files stuck in a flagged state due to missing metadata, you may need to manually transfer the files and add the required metadata.  

OneNote Files

DryvIQ supports transferring OneNote files from any source connector.

Shared Links

DryvIQ retains permissions to files granted through shared links when migrating between SharePoint connections.

Timestamps

There is a discrepancy in timestamps for the SharePoint Online Folder Created Date when using CSOM and Batch Mode. This behavior is a known issue within OneDrive for Business/Office 365.

DryvIQ will attempt to preserve timestamps on folders when using both CSOM and the batch API. However, SharePoint Online updates the folder's modified dates whenever a file is uploaded into it. As a result, when using CSOM, the timestamps will be preserved when the folder is initially created but then updated after every file that gets uploaded. When using batch API, it preserves the timestamps on the folders after all of the files within the batch are committed. This is the cause for the discrepancy between the two methods.

Version Deletes

Version deletes are supported. 

Corrupt Files

If you see “Error=Value=CobaltAllZerosDetected” errors in the logs, the file that triggered the error will not be uploaded to SharePoint online. Microsoft produces this error for files it considers to be corrupt.

Platform Item Exception Errors

DryvIQ uses a batch job (uploading multiple files and committing them to the destination asynchronously) to migrates files that do not exist to Microsoft Office 365 or OneDrive for Business connections since this is the best practice for storage providers that offer batch support. If Microsoft responds with an “item already exists” during a batch migration job, DryvIQ compares the latest set of item properties (modified, versions and number of bytes) to the item properties in the batch job. If the properties on the existing destination file do not match the properties in the batch job, DryvIQ will generate an error identifying the conflicting properties as in the example below.

In the error, original is the item property in the batch job, and latest is the item property on the destination. The item will be flagged as “Retry” and will be handled like a normal retry item.  After selecting the retry action (Retry, Ignore, etc.), the item should be resolved. 

If the batch job and destination have the same properties, no error will be generated, and the item will be transferred.