Overview

The DryvIQ Microsoft Teams connection enables you to analyze, migrate, copy, and synchronize Microsoft Teams files 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. (See below for more information.)

Creating a Connection

Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Microsoft Teams as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Click Sign in with Microsoft Teams.
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.
Enter the password for the account and click Sign in.
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.)
Click Done to finish creating the connection.

Add Connection Modal for Microsoft Teams

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 using the URL. For example, Microsoft Teams (https://mycompany.sharepoint.com/). If you need to reference the connection by account, use the default name.	Optional
URL	Enter the URL of your Microsoft Teams account. You can find the URL by Logging into Microsoft Teams through a Web browser using the account you want to use to create the connection (teams.microsoft.com). Select Teams from the menu on the left side of the screen. Select the team you wish to connect to and select Files. In the top toolbar utility, select Open in SharePoint. The URL in the address bar is the URL you need to use. It will look something like "https://mycompany-my.sharepoint.com/sites/team/" where mycompany and team will be the site name of your company and the team you selected. Copy the URL through the team name (https://mycompany-my.sharepoint.com/sites/team). Paste the URL into the DryvIQ Application.	Required
Token endpoint	This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value.	Optional
Graph API endpoint	This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value.	Optional
External users notifications	This indicates if you want to send notifications to external users. The default value is No, so notifications will not 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 type of deletion DryvIQ should perform when deleting items: Permanent or Soft. Soft delete is the default behavior. A soft delete marks items as deleted. You can still access them to restore or permanently delete the items. Permanent delete is the recommended behavior. A permanent delete removes the items. This deletion is not reversible.	Optional

Microsoft Login

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. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.

Supported	Not Supported	Other Features/Limitations

Supported	Not Supported	Other Features/Limitations
Version preservation	Mirror lock ownership	Invalid characters: / \| \ : * ? < > See below for more information.
Timestamp preservation	Restricted types	File size maximum: 250 GB Microsoft limit DryvIQ uses a file maximum size of 249.999999 GB to ensure transfer. See below for additional file size limitations.
Author/Owner preservation	Segment path length	Path length maximum: 400
File lock propagation		No consecutive periods
Account map See below for more information.		No leading periods
Group map		No trailing periods before or after extensions
Permission preservation		No leading whitespace See below for more information.
Metadata map See below for more information.		No trailing whitespace before or after extensions See below for more information.
Tags map		No non-printable characters
		No combining characters
		No invalid surrogate pairs
		No leading tildes (~)
		Maximum Enterprise Keyword length: 255 characters
		Transferring Microsoft Lists is not supported.

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.

Connection Pooling

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

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

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