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 and allows 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 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.”

Invalid Characters and Spaces

DryvIQ verifies file and folder names to identify unsupported characters based on the platform. It then replaces invalid characters with an underscore (_) so the files and folders can 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 (_).

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.  

Permissions Preservation

The following rules will be used when transferring permissions to Office 365.

• If a user account is granted permissions to a file and the user is a member of a group that has greater or equal permissions to that file, no permissions changes will be made. 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 is granted permissions to a file and the user is a member of a group that has lesser permissions to that file, inheritance will be broken, and the file will gain unique permissions for the user. The user account will be added with the requested permissions.

• If a user account is granted permissions to a file and the user is not a member of a group that has permissions to that file, inheritance will be broken, and the file will gain unique permissions. The user account will be added with the requested permissions.

• If a group is granted permissions to a file, inheritance will be broken, and the file will gain unique permissions. The group will be added 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. All items will be set to a retry status. This 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, 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.

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 at the library specified. Connection will take it down to 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 into the GET request. The following GET will return a Microsoft login link. Use the link to complete logging into the account and to grant DryvIQ access to the account. 

GET {{url}}v1/connections/platforms/office365-graph/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 a 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

 {
  "name":"Basic job with impersonation",
  "kind": "transfer",
  "transfer": {
    "audit_level": "trace",
      "transfer_type": "copy",
      "source": {
        "connection": { "id": "{{nfs_source_connectionID}}" },
        "target": {
          "path": "/sourcePath" 
        }
      },
      "destination": {
        "connection": { "id": "{{O365_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"
    }
}

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

 {
  "name":"Basic job with tenant level connection",
  "kind": "transfer",
  "transfer": {
    "audit_level": "trace",
      "transfer_type": "copy",
      "source": {
        "connection": { "id": "{{nfs_source_connectionID}}" },
         "target": {
	        "item": {
              "parent": {
                 "parent": {
                    "root": true,
                    "name": "{{site_collection_name}}"
                 },
                 "name": "{{site_name}}"
               },
               "name": "{{library_name}}"
            }
         }
      },
      "destination": {
        "connection": { "id": "{{O365_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"
    }
}