Data Connectors

Import third-party data into Microsoft 365 for compliance processing. Data connectors bring external communications and content under the same retention, eDiscovery, and compliance policies as native M365 content, ensuring consistent governance across all data sources.

Note: Data connectors require appropriate Microsoft 365 compliance licensing. Some connectors require additional third-party service subscriptions.

Supported Connector Categories

How Data Connectors Work

1. Configure Connector — Set up the connector with source system credentials and authentication
2. Map Users — Map external identities to Microsoft 365 user accounts
3. Schedule Import — Data is imported on a recurring schedule (typically every 24 hours)
4. Store in Mailboxes — Imported data is stored in user mailboxes in a dedicated folder
5. Apply Policies — Retention, DLP, eDiscovery, and communication compliance policies apply automatically

Communication Connectors

Bloomberg Message

Import Bloomberg terminal communications for FINRA and SEC compliance. Captures instant messages, chat rooms, and email-like communications.

Slack

Import Slack workspace messages including channels, direct messages, and shared files. Supports Enterprise Grid deployments.

Zoom

Capture Zoom meeting chat messages and recordings metadata. Integrates with Zoom’s compliance archiving features.

Cisco Jabber

Import Cisco Jabber instant messages and group chats for unified compliance monitoring.

HR Connectors

HR connectors provide signals that enhance insider risk detection:

• Resignation date — Trigger departing employee risk policies
• Termination notice — Identify users requiring enhanced monitoring
• Performance issues — Correlate performance signals with risky behavior
• Job level changes — Track privilege changes and role transitions

Connector Status Dashboard

Data Governance

Imported data is subject to the same governance policies as native M365 content:

• Retention policies — Apply organization-wide or connector-specific retention
• DLP policies — Scan imported content for sensitive information
• eDiscovery — Include imported data in content searches and legal holds
• Communication compliance — Monitor imported communications for policy violations
• Insider risk — Correlate imported signals with M365 activity

Connector Configuration

Prerequisites

• Global Administrator or Compliance Administrator role
• Source system admin credentials or API access
• Microsoft 365 mailboxes for data storage
• Appropriate compliance licenses

Configuration Steps

1. Navigate to Data Connectors in the compliance portal
2. Select the connector type to configure
3. Authenticate with the source system
4. Map external users to M365 accounts
5. Configure import schedule and scope
6. Validate and activate the connector

Troubleshooting

Best Practices

• Map users accurately — Ensure external identities are correctly linked to M365 accounts for proper policy application
• Monitor connector health — Check the status dashboard regularly for import failures or errors
• Test with small scope first — Configure connectors with a subset of users before expanding to full organization
• Review imported data quality — Verify that imported content is complete and properly formatted
• Document connector configuration — Maintain records of connector setup for compliance audits

Warning: Data connector failures can create compliance gaps. Set up alerts for import failures to ensure continuous coverage.

API Reference

• GET /api/compliance/connectors — List all configured connectors
• POST /api/compliance/connectors — Create and configure new connector
• GET /api/compliance/connectors/:id/status — Get connector health and import status
• PUT /api/compliance/connectors/:id — Update connector configuration
• GET /api/compliance/connectors/:id/history — Get import history and statistics