What you get
- Every meeting and email updates relationship strength automatically — no CRM data entry
- Pre-meeting briefings pulled from Outlook calendar + Teams activity + public signals
- Detect clients going quiet before your CRM shows any lapse
- Surface internal collaborators who know someone your team is trying to reach
- Enforce firm-wide privacy: inbox contents stay in your tenant; Bionicly sees metadata + sender/recipient graph only
How it works
Bionicly authenticates via Entra ID (Azure AD) using Microsoft's Graph API with an admin-consented app registration. Scopes are narrowly defined and surfaced during install for your admin to review.
Our connector reads message metadata (sender, recipient, subject, timestamp, thread id) and calendar events from Outlook Mail and Calendar, plus membership + channel-activity metadata from Teams. Email body content is never read by Bionicly unless you explicitly opt a user in.
Signals feed the same relationship graph that Salesforce and Dynamics 365 feed. No data leaves your Microsoft tenant permanently — Bionicly retains derived insights in its AWS environment and a reference hash pointing back to the source.
Data flows
- Outlook mail metadata (sender, recipient, subject, timestamp) — via Microsoft Graph
- Outlook calendar events (attendees, times, subject) — via Microsoft Graph
- Optional: Outlook calendar annotations + Teams message summaries, opt-in per user
Reads
- Outlook mail metadata (sender, recipient, subject, timestamp) — via Microsoft Graph
- Outlook calendar events (attendees, times, subject) — via Microsoft Graph
- Teams channel membership + activity metadata
- Entra ID (Azure AD) user and group directory for scoping
Writes
- Optional: Outlook calendar annotations + Teams message summaries, opt-in per user
Storage
Metadata and derived insights only. Message bodies and document contents are never stored by Bionicly unless a user explicitly opts in to full-text analysis for their own inbox.