Supported

Files can only be archived if the chat is started by an internal party

Supported

Files can only be archived if the chat is started by an internal party

Supported

Files cannot be archived unless the meeting is hosted by an internal party

Supported

Files cannot be archived unless the meeting is hosted by an internal party

Supported

Reactions that are added after the query returned the message, will not be archived. because there is a known bug in the Export API confirmed by Microsoft.

Supported

Initially, the membership information is determined based on periodic membership queries and/or message sender information (there is a chance that this is not 100% accurate all the time. VFC data is only as accurate as the information returned in the periodic query).

From the time a conversation is being recorded, accurate participant information can be determined from join/leave system events.

Supported based on periodic membership queries and message sender information (there is a chance that this is not 100% accurate all the time. VFC data is only as accurate as the information returned in the periodic query).

Participant join and leave times are stored as follows:

• Participant join timestamp: it is based on the timestamp of the last received message in the chat when the membership polling was initiated. This approach means that all the current members of the chat will be treated as they joined since the first message which was returned by the Export API query.
• Participant leave timestamp: it is based on the time when the membership polling returned the membership change (the participant is no longer listed as a participant in the chat). 

Supported for both chats and channels with limitations, participant information is not 100% accurate all the time (see below)

Chat: supported

Channel: supported, but the API only offers team based queries (user based queries are not available, teams have to be configured as recorded extensions)

Chat and channel membership information is collected at the point when the Export API is queried. The accuracy of the chat and channel membership information has no effect on the selective capture, there will be no data loss. However, due to the periodic query nature, the membership information might not be accurately reflected in the database for the chat and channel conversations. See Participant Join/Leave Events for more information.

Supported

Available through regular polling and system events.

Supported

Available through regular polling.

The Webhook/DLP API is a set of Microsoft Graph APIs that allow subscribing to change notification events for both chat and channel messages in a Teams tenant. The Webhook API based integration provides a real-time capture of messages and attachments.

For more information, see https://docs.microsoft.com/en-us/graph/teams-changenotifications-chatmessage

The system utilizes other Graph APIs to collect additional information such as attachments, user information, group membership, etc.

The Export API is a set of Microsoft Graph APIs which allow querying both chat and channel messages for specific users and teams in a Teams tenant. The Export API based integration provides a non real-time capture of messages and attachments.

For more information, see https://docs.microsoft.com/en-us/microsoftteams/export-teams-content

The system utilizes other Graph APIs to collect additional information such as attachments, user information, group membership, etc.

Supported by automatic allocation of archived users and teams to file queues

Note: Recording Director and Media Recorder roles are always co-located for Export API based deployments

Supported by deploying standby servers

Note: Recording Director and Media Recorder roles are always co-located for Export API based deployments

Scales by adding more servers

Note: Recording Director and Media Recorder roles are always co-located for Export API based deployments

• Microsoft only retries sending events a few times, so data can be lost after that. The risk can be mitigated by deploying multiple Recording Directors behind a load balancer.
• Data loss is possible if selective archiving is configured and the participant information is not up-to-date (see Participant Information for more information).

No data loss since the queries can be executed at any time. Microsoft stores messages for the defined retention period (see https://docs.microsoft.com/en-us/microsoftteams/retention-policies). Deleted messages are kept for 21 days only.

Supported

Supported

Chat: data duplication, messages and files are multiplicated based on the number of archived users in the chat

Channel: no duplication, messages and files are stored only once even where there are multiple archived users in the same channel

SMTP-based export only

User/participant-based or conversation/chat based export

SMTP based export only

User/participant based only

For licensing information, please refer to the following Microsoft knowledge base article, "Graph APIs for Teams Data Loss Prevention (DLP) and for Teams Export" section:

https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#microsoft-purview-data-loss-prevention-graph-apis-for-teams-data-loss-prevention-dlp-and-for-teams-export

In addition to the user license requirements above, the owner of the application registration must define the licensing model for the deployment. Model A is required for Security and Compliance (S+C) and general usage scenarios. The licensing model is configurable in the VFC system.

For more information about seeded capacity and consumption fees, see https://docs.microsoft.com/en-us/graph/teams-licenses.

The following limitations should be considered when deploying the Export API based solution:

• The Microsoft Export API only returns the latest version of the message, not the complete history of the message, previous edits will not be returned.
• The onBehalfOf attribute is missing for apps, such as Forms, the sender is not recognized due to this limitation.
• Microsoft has no official SLA for the completeness of the records, we estimate min. 15 minutes, but it is recommended to use the default 1 hour delay for the queries.
• Participant join/leave times are not accurate (see above)
• Reactions that are added after the query returned the message, will not be archived. because there is a known bug in the Export API confirmed by Microsoft (see above)
• Private and  shared channel messages are not supported (change is planned for 9.8.1)