Last date modified: 2025-Nov-21

Purview Sync

Purview Sync is an easy-to-use RelativityOne application for collecting your custodian’s Microsoft 365 data directly from your Microsoft Purview Premium to RelativityOne.

This includes the following Microsoft 365 data:

  • Outlook
  • Teams
  • Copilot
  • OneDrive
  • SharePoint

RelativityOne converts Teams and Copilot data into Relativity Short Message Format (RSMF), automatically overlays metadata load files, processes the data, creates custodians, and prepares it for review. For more information on RelativityOne converting Teams and Copilot data, see Data transformation.

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 Register Purview Sync with Azure.
  • A Microsoft 365 account with access to Purview eDiscovery Premium. Either eDiscovery Manager or eDiscovery Administrator. For more information, see Configure Purview Sync.

To use Purview Sync, you must:

  1. Register an application with Microsoft Purview eDiscovery (Premium). For more information, see Register Purview Sync with Azure.
  2. Update Azure permissions. For more information, see Grant users eDiscovery permissions in Microsoft Purview.
  3. Connect RelativityOne to Microsoft Purview eDiscovery. For more information, see Configure Purview Sync.

For more information on the Microsoft Purview, see Microsoft's documentation for Microsoft Purview compliance portal.

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, then 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 in RelativityOne.

Tab Visibility Other Settings

Purview Sync

  • Import
  • Configuration
Allow Purview Sync

Supported data formats

Purview Sync supports the whole Microsoft 365 data suite, including Inactive and Archived Mailboxes.

Here are prerequisites for particular formats:

  • Teams—for more information, see Relativity Short Messaging File conversion.
  • Modern attachments:
    • Teams chats: supported. Both Teams chats and their linked attachments are imported and converted to RSMF. A proper family relation is created between the parent Teams chat and its child attachment.
    • Emails: partially supported. Both parent email and its linked attachment are imported and converted to RSMF but Purview Sync does not currently establish a family relation between the email and its attachment.
  • Sensitivity labels, retention labels, tags, and other Microsoft Purview labels—supported. Purview Sync imports whichever labels are included in a load file exported together with native files from Microsoft Purview. Please note that for now, Sensitivity Labels are exported as GUIDs and not value. This is an expected behavior confirmed with Microsoft.
  • Text redacted in Microsoft Purview—unsupported as it is not a part of Microsoft load file.
  • Cards, Viva Engage, loop components—partially supported. See Relativity Short Messaging File conversion for details.
  • Fluid and White Board messages—currently unsupported.

Choosing to use Purview Sync or Collect

Relativity designed Purview Sync for customers who already use, or plan to use, Microsoft Purview Premium for eDiscovery work. The Purview Sync workflow supports imports of whole Review Sets, which can contain a variety of M365 data from Microsoft Purview.

Collect is an application which supports imports of data from a variety of sources, including Purview. Each data source is collected separately. Standard (E3) license is sufficient to use Collect, with an exception of Teams data and email archives, which require Premium (E5) license.

Delegated and application permissions

A crucial difference between Purview Sync and Collect applications are Azure Active Directory permissions.

  • Purview Sync uses delegated permissions. Delegated permissions restrict access of a signed-in user to only what they have been granted.
  • Collect uses Application Permissions which give the application a broader, tenant-level access without user context.

Inactive and archived mailboxes

Purview Sync supports inactive and archived mailboxes based on the application’s integration with Microsoft Graph API.

Collect provides support for online archived mailboxes via the Exchange Web Services (EWS) API. Currently, it does not provide support for inactive mailboxes.

Return to top of the page
Feedback