A Connectify-owned Microsoft Teams adapter, not a packaged connector
The platform handles that by keeping the Microsoft Teams adapter inside our own runtime, monitored by our SRE rotation and updated as Microsoft ships breaking changes. That means the field maps, sync cadences, and replay rules are shaped to your exact data model — including Bot Framework + adaptive cards for rich approvals and Audit + retention compliance with Purview hooks. For teams in Springfield, the difference shows up the first time the upstream API throws a 500 — the adapter retries, journals the failure, and never silently swallows a transaction.
