Microsoft Teams PST Connector

Back To Connectors Page

Messaging & Collaboration | Connector for Microsoft Teams via PST

What Is the Shield Connector for Microsoft Teams PST?

PST — Personal Storage Table — is Microsoft’s file format for storing email messages, calendar items, and other data exported from Microsoft Exchange and Outlook. In the context of Microsoft Teams compliance, PST-format exports are generated when Teams message data is surfaced through Microsoft’s eDiscovery and compliance export tooling — including Microsoft Purview — producing Teams chat and channel message records in a format that can be ingested by third-party compliance and archiving platforms.

Shield’s Microsoft Teams PST connector ingests Teams message data exported in PST format directly into Shield’s compliance platform, making exported Teams communications immediately available for AI-powered surveillance, investigation, and eDiscovery alongside every other channel the firm uses. This connector is particularly relevant for firms that export Teams data from Microsoft Purview or equivalent Microsoft compliance tooling for ingestion into a third-party compliance archive, and for firms undertaking retrospective compliance reviews or investigations that require historical Teams message data to be ingested into Shield from PST-format exports.

Teams PST exports represent a specific data delivery mechanism rather than a real-time capture approach. Unlike Shield’s native Microsoft Teams connector — which captures Teams messages directly and continuously as they are generated — the Teams PST connector processes Teams data that has already been exported from the Microsoft environment in PST format. This makes it appropriate for specific use cases: retrospective ingestion of historical Teams data, investigation-driven exports of specific Teams message populations, migration of Teams data from one compliance archive to another, and scenarios where real-time API-based capture is not available or not yet deployed.

As a record of business communications conducted in connection with regulated activity, Teams message data exported in PST format carries the same compliance obligations as Teams data captured by any other mechanism. Every Teams message relating to a trade, an order, a client instruction, or a business decision that is exported in PST format is potentially in scope for the same regulatory recordkeeping, supervision, and surveillance requirements that apply to live Teams capture — and firms must ensure that PST-format Teams exports are handled with the same compliance fidelity as any other regulated communication record.

Why Microsoft Teams PST Compliance Is Complex

Microsoft Teams data exported in PST format presents compliance challenges that are specific to the PST delivery mechanism and distinct from those of real-time Teams capture. Several issues arise consistently across regulated firms:

PST as a point-in-time export, not continuous capture. PST-format Teams exports represent a snapshot of Teams message data at the point of export — not a continuous, real-time compliance record. Firms relying solely on PST exports for Teams compliance archiving may have gaps between export cycles, and the export process itself introduces a delay between message generation and archive availability. A PST-based approach is appropriate for specific use cases — retrospective review, investigation support, historical migration — but is not a substitute for real-time capture where ongoing compliance obligations require continuous ingestion.
PST format and data fidelity. When Teams message data is exported to PST, the export process converts Teams-native data structures — including channel messages, thread replies, reactions, and Teams-specific metadata — into the PST format, which was originally designed for Exchange email data. This conversion can result in loss of fidelity, flattened thread structures, missing metadata fields, and altered data representations that differ from the Teams-native record. Compliance solutions that ingest PST-format Teams exports without accounting for these conversion artifacts produce archives that may not accurately represent the original Teams communication.
Thread and conversation structure preservation. Teams chat is structured around threads — with replies nested beneath parent messages in a way that preserves conversational context. PST exports of Teams data may not preserve this thread structure consistently, depending on the export configuration and the version of Microsoft Purview used. Compliance archives built from PST exports must account for this and reconstruct or preserve thread relationships to ensure that conversations are represented accurately for surveillance and investigation purposes.
Metadata completeness in PST exports. Teams-native metadata — including channel identifiers, workspace identifiers, participant data, message types, reaction data, and edit and deletion records — may not be fully preserved in PST-format exports. Solutions that ingest PST Teams data without enriching or restoring this metadata produce records that are incomplete for surveillance, investigation, and regulatory examination purposes.
Integration with real-time Teams capture. Firms that deploy both real-time Teams capture and PST-based historical ingestion must ensure that the two data sources are correctly integrated in the compliance archive — with deduplication logic that prevents the same messages from appearing twice, and with consistent metadata handling that allows PST-ingested historical records to be searched and produced alongside real-time capture data in a unified workflow.

Key Features of the Shield Microsoft Teams PST Connector

Complete PST-Format Teams Data Ingestion. Shield ingests Microsoft Teams message records exported in PST format — including channel messages, direct messages, group direct messages, meeting chat, and thread replies — preserving full message content and all available metadata fields. All data is ingested in full, with zero data loss during the PST-to-archive conversion process.

Thread and Conversation Structure Restoration. Shield preserves and restores the thread structure of Teams conversations exported in PST format — maintaining or reconstructing parent-reply relationships, chronological sequencing, and conversational context as accurately as the PST export data permits. This ensures that PST-ingested Teams records are available for surveillance and investigation with the same conversational fidelity as real-time captured data.

Full Metadata Preservation and Enrichment. Shield retains and enriches all available metadata from PST-format Teams exports — including channel and workspace identifiers, participant data, message types, timestamps, and message IDs — supplementing PST-level metadata with Teams-native metadata where available from the export. This metadata is made fully searchable and stored as part of the immutable compliance record.

