...
Select Connections > 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.
Select 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 select Sign in.
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.)
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
| 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.
...
Microsoft Teams has the following file/folder restrictions:
Supported | Not Supported | Other Features/Limitations |
|---|---|---|
Invalid characters: / | \ : * ? < > | ||
File size maximum: 250 GB Microsoft limit | ||
Path length maximum: 400 | ||
No consecutive periods | ||
Account map | No leading periods | |
No trailing periods before or after extensions | ||
No leading whitespace | ||
Metadata map | No trailing whitespace before or after extensions | |
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.
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.”
...
DryvIQ verifies file and folder names to identify unsupported characters based on the platform. It then replaces 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 (_) so or UTF8 encoding based on the option selected. This will allow the files and folders can to be transferred. The 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.
...
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 |
|---|