What is the Dynamics 365 Integration?
The Dynamics 365 integration is Fluint's third CRM connector, alongside Salesforce and HubSpot. Once connected, Fluint syncs your Dynamics accounts, contacts, opportunities, and users on a schedule. Opportunities show up as deals in Fluint, Olli can query your Dynamics data in chat, and documents you publish on a Dynamics-connected deal push back to the opportunity as a Note with an HTML attachment.
Like the other CRM connectors, the Dynamics integration works across these surfaces:
Surface | What it does |
Sync | Pulls accounts, contacts, opportunities, users, and process stages from Dynamics into Fluint on a schedule |
Deals | Dynamics opportunities appear as deals in Fluint, owned by the matching Fluint user |
Olli | Olli can search your Dynamics accounts, contacts, and opportunities directly in chat |
Document sync | When you publish a document revision on a Dynamics-connected deal, the rendered document pushes back to the opportunity timeline as a Note |
Where to Find It
Go to Settings > Integrations and look for the Microsoft Dynamics 365 tile in the CRM section.
If you don't see Dynamics 365 as an option, the integration may not yet be enabled for your organization. Contact [email protected] and we'll turn it on.
Before You Connect
To connect Dynamics 365 you'll need two things from your Microsoft environment:
Your Dynamics org subdomain, in the form
yourorg.crm.dynamics.com. You can find this in the address bar of your Dynamics app. The.crm.dynamics.comending varies by region (for example.crm4.dynamics.comin Europe) so use whatever appears in your browser.An Azure AD / Entra account that has permission to grant access to Dataverse on behalf of your organization. Most admins have this; some tenants require a Global Admin to approve the first connection.
You do not need to create your own Azure app registration. Fluint uses a single shared Azure app that your admin approves once during the OAuth handshake.
Connecting Your Dynamics Instance
Go to Settings > Integrations and click Microsoft Dynamics 365.
Enter your Dynamics org subdomain (for example
contoso.crm.dynamics.com) and click Continue.You'll be redirected to Microsoft to sign in. Review the permissions Fluint is asking for and approve.
Microsoft redirects you back to Fluint. The integration tile will now show as Connected.
Once connected, the first sync starts automatically. Depending on the size of your Dynamics instance, it can take anywhere from a few minutes to a couple of hours before all of your accounts, contacts, and opportunities are visible in Fluint.
What Fluint Syncs
The Dynamics integration syncs the following entities on a schedule:
Entity | What Fluint uses it for |
Users (systemuser) | Mapping Dynamics opportunity owners to the matching Fluint user, so deals are owned by the right person |
Accounts | Powering account research, account digests, and the unified account view across CRMs |
Contacts | Populating buyer context on deals and feeding contact-level research |
Opportunities | Creating deals in Fluint, including owner, stage, value, and close date |
Process stages | Populating the list of stages you can filter opportunities by |
Fluint does a full pull every sync for Dynamics (Dynamics does not support incremental reads the way Salesforce and HubSpot do). To keep the integration fast and avoid hitting Dataverse rate limits, the default sync interval is longer than the other CRMs. If a change you made in Dynamics hasn't shown up yet, give it a sync cycle and check again.
Owner Mapping
When Fluint creates a deal from a Dynamics opportunity, it sets the deal owner to the Fluint user whose email matches the opportunity owner's email in Dynamics.
A few notes on how matching works:
Fluint checks both the primary email on the Fluint user and any alternate email on the account.
Dynamics often uses the
*.onmicrosoft.comtenant email (internalemailaddress) as the system user's email. If your Fluint account only has your vanity domain email on file, add your*.onmicrosoft.comaddress as an alternate email so opportunities owned by you in Dynamics land on you in Fluint.If a Dynamics opportunity has an owner who doesn't match any user in your Fluint org, the opportunity is skipped and no deal is created until a matching user exists.
You can see which opportunities were skipped for owner-mapping reasons in your integration activity feed.
Opportunity Filtering
By default, Fluint pulls every open opportunity from Dynamics. You can narrow this down using stage filters so that only opportunities in specific pipeline stages become deals in Fluint.
Set these in Settings > Integrations > Microsoft Dynamics 365 > Filters. The list of available stages is populated from the process stages synced from your Dynamics org.
Filter changes apply on the next sync. Opportunities that no longer match your filter stay as deals in Fluint but stop receiving updates.
Olli + Dynamics
Once your Dynamics data is synced, Olli can query it directly in chat. You can ask Olli things like:
"Show me all open opportunities for Acme Corp."
"Which contacts at Contoso have we been emailing?"
"What's the pipeline value of my Dynamics deals closing this quarter?"
Olli uses the Dynamics data synced into Fluint, so results reflect the most recent sync rather than a live query against your Dynamics org. If you just made a change in Dynamics and don't see it in Olli's answer, wait for the next sync.
Document Sync: Publish to Dynamics as a Note
When you publish a document revision on a Dynamics-connected deal, Fluint pushes the document to the opportunity's timeline as a Note with a downloadable HTML attachment.
Here's how it works:
The Note's title matches the document title in Fluint.
The Note has a short body pointing to the attachment ("Synced from Fluint. Open the attachment to view the document.").
The attachment is an HTML file containing the rendered document content. Opening it in a browser shows the document with its original formatting.
Subsequent revisions update the same Note in place rather than creating a new one.
Document sync fires about a minute after you publish to avoid creating duplicate Notes while you're still editing.
Requirements for document sync
The document must be attached to a Fluint deal (not an account-only document). Account-level document sync for Dynamics isn't available yet.
The deal must be connected to a Dynamics opportunity (Fluint sets this automatically when the opportunity promotes into a deal).
Known Limitations
Sync
Full pulls every sync — Dynamics doesn't support incremental reads, so every sync pulls all accounts, contacts, and opportunities. This means sync intervals for Dynamics are longer than for Salesforce or HubSpot.
Email activity not synced yet — Fluint does not currently sync Dynamics email activities. Email-based signals (recent inbox activity, engagement timing, etc.) won't appear for Dynamics contacts until this ships.
Core objects only — Accounts, contacts, opportunities, users, and process stages. Custom entities and non-core Dynamics objects aren't synced.
Owner mapping
Users without matching Fluint accounts are skipped — If a Dynamics opportunity owner has no corresponding Fluint user, the opportunity is skipped until a matching user exists.
Mismatched emails — If the email on a Fluint user doesn't match the
internalemailaddressof the Dynamics systemuser, add the Dynamics email as an alternate on the Fluint user.
Document sync
Deals only — Document sync requires the document to be attached to a deal connected to a Dynamics opportunity. Account-only documents aren't synced to Dynamics.
Plain-text Note body — The Note body in Dynamics is a short pointer string. The actual rendered content is in the HTML attachment on the Note.
No deletion — Deleting a document in Fluint does not delete the Note in Dynamics. Matches the behavior of our Salesforce and HubSpot connectors.
Azure
Secret rotation — The shared Azure app's client secret rotates periodically. Fluint manages this; no action is required on your end unless [email protected] contacts you.
Troubleshooting
I don't see Microsoft Dynamics 365 in my integrations list
The integration may not yet be enabled for your organization. Contact [email protected] and we'll turn it on.
OAuth fails with "admin approval required"
Your Microsoft tenant requires a Global Admin to approve the Fluint app the first time anyone in your org connects. Ask a Global Admin to run through the connection flow once. After that, regular users can connect without a separate admin approval.
The connection succeeded but no data is showing up
Sync runs on a schedule. For a fresh connection, the first sync can take anywhere from a few minutes to a couple of hours depending on the size of your Dynamics instance. Check back after the next sync cycle.
If several hours have passed and nothing is showing, contact [email protected].
An opportunity in Dynamics isn't showing up as a deal in Fluint
Check that the opportunity's owner has a matching Fluint user (see Owner Mapping above). Opportunities with unmatched owners are skipped.
Check your stage filters in Settings > Integrations > Microsoft Dynamics 365 > Filters. If the opportunity's current stage is excluded by a filter, no deal is created.
Confirm the opportunity exists in the same Dynamics org you connected. Fluint only syncs the org whose subdomain you entered during setup.
A deal in Fluint has the wrong owner
The deal owner is set to the Fluint user whose email matches the Dynamics opportunity owner's email. If that's wrong, check whether the Dynamics user uses a tenant
*.onmicrosoft.comaddress that doesn't match the email on the Fluint user. Adding the tenant email as an alternate on the Fluint user fixes the mapping on the next sync.
Documents I publish aren't appearing in the Dynamics opportunity timeline
Confirm the document is on a deal (not account-only). Account-only document sync for Dynamics isn't available yet.
Confirm the deal is connected to a Dynamics opportunity. If the deal was created manually and never promoted from an opportunity, document sync won't fire.
Document sync has a short debounce (about a minute). Check the opportunity timeline again after a minute or two.
Confirm your Dynamics connection is still healthy. A disconnected or expired integration prevents document sync from firing.
The sync seems slow
Dynamics syncs are full pulls, so they take longer than Salesforce or HubSpot. Sync cadence is tuned conservatively to protect against Dataverse rate limits. If you believe your org's sync cadence is materially too slow for your workflow, contact [email protected].