CRM integration guide
Dynamics 365 Sales + UbiGrowth workflows
Dynamics 365 Sales is the sales application in Microsoft Dynamics 365, holding accounts, opportunities, and enterprise sales process data. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Dynamics 365 Sales part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Dynamics 365 Sales with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Account, Contact, Lead, Opportunity, Quote, Order, and Activity. Dynamics 365 Sales models the Quote-to-Order chain explicitly, so an opportunity that has produced a Quote carries commercial commitment that an opportunity record alone does not express.
Dynamics 365 Sales is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Dynamics 365 Sales integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Dynamics 365 Sales integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Dynamics 365 Sales's.
Identity and matching
Dynamics 365 Sales models the Quote-to-Order chain explicitly, so an opportunity that has produced a Quote carries commercial commitment that an opportunity record alone does not express.
Start here
Read Opportunities with an active Quote and no Activity since the quote was sent, and stage the follow-up against what was actually quoted.
What this will not do
It will not price anything. Pricing lives in the product catalogue and its rules; the workflow works with quotes that already exist.
The constraint to plan around
Quote and Order records are governed by pricing and product catalogue configuration; writes that bypass the catalogue are rejected or produce lines that finance cannot reconcile.
Build notes
What you actually have to reason about in Dynamics 365 Sales.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| quoteid / revisionnumber | quotes are versioned, and reporting against the wrong revision misstates commitment |
| statecode on Quote | draft, active, won, or closed — the commercial commitment signal |
| opportunityid | the link back from Quote and Order to the pipeline record |
| priceleveid | the price list that governs valid line pricing; writes that bypass it are rejected |
| totalamount | calculated from lines rather than set, so writing it directly is not possible |
Authentication
Same Entra ID and Dataverse application-user model as the wider Dynamics platform, plus licensing that gates which Sales entities are available. A permission error here is as often a licence as a role.
Events and delivery
Dataverse change tracking and webhooks, as elsewhere on the platform. Quote and Order state transitions are the events with commercial meaning.
Workflow
How the Dynamics 365 Sales workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Dynamics 365 Sales accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Dynamics 365 Sales workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Dynamics 365 Sales and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Dynamics 365 Sales workflow.
- 01
Decide which fields Dynamics 365 Sales owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
After quote follow-up works, add margin visibility: surface quotes discounted beyond policy before they are sent rather than after they are won.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Dynamics 365 Sales integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Quote lines are rejected or produce amounts finance disputes.
Cause
The write bypassed the price list governing valid pricing.
Fix
Write through the product catalogue with a valid price level, and never set calculated totals directly.
Symptom 02
Reporting shows commitments that were superseded.
Cause
Quotes are versioned and the report read every revision.
Fix
Filter to the current revision, and be explicit about which revision a number refers to.
Symptom 03
A Sales entity returns not-found despite correct permissions.
Cause
The entity requires a licence the integration user does not have.
Fix
Check licensing as well as roles when diagnosing access here.
What changes at scale
The same Dataverse service protection limits apply, and quote-heavy orgs generate more writes per opportunity than a simple pipeline. Budget accordingly.
Examples
What a working Dynamics 365 Sales workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Enterprise sales workflows
With Dynamics 365 Sales connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Dynamics 365 Sales, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Quote and Order records are governed by pricing and product catalogue configuration; writes that bypass the catalogue are rejected or produce lines that finance cannot reconcile.
- Quote and Order records are governed by pricing rules and product catalogue configuration. Writes that bypass them either fail or produce lines finance cannot reconcile, and the second outcome is discovered much later.
- When quoting is handled in a dedicated CPQ. Two systems generating quotes is a pricing-integrity problem before it is an integration problem.
- If Dynamics 365 Sales data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Dynamics 365 Sales integration questions.
What records does a Dynamics 365 Sales integration actually work with?
The primary records are Account, Contact, Lead, Opportunity, Quote, Order, and Activity. Dynamics 365 Sales models the Quote-to-Order chain explicitly, so an opportunity that has produced a Quote carries commercial commitment that an opportunity record alone does not express.
What should the first Dynamics 365 Sales workflow be?
Read Opportunities with an active Quote and no Activity since the quote was sent, and stage the follow-up against what was actually quoted.
What will a Dynamics 365 Sales integration not do?
It will not price anything. Pricing lives in the product catalogue and its rules; the workflow works with quotes that already exist.
What is the main constraint to plan around?
Quote and Order records are governed by pricing and product catalogue configuration; writes that bypass the catalogue are rejected or produce lines that finance cannot reconcile.
What changes about a Dynamics 365 Sales integration at scale?
The same Dataverse service protection limits apply, and quote-heavy orgs generate more writes per opportunity than a simple pipeline. Budget accordingly.
How does authentication work for Dynamics 365 Sales?
Same Entra ID and Dataverse application-user model as the wider Dynamics platform, plus licensing that gates which Sales entities are available. A permission error here is as often a licence as a role.
Does Dynamics 365 Sales support webhooks, and can they be trusted?
Dataverse change tracking and webhooks, as elsewhere on the platform. Quote and Order state transitions are the events with commercial meaning.
What is the risk of writing to Dynamics 365 Sales?
Quote and Order records are governed by pricing rules and product catalogue configuration. Writes that bypass them either fail or produce lines finance cannot reconcile, and the second outcome is discovered much later.
When is connecting Dynamics 365 Sales the wrong call?
When quoting is handled in a dedicated CPQ. Two systems generating quotes is a pricing-integrity problem before it is an integration problem.
What should a Dynamics 365 Sales integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Dynamics 365 Sales to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Dynamics 365 Sales?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Dynamics 365 Sales stay the system of record?
Yes. The design assumption is that Dynamics 365 Sales remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Dynamics 365 Sales, and who decides.
Connecting Dynamics 365 Sales is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.