Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On This Page

Table of Contents

...

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

  2. Click Connections.

  3. Click Add connection.

  4. Select Microsoft Office 365 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 Office 365.

  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 Office 365 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 Office 365 

...

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 using the URL. For example, Microsoft Office 365 (https://mycompany.sharepoint.com/). If it will be useful for you to reference the connection by account, you should use the default name.

Optional

URL

Enter the URL of your Office 365 account. 

You can find the URL by logging into Microsoft Office 365 using the account you want to use to create the connection. The URL in the address bar is the URL you need to use. It will look something like "https://mycompany.sharepoint.com/_layouts/15/viewlsts.aspx?view=14," where mycompany will be the site name of your company. You can copy and paste the full URL or only the part before layouts "layouts" (https://mycompany-my.sharepoint.com/). DryvIQ will ignore the extra part of the URL in most cases.

(warning) If the connection fails, verify the URL. DryvIQ cannot create the connection if the URL is incorrect. 

(warning) When entering the the path for a tenant-level connection, you need to use %252F instead of a / between “sites” and the site name (for example, /sites%252FTestSite versus /sites/TestSite).

Required

Token endpoint

This setting is rare for most Microsoft connections and can be left blank. If needed, this value will be provided by your administrator.

Optional

Graph API endpoint

This setting is rare for most Microsoft connections and can be left blank. If needed, this value will be provided by your administrator.

Optional

External users notification

This indicates if 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

Set Tenant Level Connection

This indicates if the connection should be set at the tenant level. The default value is No, so the connection will be set based on the URL provided.

If you select Yes, the connection will override the URL provided and connect to {tenant}-admin.sharepoint.com.

(warning) Using a tenant level connection allows one connection to be used to create jobs that point at different site collections.  When creating a job using the Microsoft Office 365 connection, you will need to make the root an actual site collection since DryvIQ cannot create a new site.  

(warning) Currently, SharePoint Online does not prevent you from creating a document library (subsite) named “sites.” If you will be using a tenant-level connection to SharePoint, you must ensure your site does not contain a document library (subsite) named “sites.” Otherwise, all data for the migration will be transferred to the “sites” library rather than the top-level site. Since “sites” is a managed path in SharePoint, you will not be able to browse to this location to locate the data.

Optional

Behavior When Deleting Items

Select the type of 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 a deleted. You can still access them to restore or permanently delete the items.

A permanent delete removes the items. This delete is not reversible.

Optional


Microsoft Login

...

Features and Limitations 

...

Supported Features (tick)

Unsupported Features  (error)

Other Features/Limitations (warning)

Version preservation

Mirror lock ownership

Invalid characters:  |   "   \   /   :   *   ?   <   >
See below for more information.

Timestamp preservation

User impersonation

File size maximum: 250 GB Microsoft limit
DryvIQ uses a file maximum size of 249.999999 GB files to ensure transfer. 
See below for additional file size limitations.

Author/Owner preservation


Segment path length: N/A

File lock propagation


Path length maximum: 400

Account map
See below for more information.


Maximum number of files per folder: 5000 

Group map


Maximum Enterprise Keyword length: 255 characters 

Permission preservation


Restricted characters in Enterprise Keywords: < and >

Metadata map
See below for more information.


No leading whitespace 
See below for more information.

Tags map


No trailing periods and whitespace. 
See below for more information.



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.

...

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

Link Remediation

When remediating links from Microsoft OneDrive for Business or Microsoft Office 365, only links in the following format are supported:
https://%3Ctenant%3E-my.sharepoint.com/:w:/r/personal/%3CUser's%20OneDrive%20path%3E/_layouts/15/Doc.aspx?sourcedoc=%7B%3CPlatform%20Id%3E%7D&file=%3CFilename%3E&action=default&mobileredirect=true

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. 

...