You can upload data directly from your Microsoft organization into Everlaw using the Everlaw cloud connection to Office 365. Using this connection, you can upload large volumes of Microsoft data without first downloading them locally.
Requirements
Using the cloud connection to upload data directly into Everlaw from your Microsoft organization requires that you have:
- Database Upload permissions on Everlaw
-
One of the following:
- Global Admin permission for the Microsoft organization
-
Have been granted permissions to upload from the Microsoft organization by a Global Admin
Learn more in our article on Cloud Management.
If you do not have permission to make the cloud connection, you can upload your Microsoft data from your local machine:
- For Teams data, read this article on Uploading Microsoft Teams Files from Your Local Machine.
- Other data stored in your Microsoft organization (Outlook, OneDrive, etc.) can be exported to your local machine and uploaded as native data. Read more Supported Native Data Types and our article on Uploading Native Data to Everlaw.
Data security and privacy
To learn more about how Everlaw handles third party data, please consult our privacy policy.
See our Cloud Management article for a list of permissions requested as part of setting up the connection.
Types of data sources
The following data sources are supported through this cloud connection:
- OneDrive
- Outlook Mail
-
Outlook Calendars
- Group Calendars are currently not supported and will not be included in any Microsoft 365 uploads.
-
Teams
- Teams Chats and Channels are converted to PDFs. The header of each document includes information with the chat channel name, timezone, and chat contributors. Threaded messages are denoted by a box encapsulating messages in the thread.
- The Chat Contributors metadata field is automatically populated with the names of all participants. Everlaw also populates the Start Date and End Date metadata fields with the date and time of the first and last message of the conversation, respectively.
- During upload, you can choose how chat files are segmented. To learn more, see the Chat documents bullet in the Dataset Details step of our Uploading Native Data article.
Everlaw does not support sensitivity labels applied to documents
Upload process
To start an upload:
-
Go to Data Transfer
> Uploads. This takes you to the uploads page.
- Select Native Upload. Then select Start upload.
-
Under Collect from cloud application, select Office 365.
- A dialog box prompts you to log into your Microsoft account. If you are already logged in, you are prompted to select your username.
-
Once you are logged in, an upload wizard opens to guide the upload. Select the Apps you want to upload from.
- When you are done, select Next to move onto the Custodians step.
-
The Custodians step displays a list of all users and shared inboxes in your organization. Select the subset of custodians whose data you would like to upload to Everlaw.
You can filter this list by custodian name or email.
Select the box in the table next to Custodian to select all custodians.
Selecting a user as a custodian means that you will upload any documents this user has access to from the apps you selected in the previous step. - Select Next to move on to the Date range selection step.
-
On the Date range step, you can choose to only upload documents that were created or modified within a certain time frame. Enter the beginning of the time frame in the From date and time fields and the end of the time frame in the To date and time fields, then select the Timezone.
If you do not specify a range, all files associated with your selected custodians and data sources will be uploaded. - Select Next to move on to the Summary step.
- On the Summary step, review your choices. If you're ready to move on, select Continue. Otherwise, select Previous to edit your choices.
- You are taken to Everlaw’s native data upload wizard. Here, you can name your upload, specify deduplications settings, and choose which projects to upload the data to. For more information about these upload settings, read this section of the Native Data Uploads article.
Upload troubleshooting
If a Microsoft 365 upload contains multiple custodians, the upload will still complete even if one or more custodians are unreachable. The upload report of a completed upload can help you troubleshoot unreachable custodians. To access it:
-
On the Native Data page, select the three-dot menu of the relevant upload card, then select View upload details.
-
Go to the Transferring tab. Here, a complete list of custodians whose data was attempted to be uploaded is displayed, along with errors for any sources that could not be uploaded for each custodian.
-
To download a CSV of the errors, select Download. The CSV displays the names of the errored custodians, the custodian ID, and lists the failed Microsoft 365 source(s).
The CSV automatically updates with new errors as an upload is in process. If you download the error report before the upload completes, some errors may not yet be listed on the CSV.
There are many reasons why custodians might be unreachable, including but not limited to:
- Your Microsoft tenant may be configured to restrict application access to specific mailboxes, as described in Microsoft’s documentation here
- Your Microsoft tenant may be configured with application access policies that restrict access, as described in Microsoft’s documentation here
- Your Microsoft tenant may not be configured for Graph API usage
- Your Microsoft account may be suspended or deleted
- The license for your account may not include Graph API usage
- You may have a Microsoft account on the tenant but not an instance of the particular application you are trying to upload