Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »



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

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 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 Microsoft Teams account. 

You can find the URL by

  1. Logging into Microsoft Teams through a Web browser using the account you want to use to create the connection (teams.microsoft.com).

  2. Select Teams from the menu on the left side of the screen.

  3. Select the team you wish to connect to and select Files.

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

  5. Copy the URL through the team name (https://mycompany-my.sharepoint.com/sites/team).

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

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

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

Supported (tick)

Not Supported (error)

Other Features/Limitations (warning)

Version preservation

Mirror lock ownership

Invalid characters: / | \ : * ? < >
(See Invalid Characters and Spaces below.)

Timestamp preservation

Restricted types

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

Author/Owner preservation

Segment path length

Path length maximum: 400

File lock propagation

User impersonation

No consecutive periods

Account map
(See Mapping below.)

No leading periods

Group map

No trailing periods before or after extensions

Permissions preservation

No leading whitespace
(See Invalid Characters and Spaces below.)

Metadata map
(See Metadata Mapping below.)

No trailing whitespace before or after extensions
(See Invalid Characters and Spaces below.)

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.

Connection Pooling

Microsoft Office 365 connections using OAuth 2 authentication may experience bandwidth throttling from Microsoft when using connection pooling.

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.

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


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. 

GET {{url}}v1/connections/platforms/microsoft-teams-graph/new















  • No labels