Overview

DryvIQ supports connections to Microsoft OneDrive for Business Government Community Cloud (GCC) High — an environment that provides compliance with US government requirements for cloud services platforms. The DryvIQ Microsoft OneDrive for Business GCC High connection enables you to analyze, migrate, copy, and synchronize files from your OneDrive account to cloud storage repositories and on-premises network file shares. DryvIQ creates the connection using the OAuth 2.0 flow to simplify login and connection management. You can use any administrator account with the proper privileges to manage Microsoft 365 configurations to create the connection. 

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 GccH 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 Gcch.
7. Enter the email for the account being used to create the connection and click Next. You must use an administrator 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 at the bottom of the modal when DryvIQ establishes a connection. (If the connection fails, verify the information you entered.)
10. Click Done to finish creating the connection.

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. The information below is platform-specific. 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. For more information on Office 365 restrictions, see Microsoft’s official documentation.

Connection Pooling

Microsoft OneDrive for Business connections using OAuth 2 authentication may experience bandwidth throttling from Microsoft when using connection pooling.

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.

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. DryvIQ will add an entry to 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. DryvIQ handles invalid characters 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 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, allowing DryvIQ to transfer the 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 (_).

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 pointing directly to documents (Word documents, Excel workbooks, PowerPoint presentations, etc.). 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

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 adhere to the search requirements for 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.

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 are preserved when the folder is created, but they are updated after every file that gets 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. 

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 “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.

PlatformItemOutOfDateException: The item changed during processing. Retry the item to resolve the issue. Contact support if the problem persists. /TD_7bcd1ca33f274b0bb7a8698f99936f6b/Folder/File.txt with changed properties: timestamp - original:7/3/2024 4:09:49 PM +00:00, latest:7/3/2024 4:09:56 PM +00:00; number of bytes - original:3, latest:8;

In the error, “original” refers to the item property in the batch job, and “latest” refers to the item property on the destination. The item will be flagged for retry and will be handled 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.