Purview Sync

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

This includes the following Microsoft 365 data:

• Outlook
• Teams
• Copilot
• OneDrive
• SharePoint

Relativity aiR 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 Relativity aiR converting Teams and Copilot data, see Data transformation.

If you are trying to decide between using Purview Sync or Collect, see Choosing to use Purview Sync or Collect.

Prerequisites

Before you get started, you will need the following access in Microsoft 365:

• Access to Entra ID by creating and updating Application registrations.
• A Microsoft 365 account with access to Purview eDiscovery (Premium).
  • The account must either be eDiscovery Manager or eDiscovery Administrator.
  • The account must be a member of the eDiscovery cases it will work with.
  • See Microsoft Purview permissions below for details.

To use Purview Sync, you must:

1. Register an application with Microsoft Purview eDiscovery (Premium).
2. Update Azure permissions.
3. Connect Relativity aiR to Microsoft Purview eDiscovery.

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 a Microsoft 365 E5 subscription, or a related E5 add-on subscription, for anyone collecting data.

E3 licenses only include access to Purview eDiscovery Standard, which does not work with Purview Sync.

Purview Sync supports importing from Microsoft Purview Searches and Review Sets under E5 license.

One of the following licenses are required for Purview Sync:

• 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 Relativity aiR.

Tab Visibility	Other Settings
Purview Sync Import Configuration	Allow Purview Sync

Microsoft Purview permissions

The following roles are admin-level roles to grant eDiscovery permissions, not required for users running Purview Sync jobs:

• Compliance Administrator—to read, configure, and manage compliance permissions in Microsoft Purview.
• eDiscovery Administrator—to create and manage compliance content in Microsoft Purview.

One of the following roles is needed for users running Purview Sync jobs:

• eDiscovery Administrator—Purview role, lets a user search organizational content and create, manage, and review data in eDiscovery cases, with access to all cases in the organization (not just their own) and the ability to configure solution-wide eDiscovery settings.

• eDiscovery Manager—Purview role, lets a user search organizational content and access/manage the eDiscovery cases they're a member of (automatically, as the creator, or added by someone else), but not other cases in the organization.

For full reference on Microsoft Purview eDiscovery permissions, see Microsoft's documentation.

Purview search and review set differences

You can use either a review set or search as a source in Microsoft Purview while importing data to Relativity aiR with Purview Sync. Both require Premium (E5) license.

A few things behave differently depending on the source:

	Search	Review set
Result repeatability	Point-in-time — reflects the tenant at the moment of the export request; the same search re-run later can return different results	Static, immutable copy — repeatable
Message/conversation export format	Mail → MSG; Teams/Copilot conversations → HTML transcript → RSMF	Native original file formats (originalFiles); Teams/Copilot conversations → HTML → RSMF
Export package retention	14 days from export creation, then auto-deleted	30 days to download after export completes (export process retained for the life of the case)
Metadata field completeness	66/162 documented MSFT fields populated in the loadfile; known gaps incl. File Name on RSMF conversation parents, File ID, Family ID, File class are blank natively	135/162 fields populated; File Name, File ID, Family ID, File class are populated natively by Purview
Email with regular attachment	Relation created, no duplicated attachments	Relation created, attachments duplicated
Email with Linked Cloud File	Relation not created, no duplicated attachments	Relation not created, no duplicated attachments
Teams message with regular attachment	Relation created, no duplicated attachments	Relation created, no duplicated attachments
Teams message with Linked Cloud File	Relation not created, no duplicated attachments	Relation created, no duplicated attachments

Supported data formats

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

Here is what is supported for particular formats:

Item/Format	Support status	What this means
Teams (RSMF)	Supported	Both Teams chats and their linked attachments are imported and converted to RSMF. A proper family relationship is created between the chat (parent) and attachment (child). For more information, see Relativity Short Messaging File conversion.
Emails with modern attachments	Partially Supported	Both the email and its linked attachment are imported. However, Purview Sync does not currently create a family relationship between the email and its attachment.
Sensitivity labels, retention labels, tags, and other Microsoft Purview labels	Supported	Any labels included in the Purview load file are imported into Relativity. Sensitivity Labels are exported as GUIDs, not display values—this is expected and confirmed by Microsoft.
Text redacted in Microsoft Purview	Unsupported	Redacted text is not included in the Microsoft load file, so Purview Sync cannot import it.
Cards, Viva Engage, Loop components	Partially Supported	These items are imported with limitations. See Relativity Short Messaging File conversion for details.
Fluid and Whiteboard messages	Unsupported	These message types are not currently imported or converted by Purview Sync.

Choosing to use Purview Sync or Collect

There are differences to consider when choosing to use Purview Sync or Collect. Use the following table to select the best application to import Microsoft 365 data into Relativity aiR:

Category	Purview Sync	Collect
Primary use case	Used when organizations use Microsoft Purview Premium and want to import full searches or review sets.	Used to locate and collect M365, GCC, and GCC High data directly into Relativity aiR without Purview.
Data sources and importing	Imports entire searches and review sets from Microsoft Purview.	Collects data directly from Microsoft sources using built‑in connectors.
Licensing requirements	Requires Microsoft Purview Premium.	Most workflows supported with M365/GCC E3. Teams collections require E5.
Permissions For more information, see Delegated and application permissions.	Uses delegated permissions. Access limited to the signed‑in user's permissions.	Uses application permissions. Provides tenant‑level access.
Inactive mailboxes For more information, see, Inactive and archived mailboxes.	Supported.	Supported.
Archived mailboxes For more information, see, Inactive and archived mailboxes.	Supports archived mailboxes.	Supports online archived mailboxes via EWS.
Best fit	Organizations already invested in Purview Premium workflows and search- and review set–based collection.	Organizations needing direct collection from M365/GCC into Relativity aiR without Purview dependency.

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 with the Exchange Web Services (EWS) API. For more information, see Microsoft 365 - Outlook data source.

Collect also provides support for inactive mailboxes with the Microsoft 365 Inactive mailboxes. For more information, see Microsoft 365 - Inactive mailboxes data source.

Teams data

Collect uses the Teams API endpoints.

• The Teams export does not currently support access to preserved Teams chat messages.
• This endpoint does not navigate to recoverable items folders. For example, the SubstrateHold folder.