Data transformation (Advanced Access)

Table of Contents (Advanced Access)

Use this table of contents to navigation Purview Sync during the Advanced Access phase.

• Purview Sync (Advanced Access)
• Install Purview Sync (Advanced Access)
• Register Purview Sync with Azure (Advanced Access)
  • Purview Sync Application registration issues troubleshooting
• Configure Purview Sync (Advanced Access)
• Importing data (Advanced Access)
• Data transformation (Advanced Access)

Processing custodians

Purview Sync automatically organizes all imported files by custodians, with custodian definitions derived from the load file imported from Microsoft Purview. Custodians are automatically created by Purview Sync. You can find them after clicking into the Documents tab.

Each custodian is associated with a data source that includes the source path where the custodian's files are saved.

Currently, Purview Sync supports custodial data sources.

Automatic overlay and using Microsoft fields

Overlay in Purview Sync updates existing records in the review workspace by merging or replacing data from the source with corresponding fields in the workspace, based on the fields already existing in the Microsoft Purview load file.

Microsoft Purview creates an export object containing native files alongside a load file that holds all metadata information. Once Relativity processes the files into the workspace, Purview Sync overlays them with metadata from the load file, assuming that the workspace has the necessary fields created. These fields must match the column names in the load file exactly. Purview Sync will not create them automatically.

When creating the metadata fields in RelativityOne for overlay, we recommend to refer to Microsoft documentation. For more information, see Microsoft's documentation.

Relativity Short Messaging File conversion

We automatically convert HTML Teams data into Relativity Short Messaging File (RSMF). For more information about RSMF, see The Relativity Short Message Format .

Teams formats supported by Purview Sync are:

Teams format	Description
Single chat between two users	Supported
Group chat with three or more people	Supported
Messages in Teams and channels	Supported
Threads	Supported
Deleted threads	Supported In Teams, when a thread is deleted, only the top, or root, message is deleted. The replies retain their structure. In Purview Sync, they are classified as Orphaned Replies and marked deleted.
Deleted and edited messages	Supported
Attachments	Supported
Channels	Supported
Deleted chat	Supported
User leaving team	Supported
User deleted	Supported
Archived channel	Supported
Add removed user back to chat	Supported
Tag in chat	Partially supported Exported from Microsoft Purview as an email, processed correctly.
Reply in chat	Supported
Channel name change	Supported
Forwarded message	Supported RSMF is properly generated with user and message. Following the same behavior in Microsoft Purview, it dies not indicate that someone forwarded the message.
Chat with picture	Supported
Chat with shared M365 docs	Supported
Links	Partially Supported RSMF is properly generated with user and message, links are normal text
Chat from audio, video, meeting	Partially Supported Relativity generates the data as RSMF, but as of now user is Unknown User.
Automatically created meeting recording	Partially Supported Relativity makes the video file is available, but the extension is not visible. This makes it difficult to locate.
Scheduled messages	Supported Relativity generates the data as RSMF with user and message. The following the same behavior in Microsoft Purview, it is not indicated that someone scheduled the message.
Translated messages	Supported Relativity generates the data as RSMF with user and message. The following the same behavior in Microsoft Purview, only in original language.
Modern attachments	Partially supported There is a link in Teams’ message, but Purview Sync does not support family relation.
Different alphabets	Supported