Capturing audio, video, and screen content from Teams meetings for later review or sharing
Hi @Monica Schultz,
Thank you for reaching out regarding your eDiscovery metadata inquiry.
In Microsoft 365 eDiscovery exports, SkypeSpacesData\TeamsMeeting does not appear to be a standard user-facing file extension such as .docx, .xlsx, or .mp4. Instead, it is more likely the original mailbox path/location of the item rather than the file type itself.
Within the M365 ecosystem, Microsoft stores Teams collaboration data including meeting metadata, chat histories, and call logs in hidden folders within the user's mailbox to ensure it can be indexed for compliance and retention.
When data is ingested into Relativity, the system populates metadata fields based on the original source extract:
- Original path / folder path: This field identifies where the item was located at the time of collection. In this instance, SkypeSpacesData\TeamsMeeting indicates that the item was extracted from the specific subfolder Microsoft dedicated to Teams meeting data.
- Item class / message kind: These fields identify what the item actually is. For example, a Teams call log might have an Item Class of IPM.SkypeTeams.CallLog.
To definitively identify the underlying data type of these records within your Relativity environment, I advise reviewing the following metadata columns:
- Item class (or message class): Look for values starting with IPM.SkypeTeams or IPM.Note, which dictate how the message is handled by Exchange.
- Message kind: This field will often categorize the item broadly (e.g., microsoftteams or im).
- Original file extension: If the item was an actual attachment to a meeting, this field will display the true extension (like .pdf, .docx).
I hope this helps clarify and please let me know if you require further assistance.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.