What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Gilbert, Arizona. After go-live, the Microsoft Teams adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Microsoft Teams adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
How long does the Microsoft Teams integration take to ship?
Our standard window is thirty days from signed scope to live Microsoft Teams adapter in production, plus a one-week monitored stabilization phase. For Gilbert, Arizona, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Do we own the integration code at the end?
Yes. The Connectify Microsoft Teams adapter ships with full source escrow rights — at any point you can request a snapshot of the code, configuration, and runbooks. We prefer you stay on our managed runtime, but you are never locked in.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the Microsoft Teams surface.
Is this a packaged Microsoft Teams connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.