Short message conversion for Microsoft Teams
This page covers information for Microsoft Teams (Teams) conversion. To view the Relativity supported and unsupported file type tables, see Supported file types for processing.
Processing can automatically convert discovered Teams conversations within Microsoft eDiscovery (Standard) export data files (PST). For information on enabling short message conversion, including how files should be converted (via slicing), see Short message conversion settings.
Microsoft eDiscovery (Standard) PST exports
- To learn more about exporting Teams data with the Microsoft eDiscovery (Standard) solution, see Feature reference for Content search on the Microsoft website.
- Processing expects data to be provided as a PST container where a single PST might contain both email and Teams data.
- Teams messages are automatically identified based on the message class of emails inside the export, for example, IPM.SkypeTeams (as opposed to i.e IPM.SkypeTeams.Message or IPM.SkypeTeams.SystemMessage.)
- If you have enabled Teams conversion in the processing profile, the original MSG files that contain Teams information are not discovered. If you want to retain the original files, disable RSMF conversion.
- The email processing and Teams conversion jobs are independent within a single container processing. If the conversion fails with a document-level error, email files are still discovered.
- Any attachments embedded inside the PST are extracted and processed; any attachments not inside the PST are kept as links within RSMF files (for example, attachments shared via OneDrive or SharePoint.)
Microsoft eDiscovery (Premium) HTML exports
Microsoft eDiscovery (Premium) HTML exports are currently not supported for RSMF conversion in processing. See Relativity Collect documentation for collection capabilities for Microsoft 365.
Generated RSMF fields
The following table lists the metadata fields found in RSMF files after Teams conversion.
| Relativity source field name |
Description |
|---|---|
| Subject |
The name of the conversation.
|
| EmailFrom | The display name and email of sender of first event in the conversation. |
| EmailTo | A list of display names and emails of all participants in conversation that generated events. |
| Date | The date of first event in conversation. |
| Rsmf/Version | 2.0.0 |
| Rsmf/Participants | A list of display names of all participants in conversation that generated events. |
| Rsmf/Generator | Relativity Processing |
| Rsmf/Application | Teams |
| Rsmf/MessageCount | The number of events in the conversation. |
| Rsmf/AttachmentCount | The number of attachments in conversation. |
| Rsmf/EventCollectionId | The conversation ID that is persisted between file slices. |
| Rsmf/BeginDate | The date and time of first event in conversation. |
| Rsmf/EndDate | The date and time of last event in conversation. |
Known issues and limitations
The Teams metadata available within the PST depends heavily on the Microsoft eDiscovery (Standard) search configuration. The following is a list of known issues and limitations:
- Teams metadata limitations in RSMF conversion capability:
- Giphy app and stickers—GIFs are provided as links in the RSMF files. Only custom text from stickers is available within RSMF files. For more information, see Send en emoji, GIF, or sticker in Microsoft Teams.
- Approvals app—are not available within RSMF files. For more information, see Approvals in Microsoft Teams.
- Praise app—are not available within RSMF files. For more information, see Send Praise to people in Microsoft Teams.
- Loop components—are downloaded as HTML attachments linked in the RSMF files. For more information, see Send a loop component in a channel.
- Meetings—are not available within RSMF files.
- Known issues with Microsoft eDiscovery
(Standard) PST metadata:
- Join/leave events are available only for chats exported with specific Microsoft eDiscovery content search. These are system events, so they are not retrieved if the export is filtered only to instant messages (itemclass:IPM.SkypeTeamsMessage) or Teams (kind:microsofteams)
- Announcements— do not include edit information. For more information, see Send an announcement to a channel in Microsoft Teams.
- Full participant information (full display name and email) becomes unavailable once the participant has left the chat.
Resources
- For information on enabling short message conversion, see Short message conversion settings.
- For information on short message use, metadata, and mapping, see Relativity's short message format.
