Microsoft Teams
Ingest Teams conversations for approvals and broadcast. Writes require certificate checks and retention alignment with Microsoft Purview.
Monthly verification • last run September 2025
Modes & scopes
Modes
- Read-first
- Write-gated (message posting)
Scopes
- Microsoft Graph delegated app with Team.ReadBasic.All
- ChannelMessage.Send for approved automations
Runbook highlights
Connection modes
Private Azure AD app registration with Conditional Access and Customer tenant consent.
Learning Controls
Response quality monitors ensure governance updates stay within regulatory scripts.
Evidence
Certificates attach team IDs, channel IDs, and Purview retention policy IDs.
Sample automations & evidence
Sample automations
- Notify risk committee of certified write volume
- Collect approvals via adaptive card with certificate link
Action Certificate mapping
Every certificate embeds connector identifiers, residency policy hashes, and Learning Control references so downstream systems can verify scope before allowing writes. Export verification logs to Splunk/Datadog using thetrustplane.certificate_id attribute.
Need a signed runbook?
Request a signed copy of this connector runbook, DPIA, or sub-processor alignment via the security contact form. We respond within one business day and can include environment-specific attestations.
Contact security