On This Page

Microsoft Office 365 Connection Overview

DryvIQ connections to the Microsoft Office 365 platform can be made by using an administrator account with the proper privileges to manage Office 365 configurations. The connection can be made to a single site or to a site collection/tenant root. DryvIQ creates the connection using the OAuth 2.0 flow to simplify login and connection management.

Create Connection | User Interface

1. Select Connections > Add connection.

2. Select Microsoft Office 365 as the platform on the Add connection modal.

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

4. Select Sign in with Microsoft Office 365.

5. 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 Office 365 configurations. 

6. Enter the password for the account and select Sign in.

7. You will see a "Connection test succeeded" message on the Add connection modal. (If you don't see this message, repeat the sign-in and authorization steps above. If the connection fails, verify the URL. DryvIQ cannot create the connection if the URL is incorrect.)

8. Select Done to finish creating the connection. 

Add Connection Modal - Microsoft Office 365 

Microsoft Sign In Modal

Connection Test Succeeded

Features and Limitations 

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

Files/Folders

Office 365 has the following file/folder restrictions.

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 Office 365 restrictions, see Microsoft’s official documentation.

Connection Pooling

Microsoft Office 365 connections using OAuth 2.0 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.

Disabled Users

The Microsoft Office 365 Connector supports author/owner preservation for disabled users in the following cases:

• When content is being migrated using the SharePoint Migration API (which happens by default during the initial migration job execution), DryvIQ will preserve author/owner for disabled users.

• When the migration job is creating the destination root folder (the root folder selected for the job doesn’t exist and needs to be created), DryvIQ will preserve the owner/author for the disabled user only if it can resolve the user through the EnsureUser CSOM API method or the _api/web/siteusers REST API call. Depending on the state of the disabled user's information in SharePoint, these API calls may not return the required IDs DryvIQ requires to set the user as the owner/author.

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 DryvIQ will log an entry 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.”

Invalid Characters and Spaces

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

Open

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

If enabled, DyvIQ will replace invalid characters with an underscore (_) or UTF-8 encoding based on the option selected. This setting allows DryvIQ to transfer files and folders. 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 (_).

Job Target Paths

When entering the job target path manually, you can use either “%252F” or forward slashes (/) between “sites” and the site name since DryvIQ supports both formats (for example, “/sites%252FTestSite” or “/sites/TestSite”).

Language Translation

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

Link Remediation

DryvIQ currently supports file-based links only for OneDrive and SharePoint. This means DryvIQ will remediate links that point directly to documents (such as Word documents, Excel workbooks, and PowerPoint presentations). However, DryvIQ does not remediate links to folders or entire SharePoint sites. If your documents contain folder paths or site URLs, you’ll need to update those links manually after the migration to ensure they point to the correct location.

Lock Events

The Graph API does not support lock event detection without the use of a separate API call, which can slow down change detection. The workaround is to turn off 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, usernames must be in lowercase to adhere to the search requirements of the connector properly.

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 job runs. If you have files stuck in a flagged state due to missing metadata, you may need to transfer the files and add the required metadata manually.  

OneNote Files

Microsoft has specific standards regarding migrating OneNote files (defined in the Microsoft documentation), and DryvIQ adheres to these standards. DryvIQ converts the OneNote files during the initial folder transfer. If a folder is a valid OneNote folder, DryvIQ will convert it to a OneNote file on Microsoft 365. The item status in the DryvIQ Platform will be “Revised” to indicate DryvIQ converted it. If it is not a valid OneNote folder, DryvIQ will not convert the folder and will transfer it as a regular folder to Microsoft 365.

Updates to the files will not result in the folder type changing, so DryvIQ will not update the folder type based on events in the folder after initial transfer. For example, if a folder contains a non-OneNote file, DryvIQ transfers it as a regular folder on the initial transfer. If you remove the non-OneNote files from the source folder, DryvIQ will not detect the change and will not attempt to convert the folder on subsequent job runs.

Permissions Preservation

DryvIQ uses the following rules when transferring permissions to Office 365.

• If a user account has permissions to a file and the user is a member of a group that has greater or equal permissions to that file, DryvIQ will not make any permissions changes. The operation will show as succeeded, and no permissions will have changed. This behavior applies to both inherited and unique permissions scenarios.

• If a user account has permissions to a file and the user is a member of a group that has lesser permissions to that file, DryvIQ will break inheritance, and the file will gain unique permissions for the user. DryvIQ will add the user account with the requested permissions.

• If a user account has permissions to a file and the user is not a member of a group that has permissions to that file, DryvIQ will break inheritance, and the file will gain unique permissions. DryvIQ will add the user account with the requested permissions.

• If a group has permissions to a file, DryvIQ will break inheritance, and the file will gain unique permissions. DryvIQ will add the group with the requested permissions.

Inherited Library Permissions

If DryvIQ is not able to obtain the inheritance settings for a document library (due to an error during the request or other unknown application error), DryvIQ will produce an ”Unable to determine Document Library permissions inheritance. Retry the item to resolve the issue. Contact support if the problem persists” exception for all items in the batch request. DryvIQ sets items to a retry status. This status allows DryvIQ to retry obtaining inherited permission settings rather than making assumptions about the library’s unique permissions and enabled inheritance.

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, timestamps are preserved when the folder is initially created but are updated after every file is uploaded. When using the batch API, it preserves the timestamps on the folders after all of the files within the batch are committed. This process is the cause of 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 migrate 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 DryvIQ will handle it like a regular 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.

Transfer Content to SharePoint Online Shared Document Library | Connection URI and Path Example

• PlatformType in Connection: office365

• URI Pattern in Connection: https://company.sharepoint.com/[SiteNameWhereLibraryExists]/

• Target/Path in Job:Connection Config: /[LibraryName]

This configuration will transfer data to the destination library specified. The connection will take it down to the site-specific level. 

Path in the 'Job:Connection:Target' should be the Document Library.

Use the Library name found in the URI (you do not have to escape/encode spaces, just enter a space if that exists in the library name).

Create Connection | REST API

You will need to add the relevant connection information to the GET request. The following GET request will return a Microsoft login link. Use this link to complete logging into your account and grant DryvIQ access to the account. 

Create Job | Impersonation with Admin Connection

As an Office 365 administrator, you can impersonate a user using the path that relates to their content. Then, use their information in the impersonate_as block. (See Impersonation for more information on how to impersonate users.)

Impersonation with Office 365 Connection

Create Job | with Tenant Level Connection

When creating a job that is mapped to the default site collection of the tenant the value "Default" must be used even though the URL does not have a ../sites/{site_name} representation.  When setting the root site collection the name should not be prefixed with "sites/".

Impersonation with Office 365 Connection