Purview sync
To use Purview sync, you will need to register an application with Microsoft Purview eDiscovery (Premium), update Azure permissions, and connect RelativityOne to Microsoft Purview eDiscovery.
For more information on the Microsoft Purview, see Microsoft's documentation for Microsoft Purview compliance portal.
Prerequisites
Before you get started, you will need the following access in Microsoft 365:
- Access to Entra ID by creating and updating Application registrations. For more information, see Registering Purview Sync with Microsoft.
- A Microsoft 365 account with access to Purview eDiscovery Premium. Either eDiscovery Manger or eDiscovery Administrator. For more information, see Configure Purview Sync.
Licensing requirements
To use Purview Sync, your organization must have an Office 365 E5 subscription for your custodians, or related E5 add-on subscription. If you only have E3 licenses, the you are only able to use Purview eDiscovery Standard. which does not currently work with the Purview Sync application.
- Microsoft 365 E5
- Office 365 E5
- Microsoft 365 Education A5
- Office 365 Education A5
- Microsoft 365 F5 Compliance add on or F5 Security and Compliance add on
- Microsoft 365 G5
- Microsoft 365 G5 with G5 eDiscovery and Audit add on
- Microsoft 365 E3 with E5 Compliance add on
- Microsoft 365 E3 with E5 eDiscovery and Audit add on
Permissions
To complete the entire Purview Sync workflow, you will need the following permissions.
| Object Security | Tab Visibility | Other Settings |
|---|---|---|
| Advanced eDiscovery Case - View, Create, Edit, Add, Delete |
Purview Sync
|
|
| Advanced eDiscovery Import - View, Create, Edit, Add, Delete | Import |
Considerations
| Purview Standard | Purview Premium |
|---|---|
| Attachments in 1-on-1 chats are not exported through eDiscovery Standard. They must be collected from OneDrive separately. Inline images are present. | Code snippets lack the actual snippet in HTML. |
| Read status may be incorrect. The read/unread flag might display inaccurately. | Not all delivery options are visible; Important works, but Urgent does not. |
| PSTs occasionally export corrupt and require reattempting. | Cards are captured but do not display the card contents. |
| Join/Leave events are not available when the search query is configured for type: Instant Messages/kind of: Microsoft Teams. | Duplications occur for each custodian when dealing with multiple custodians. |
| Reactions are missing when the event content is an attachment. | Reactions are missing for all tested items, specifically for group and direct messages. Tested items include GIFs, attachments, messages, and others. |
| Reactions are missing for all tested items. This includes GIFs, attachments, messages, and others. | |
| Sometimes edit information is absent, and the edited state of the event is presented as the original. | |
| Edit information is missing for announcements. | |
| Code snippets lack the actual snippet in HTML. | |
| Attachments are referenced separately through SharePoint. | |
| Cards are captured but do not display the card contents. | |
| When dealing with multiple custodians, duplications occur for each custodian. | |
| Co-pilot chats are visible but can only be viewed by downloading them. They cannot be viewed within the application. | |
| Chat reviews display conversations in a random order, making it challenging to follow the discussion. | |
| Meeting Audio/Video files are not exported. |
Choosing to use Purview Sync or Collect
Purview Sync is a more sophisticated search capability than the MS Graph API. For customers who want to limit their search results they should use Purview Sync. For broader searches and imports using general date range or file types, you can use Collect.
You must have an E5 license to collect Teams data and email archives using Collect. For more information, see Collect. You need an E5 license for Advanced Discovery in Purview. For more information, see Importing data.
| Data collected | Collect | Microsoft Purview Standard | Microsoft Purview Premium |
|---|---|---|---|
| DM content | |||
| Text | Yes | Yes | Yes |
| File attachments | Yes | Yes. Reference the attachment and puts separately through SharePoint. | Yes |
| Reactions | Yes | No | Yes |
| Emojis | Yes | Yes | Yes |
| GIFs | No | Yes | Yes |
| Edits | Yes | Yes | Yes |
| Deletes | Yes | Yes | Yes |
| Delivery options | No | No. Attachment is not available. We see a text string. | No. |
| Cards | Yes. Captures the text that it was added, but nothing else. | Yes. Cannot see the contents of the card. | Yes |
| Senders | Yes | Yes | Yes |
| Recipients | Yes | Yes | Yes |
| Tabs metadata | Yes | Unsure | Yes |
| Code Snippet | Yes | No | No |
| Meeting A/V | No | Yes | Yes |
| Channel content | |||
| Text | Yes | Yes | Yes |
| File attachments | Yes | Yes. Reference the attachment and puts separately through SharePoint. | Yes |
| Reactions | Yes | Yes | Yes |
| Emojis | Yes | Yes | Yes |
| GIFs | No | Yes | Yes |
| Edits | Yes | Yes | Yes |
| Deletes | Yes | Yes | Yes |
| Cards | Yes. Captures the text that it was added, but nothing else. | Yes. Cannot see the contents of the card. | Yes. Cannot see the contents of the card. |
| Senders | Yes | Yes | Yes |
| Recipients | Yes | Yes | Yes |
| Tabs metadata | Yes | Yes | |
| Code snippet | Yes | No | No |
