On This Page

Overview

DryvIQ connections to Microsoft Teams can be made by using an administrator account with the proper privileges to manage Microsoft Teams configurations. DryvIQ can create this 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 Teams 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 Teams.

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 OneDrive for Business 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.)

8. Select Done to finish creating the connection.

Add Connection Modal - Microsoft Teams

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

Microsoft Teams has the following file/folder restrictions:

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. Invalid characters are handled 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 cannot be migrated due to an unsupported character in the name.

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

Language Translation

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

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.  

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.

Create Connection | REST API

The following GET will return a Microsoft login link. Use the link to complete logging into the account and creating the connection.