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.)
One-Time Global Admin Tenant Authorization
DryvIQ requires a one-time Microsoft 365 Global Administrator to authorize connection to the customer's Microsoft 365 (Office 365/SharePoint and OneDrive for Business) tenant. DryvIQ facilitates this authorization when creating the connection. The authorization requires a Microsoft 365 Global Administrator to sign in and authorize DryvIQ's connection to the tenant.
After initial authorization, you can use any user account to create a connection between DryvIQ and Microsoft 365, and DryvIQ no longer needs to use the Microsoft 365 Global Administrator account. You must add the account used for the DryvIQ connection as the Site Collection Administrator for each SharePoint Site or OneDrive for Business user being migrated.
If you prefer not to use the Microsoft 365 Global Administrator account, DryvIQ Consulting Services can assist with an alternate option that grants authorization outside of the DryvIQ Platform.
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 administrator account with the proper privileges to manage Microsoft 365 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.
| 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
|
Required |
| Token endpoint | This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value. | |
| Graph API endpoint | This setting is rare for most Microsoft connections and can be left blank. If needed, your administrator will provide this value. | |
| External users notification |
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. |
|
| 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 |
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
| Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
| Account Map | Mirror Lock Ownership |
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 | User Impersonation | Path Length Maximum: 400 |
| File Lock Propagation | Restricted Types: N/A | |
| Group Map | Segment Path Length: N/A | |
| Metadata Map |
Invalid Characters: | " \ / : * ? < > See below for more information. |
|
| Permission Preservation | Maximum number of files per folder: 5000 | |
| Tags Map | Maximum Enterprise Keyword length: 255 characters | |
| Timestamp Preservation | Restricted characters in Enterprise Keywords: < and > | |
| Version Preservation | No leading whitespace See below for more information. |
|
| 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. |
File and Folder Name Restrictions
The following are restricted file/folder names. For more information on Office 365 restrictions, see Microsoft’s official documentation.
|
|
|
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. DryvIQ handles invalid characters 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 it cannot migrate 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, allowing DryvIQ to transfer the files and folders. 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.
DryvIQ will sanitize file names that contain combined Unicode characters by replacing the characters with an underscore (_).
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.
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.