On This Page

Overview

DryvIQ supports connections to Microsoft Office 365 Government Community Cloud (GCC) High, an environment that provides compliance with US government requirements for cloud services platforms. Connections can be made using an administrator account with the proper privileges to manage configurations. DryvIQ creates this connection using the OAuth 2.0 flow to simplify login and connection management.

Do not select the “Microsoft Office 365 GccH (OAuth 2.0 Deprecated)” connector. That connector is an old connector that uses CSOM, which Microsoft is deprecating. Select the “Microsoft Office 365 GccH” connector when creating the connection since it uses Microsoft Graph API, which results in better job performance.

Create Connection | User Interface

Select Connections > Add connection.
Select Microsoft Office 365 GccH as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Select Sign in with Microsoft Office 365 GccH.
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 Microsoft 365 configurations.
Enter the password for the account and select Sign in.
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.)
Select Done to finish creating the connection.

Add Connection Modal - Microsoft Office 365 GccH

Field	Description	Required

Field	Description	Required
Display as	Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named.	Optional
URL	Enter the URL of your Microsoft 365 GCC High account. You can find the URL by logging into Microsoft 365 GCC High using the account you want to use to create the connection. The URL in the address bar is the correct URL to use.	Required
Token endpoint	This setting is rare for most Microsoft connections and can be left blank. Your administrator will provide this value if needed.	Optional
Graph API endpoint	This setting is rare for most Microsoft connections and can be left blank. Your administrator will provide this value if needed.	Optional
External users notifications	This setting indicates whether you want to send notifications to external users. The default value is No, so no notifications will be sent. If you select Yes, notifications will be sent to external users when they have been granted access to content based on permissions.	Optional
Behavior When Deleting Items	Select the delete DryvIQ should perform when deleting items: Permanent or Soft. Soft delete is the default delete behavior; however, Permanent is the recommended behavior. A soft delete marks items as deleted. You can still access them to restore or permanently delete the items. A permanent delete removes the items. This deletion is not reversible.	Optional

Microsoft Sign In Modal

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.

Authentication Requirement for Microsoft Office 365 Connections

Some SSO providers retain prior login sessions and allow users to select an existing account during sign-in. This behavior can result in a connection being created using an unintended user identity. To prevent this, DryvIQ requires a new authentication for each new connection, even if the account has already been authenticated. This ensures that every connection is created with the correct user account, permissions, and tenant context.

Files/Folders

OneDrive for Business has the following file/folder restrictions:

Supported Features	Unsupported Features	Other Features/Limitations

Supported Features	Unsupported Features	Other Features/Limitations
Version preservation	Mirror lock ownership	Invalid characters: \| " \ / : * ? < > (See Invalid Characters and Spaces below.)
Timestamp preservation		File size maximum: 250 GB Microsoft limit DryvIQ uses a file size limit of 249.999999 GB to ensure seamless transfers. (Refer to HTML Files below for additional file size limitations.)
Author/Owner preservation		Segment path length: N/A
File lock propagation		Path length maximum: 400
Account map (See Mapping below.)		Restricted types: N/A
Group map		Maximum number of files per folder: 5000
Permissions preservation		Maximum Enterprise Keyword length: 255 characters
User impersonation		Restricted characters in Enterprise Keywords: < and >
Metadata map (See Metadata Mapping below.)		No leading whitespace (See Invalid Characters and Spaces below.)
Tags map		No trailing periods and whitespace. (See Invalid Characters and Spaces below.)
		If a file extension is present, trailing periods and whitespace are allowed before the extension
		No non-printable ASCII characters
		Transferring Microsoft Lists is not supported.

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

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 add an entry in the audit log 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 formatting is expected behavior for batch mode/bulk migration API. With batch mode off, the impersonated user will be displayed 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. This setting allows 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, so 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.

Microsoft Link Type	Microsoft Link Format

Microsoft Link Type	Microsoft Link Format
Links to personal or user-owned files stored in the OneDrive document library	<https://<tenant>-my.sharepoint.com/:w:/r/personal/<UserOneDrive>/_layouts/15/Doc.aspx?sourcedoc={<PlatformId>}&file=<Filename>&action=default&mobileredirect=true
Links to team-based or site-owned files stored in libraries managed by SharePoint sites	<https://<tenant>>.sharepoint.com/<LibraryOrFolderPath>/<Filename> <https://<tenant>>.sharepoint.com/<LibraryOrFolderPath>/<FileId> <https://<tenant>>.sharepoint.com/_layouts/15/Doc.aspx?sourcedoc={<PlatformId>}&action=<Action> <https://<tenant>>.sharepoint.com/:x:/r/_layouts/15/Doc.aspx?sourcedoc={<PlatformId>}&file=<Filename>&action=<Action>&mobileredirect=true

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.

Site and Library Path Resolution

Microsoft connectors use a SharePoint-based URL to identify the target location. In some cases, a SharePoint site and a document library can have the same name and therefore appear to share the same path. When this happens, DryvIQ will use the document library.

When entering paths manually, small mistakes such as extra spaces or typos can cause SharePoint to create a new document library instead of using the intended site or library. DryvIQ will then use that newly created location as the destination.

Always verify URLs and paths carefully to avoid migrating content to an unintended location.

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

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.

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. 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 need to escape/encode spaces; enter a space if that exists in the library name.

If a path is not specified, DryvIQ will transfer files to the default library for the site selected.

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.

GET {{url}}v1/connections/platforms/office365-graph-gcch/new?domain={{YOUR URL}}&name={{YOUR CONNECTION NAME}}&client_id={{YOUR CLIENT ID}}&client_secret={{YOUR CLIENT SECRET}}

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

{
  "name":"Basic job with impersonation",
  "kind": "transfer",
  "transfer": {
    "audit_level": "trace",
      "transfer_type": "copy",
      "source": {
        "connection": { "id": "{{source_connectionID}}" },
        "target": {
          "path": "/sourcePath" 
        }
      },
      "destination": {
        "connection": { "id": "{{O365GCCH_destination_connectionID}}" },
        "impersonate_as": {
            "id": "00",
            "name": "Joe Smith",
            "email": "jsmith@company.onmicrosoft.com"
        },
        "target": {
          "path": "/destinationPath"
        }
      },
        "simulation_mode": false
    },
    "schedule": {
        "mode": "manual"
    },
    "stop_policy": {
        "on_success": 5,
        "on_failure": 5,
        "on_execute": 25
    },
    "category": {
      "name": "category name"
    }
}

Microsoft Office 365 GCC High