On This Page
Table of Contents |
---|
...
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Microsoft OneDrive for Business 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 OneDrive for Business.
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 on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
Click Done to finish creating the connection.
Add Connection Modal for Microsoft OneDrive for Business
...
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, OneDrive for Business (https://mycompany-my.sharepoint.com/personal/user_mycompany_onmicrosoft_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 OneDrive for Business account. This must be the full URL. If the connection fails, verify the URL. DryvIQ cannot create the connection if the URL is incorrect. You can find the URL by logging into OneDrive for Business using the account you want to use to create the connection. The URL in the address bar is the URL you need to use. It will look something like "https://mycompany-my.sharepoint.com/personal/user_mycompany_onmicrosoft_com" (where mycompany will be the site name of your company). You must use the full URL, or the connection will fail. For example, the following URL is invalid since it is not the complete URL and will result in a failed connection: "https://companydesktop-my.sharepoint.com/personal/". | 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 Login
...
Features and Limitations
...
Supported Features | Unsupported Features | Other Features/Limitations |
---|---|---|
Invalid characters: | " \ / : * ? < > | ||
File size maximum: 250 GB Microsoft limit | ||
Segment path length: N/A | ||
Path length maximum: 400 | ||
Account map | Maximum number of files per folder: 5000 | |
Maximum Enterprise Keyword length: 255 characters | ||
Restricted characters in Enterprise Keywords: < and > | ||
No leading whitespace | ||
Metadata map | No trailing periods and whitespace. | |
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. |
...
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.
...
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.
Platform Item Exception Errors
DryvIQ uses a batch job (uploading multiple files and committing them to the destination asynchronously) to migrates files that do not exist to Microsoft Office 365 or OneDrive for Business connections since this is the best practice for storage providers that offer batch support. If Microsoft responds with an “item already exists” during a batch migration job, DryvIQ compares the latest set of item properties (modified, versions and number of bytes) to the item properties in the batch job. If the properties on the existing destination file do not match the properties in the batch job, DryvIQ will generate an error identifying the conflicting properties as in the example below.
Code Block |
---|
PlatformItemOutOfDateException: The item changed during processing. Retry the item to resolve the issue. Contact support if the problem persists. /TD_7bcd1ca33f274b0bb7a8698f99936f6b/Folder/File.txt with changed properties: timestamp - original:7/3/2024 4:09:49 PM +00:00, latest:7/3/2024 4:09:56 PM +00:00; number of bytes - original:3, latest:8; |
In the error, original
is the item property in the batch job, and latest
is the item property on the destination. The item will be flagged as “Retry” and will be handled like a normal retry item. After selecting the retry action (Retry, Ignore, etc.), the item should be resolved.
If the batch job and destination have the same properties, no error will be generated, and the item will be transferred.