What you get
- Dataverse-backed account, contact, and opportunity data feeds the relationship graph
- Dynamics Sales activity timeline joins with Outlook + Teams signals for the full picture
- Insights delivered via Outlook, Teams, or the Bionicly UI — matches your team's existing workflow
- Single Entra ID (Azure AD) identity for Dynamics + Microsoft 365 — one auth, two integrations
How it works
Bionicly authenticates to Dataverse via Entra ID with read-only scopes. Install uses the same admin-consent flow as the Microsoft 365 connector.
The connector pulls Dataverse entities via the Dataverse Web API: Account, Contact, Lead, Opportunity, Activity, Task, Appointment, plus custom entities you map.
Signals join the Bionicly relationship graph alongside Microsoft 365 and public-web inputs. Write-back is opt-in and configurable per field.
Data flows
Data flow
Dynamics 365
System of record
Reads
Writes back
Reads
- Dataverse: Account, Contact, Lead, Opportunity, Activity, Task, Appointment
- Custom Dataverse entities you map via the Bionicly admin console
Writes back
- Optional, opt-in: insight records written back as Task or custom entity entries
Derived insights + minimal reference hashes only. Raw Dataverse records are not warehoused outside your Microsoft tenant.
Reads
- Dataverse: Account, Contact, Lead, Opportunity, Activity, Task, Appointment
- Custom Dataverse entities you map via the Bionicly admin console
- Dynamics Sales activity timeline
Writes
- Optional, opt-in: insight records written back as Task or custom entity entries
Storage
Derived insights + minimal reference hashes only. Raw Dataverse records are not warehoused outside your Microsoft tenant.