Create a Cloud Connection to Upload M365 Purview Exports

Everlaw’s Purview Cloud Connector allows teams to upload Microsoft Purview exports directly into Everlaw.

A Purview export is a review set that you have packaged and prepared for download within Purview. On Everlaw, the documents uploaded through the cloud connection are formatted, accessed, and reviewed the same as those uploaded through a local upload. This includes attachment family grouping, email threading, and chat formatting. Sensitivity labels are not supported.

Establishing this connection requires initial setup by a user with the necessary permissions, after which users with the required Purview and Everlaw permissions can use their own accounts to upload the Purview exports that they have access to. 

This article covers how to set up your Everlaw to Purview connection for the first time. If your cloud connection is already configured, visit Upload M365 Purview Exports via a Purview Cloud Connection to learn how to use the connector.

Requirements

To initially set up and consent to the connection between Purview and your Everlaw organization, you must:

• Have the following Microsoft Admin roles (used for granting consent for apps requesting any permission for any API):
  • Privileged Role Administrator, AND 
  • Cloud Application Administrator or Application Administrator

• Be an eDiscovery Manager in Microsoft
• Have Database Upload permission for the database to which you are uploading
• Have a Purview account with access to any documents you want to export/upload (if you are also performing an upload at this time)

Data security and privacy

When an admin grants permission to form the cloud connection between Everlaw and Purview, they grant Everlaw the following permissions for their Purview tenant:

• eDiscovery.Download.Read
• Read all eDiscovery objects
• Sign you in and read your profile
• Maintain access to data you have given it access to

These permissions are listed in the confirmation dialog that appears during setup.

After the connection is set up, export permissions are authenticated based on the account performing the upload, rather than being associated with the account that initially set up the connection.

To learn how Everlaw handles third party data, please consult our privacy policy. 

Supported formats

You can upload PST exports to Everlaw. For a successful upload, please ensure the following guidelines are met when preparing your exports:

• Exports should be produced from a Purview search (not Review sets or any other workflow)
• The option to organize conversations into an HTML transcript should be disabled
• The option to organize data from different locations into separate folders or PSTs should be enabled

Connect Everlaw to Purview

Before users can use the connector, it needs to be set up with consent from a permitted individual. This requires steps in both Purview and Everlaw.

In Purview:

• Step 1: Check your Purview Admin roles
• Step 2: Confirm that you are a Purview eDiscovery Manager
• Step 3: Enable Purview EDiscoveryApp using Graph Explore

In Everlaw:

• Step 4: Approve the connection in Everlaw

Step 1: Check your Purview Admin roles

To connect Everlaw to your Microsoft Purview exports via cloud connection, you must first verify that you have the necessary Microsoft Admin roles. These roles can be verified from your user account in the Microsoft 365 Admin Center.

The necessary admin roles (used for granting consent for apps requesting any permission for any API) are:

• Privileged Role Administrator
• Cloud Application Administrator or Application Administrator

Alternatively, a custom directory role that includes the permission to grant permissions to applications (for the permissions required by Everlaw) would work as well. These permissions are:

• eDiscovery.Download.Read
• Read all eDiscovery objects
• Sign you in and read your profile
• Maintain access to data you have given it access to

Step 2: Confirm that you are a Purview eDiscovery Manager

Confirm that you are a Purview eDiscovery Manager. This role allows users to export documents from Purview, once the connection between Purview and Everlaw has been established.

Step 3: Enable Purview EDiscoveryApp using Graph Explorer

After confirming your Purview permissions, you will need to enable the MicrosoftPurviewEDiscovery app (App ID: b26e684c-5068-4120-a679-64a5d2c909d9). This creates a service principle, which will allow Everlaw to download your team’s future export(s). 

We highly recommend using Graph Explorer to enable the MicrosoftPurviewEDiscovery app. However, you can also follow Microsoft's Add an enterprise application quickstart to enable the app from Entra.

If you use Graph Explorer, you will need to enter the following information, as well as locateand consent to the permissions required to run the query (also done in Graph Explorer):

• HTTP method: POST
• Endpoint: https://graph.microsoft.com/v1.0/servicePrincipals
• Request Headers: content-type: application/json
• Request Body:

  {
      "appId": "b26e684c-5068-4120-a679-64a5d2c909d9"
  }

For an introduction to Graph Explorer, visit Microsoft’s Use Graph Explorer to try Microsoft Graph APIs. For more information about using Graph Explorer to manage an application, visit Microsoft’s Manage a Microsoft Entra application using Microsoft Graph.

Step 4: Approve the connection in Everlaw

To finish setting up your Everlaw connection to Purview, you must start the upload process from within Everlaw, as it is within the Upload dialog that you'll be prompted to grant consent. This step allows Everlaw to access Purview.

You don't have to finish the upload to grant consent. We'll let you know in the instructions below when it's okay to exit the Everlaw dialog if you're not planning to upload files yourself right away.

When you first connect Everlaw to Purview, you’ll be given the option to consent to granting permissions to your organization. Consenting for the organization allows other users to perform subsequent uploads without needing to re-grant consent. These other users will still be required to log into their own Purview accounts, be an eDiscovery Manager in Microsoft, and have database upload permissions in Everlaw. If you choose not to do this, subsequent users will need to follow the steps in this document. 

Before you start: If you plan to perform your first upload immediately, you should prepare your export in Purview at this point. For more information, visit this article’s section about supported formats.

To approve your Puview connection in Everlaw:

1. Go to Data Transfer > Uploads.
   This takes you to the uploads page.
2. Select Native Upload. Then select Start upload. 
3. Under Collect from cloud application, select Purview.
   
4. You are then prompted to log into your M365 account with access to Purview, or if you're already signed in, select your account. 
5. Assuming your connection has not been fully set up yet, you will have the option to consent to the connection on behalf of your organization. This consent is saved for future uploads, so other users will not need to complete this step. Each user on subsequent uploads is limited to the exports that they have access to within Purview, based on their permissions and access within Purview.
   To consent, select Consent on behalf of your organization.
   
6. Select Accept to continue with the upload.
   

   Note

   If you are only setting up the connection, and are not ready to perform an upload, you can exit the dialog at this point. The connection configuration is complete. You may also continue to create your first upload.

7. The Upload from Purview dialog appears. Here you can choose your case.
   On the Cases step, select the case that contains the export you'd like to upload.
   
8. Select Next to move on to the Exports step. 
9. On the Exports step, choose the export you want to upload.
   
10. If you are happy with your selection, select Continue.  Otherwise, select Previous to edit your choice.
11. 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.

Prepare your team

Once a Purview Cloud Connection has been established, you can direct your team members to the following article to perform their own uploads: Upload M365 Purview Exports via a Purview Cloud Connection.