What happens if Microsoft Teams changes their API after we go live?
Our SRE team monitors Microsoft Teams change announcements and rolls compatibility updates inside our maintenance retainer. If a breaking change ships, we own the migration; you don't pay extra to stay current and you don't field calls from the vendor.
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 Buffalo, New York, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
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.
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.
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.
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.