How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Microsoft Dynamics 365 adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
Does it work with our existing Microsoft Dynamics 365 licenses?
Yes — the adapter rides on top of your existing Microsoft Dynamics 365 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.
What happens if Microsoft Dynamics 365 changes their API after we go live?
Our SRE team monitors Microsoft Dynamics 365 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.
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 Dynamics 365 surface.
How long does the Microsoft Dynamics 365 integration take to ship?
Our standard window is thirty days from signed scope to live Microsoft Dynamics 365 adapter in production, plus a one-week monitored stabilization phase. For companies running Microsoft Dynamics 365, 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 Dynamics 365 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.