Immutable, Audit-Ready Archive. All Teams PST data ingested by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations. Retention periods are fully configurable to meet jurisdiction-specific requirements — including the six-year standard under SEC Rules 17a-3 and 17a-4, the five- to seven-year requirements under MiFID II and MAR, and the five-year requirements under CFTC Regulation 1.35.

Deduplication and Integration with Real-Time Teams Capture. Shield’s Teams PST connector includes deduplication logic that correctly identifies and reconciles PST-ingested historical Teams records alongside messages captured via real-time Teams archiving — ensuring that the unified compliance archive is complete without generating duplicate records that would distort surveillance outputs or inflate review volumes.

Out-of-the-Box AI Surveillance Models. Shield applies pre-configured AI surveillance models to PST-ingested Teams data, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, and personal misconduct — enabling retrospective surveillance of historical Teams archives with the same AI capability applied to current-generation real-time capture.

Unified Cross-Channel Surveillance. PST-ingested Teams data does not exist in isolation. The same employees whose Teams messages are ingested via PST are also communicating — historically and currently — over Bloomberg IB, email, Symphony, and other channels. Shield ingests Teams PST data into the same unified compliance platform as every other channel, enabling compliance teams to correlate historical Teams records with communications from all other sources in a single investigation workflow.

Data Governance and Chain of Custody. Shield’s Teams PST connector preserves a complete, verifiable chain of custody from PST ingestion through archiving and retrieval. Every stage of data handling is logged, auditable, and reportable — giving compliance officers and legal teams the confidence that PST-ingested Teams records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

Microsoft Teams message records ingested via PST carry the same regulatory obligations as Teams data captured by any other mechanism. The Shield Teams PST connector supports compliance with:

SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant, non-rewriteable format with an audit trail, for a minimum of six years.
FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their business as such — including email — with written supervisory procedures, supervision requirements, and full audit trail capability in place.
MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days, and to monitor communications for indicators of insider trading, front-running, and market manipulation.
CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to retain records of all communications relating to commodity interests and swap transactions as part of a complete audit trail for trade reconstruction.
FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to record and retain relevant electronic communications, including email, for a minimum of five years, and to implement effective surveillance arrangements to detect and prevent market abuse.
GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions, enabling firms with EU operations or EU data subjects to meet GDPR obligations alongside their financial services recordkeeping requirements.

Other Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform — so Teams PST data is always reviewed in the context of every other channel your workforce uses.

Frequently Asked Questions

How does the Teams PST connector differ from the native Microsoft Teams connector?

Shield’s native Microsoft Teams connector captures Teams messages directly and continuously as they are generated — providing real-time, API-based ingestion with full Teams-native metadata fidelity. The Teams PST connector ingests Teams data that has already been exported from the Microsoft environment in PST format — a point-in-time mechanism appropriate for retrospective, historical, or migration use cases. Many firms deploy both: the native Teams connector for ongoing real-time capture, and the Teams PST connector to ingest historical data or specific investigation-driven exports. Shield’s deduplication logic ensures the two data sources are correctly integrated without creating duplicate records.

Does PST export preserve the full fidelity of Teams message data?

Not always. The PST format was designed for Exchange email data, and exporting Teams data to PST involves converting Teams-native data structures — including thread replies, channel context, reactions, and Teams-specific metadata — into PST. This conversion can result in flattened thread structures, missing metadata fields, and altered data representations. Shield’s Teams PST connector accounts for these conversion characteristics, restoring thread structure where possible and enriching metadata to maximise the fidelity of PST-ingested Teams records within the compliance archive.

Can PST-ingested Teams data be searched and produced alongside real-time captured Teams data?

Yes. Shield ingests Teams PST data and real-time Teams capture data into the same unified compliance archive, with deduplication logic to prevent duplicate records. Both data sources are searchable and producible in a single unified workflow — compliance teams and legal teams can search across historical PST-ingested records and current real-time captured messages without distinguishing between data sources or switching between separate interfaces.

Which regulations does the Shield Teams PST connector help firms comply with?

The Shield Teams PST connector supports compliance with SEC Rules 17a-3 and 17a-4, FINRA Rules 4511 and 3110, MiFID II, Market Abuse Regulation (MAR), CFTC Regulation 1.35 and 17 CFR § 23.202, FCA SYSC 10A, and applicable data privacy regulations including GDPR — applicable to Teams message records ingested via PST export within the active retention and investigation window.

Can Teams PST records be reviewed alongside other channels during an investigation?

Yes. Shield ingests Teams PST data into the same unified compliance archive as every other channel — Bloomberg IB, email, Symphony, voice, and mobile. Investigators can search and reconstruct the complete sequence of a business interaction across all communication types in a single workflow, including historical Teams messages ingested via PST alongside current-generation real-time captured data from all channels.

How should firms handle GDPR obligations for Teams message data ingested via PST?

Teams message data ingested via PST carries the same GDPR obligations as Teams data captured by any other mechanism — including requirements around lawful basis for retention, data subject access rights, and retention limitation. The PST ingestion mechanism does not change the underlying privacy obligations for the data. Shield’s architecture supports privacy-compliant handling of Teams PST data, including configurable retention periods and data residency controls.