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.
Does it work with our existing Microsoft Teams licenses?
Yes — the adapter rides on top of your existing Microsoft Teams subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
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.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Joliet, Illinois. 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.
Can the Microsoft Teams adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Microsoft Teams tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
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.