Microsoft Dynamics 365 integration

Last updated: November 10, 2026

Connect Microsoft Dynamics 365 Sales to CRED to bring your Dynamics records into CRED and write account, contact and opportunity changes back. This article covers what's specific to Dynamics, including a checklist to complete before your setup call. For how sync works in general, see the CRM integrations overview.

What CRED syncs

Dynamics entity	In CRED	CRED can write back
account	Account	Yes
contact	Contact	Yes
opportunity	Opportunity	Yes, including the business process flow stage
Business process flows, and the sales stage option set	Opportunity pipeline	No
Process stages	Opportunity stage	No
lead	Lead	No
campaign	Campaign	No
task	Task	No
annotation	Note	No
email	Email	No
Custom entities	Custom entity records	No
systemuser	CRM user (for owners)	No

Write-back is limited to accounts, contacts and opportunities. Everything else is read into CRED only.
Custom fields on these entities are found automatically and can be mapped in the wizard. Industry (industrycode) is read into CRED but never written back.
Active records only. By default CRED reads active accounts and contacts, and open and won opportunities. Inactive records and lost opportunities are skipped.
Campaign members aren't synced. Dynamics stores campaign membership in marketing lists, which don't map to CRED's campaign members.
Pipelines: if your org uses business process flows, each one becomes a pipeline in CRED. Orgs without them get a pipeline built from the opportunity sales stage values.

Before your setup call: checklist

Admin account

☐ Choose the admin who will authorise the connection, and make sure they can join the call.
☐ They have the System Administrator or System Customizer security role in Dynamics 365. Real-time sync needs System Customizer or higher.
☐ They can grant consent to third-party apps in Microsoft Entra ID (Azure AD), and can complete MFA if it's on.

Dynamics 365 instance

☐ You know your Dynamics subdomain: the part of your Dynamics URL before .dynamics.com, for example yourcompany.crm or yourcompany.crm4.
☐ You know which environment to connect.
☐ Web API access is enabled for the admin account.

Data scope

☐ You've decided which entities to sync (see the table above).
☐ You know your approximate record counts, for example 5,000 accounts and 25,000 contacts.
☐ You've listed any custom entities you need.

Write-back (if you need it)

☐ You've decided between read-only and two-way sync for accounts, contacts and opportunities.
☐ Any custom fields CRED should write to exist on those entities in Dynamics.
☐ Field security profiles give the connected user Read and Write on those fields.
☐ You've checked business-required fields, business rules and plugins that could reject records from CRED.
☐ You've run Publish All Customizations after any field changes.

Network and security

☐ No IP restrictions block external API access.
☐ Conditional Access policies won't block the sign-in.
☐ You've noted other tools that write to Dynamics, so you can avoid conflicting updates.

How to connect Dynamics 365

Open Integrations in the left navigation and find Microsoft Dynamics 365 under CRM & Sales.
Click Connect (or Enable) on the tile.
Enter your Dynamics subdomain. For example, if your Dynamics URL is yourcompany.crm.dynamics.com, enter yourcompany.crm.
Sign in with your Microsoft account and approve access.
Back in CRED, the integration wizard opens. Choose Automatic or Custom setup, pick the entities to sync, map fields and set write rules. See the overview for each step.

Use a dedicated integration user rather than a person's own login. Dynamics limits API requests per user, so a dedicated user also keeps CRED from competing with your team's own Dynamics use.

To change settings later, click Settings on the Dynamics tile. To disconnect, click Disconnect on the tile. Disconnecting stops syncing; records already in CRED and Dynamics stay where they are.

How Dynamics sync works

First read: CRED reads each entity you chose, in order (users, pipelines and custom entity definitions first, then accounts, contacts and leads, then opportunities, then tasks, notes and emails). Large orgs can take several hours.
Ongoing reads: about once an hour, CRED reads the records whose modifiedon date changed since the last sync.
On demand: Pull latest from Dynamics on a company or person's sidebar re-reads that record now. Pull all changes since last sync in the connection's settings panel reads every recent change.
Real-time sync: with Dynamics webhooks, changes to the listed entities reach CRED within seconds. This may not be enabled for your workspace yet; contact support to turn it on. Turning it on needs a connected user with the System Customizer role or higher. If the panel shows Scheduled (missing Dynamics permission), an admin with that role must reconnect Dynamics and turn real-time sync on again.
Deleted records: CRED checks for records deleted in Dynamics in the last 30 days and removes them from CRED.
Writing back: accounts, contacts and opportunities follow each entity's Update Rule and Create Rule and each field's write rule. When you change an opportunity's stage in CRED, CRED moves its business process flow to that stage in Dynamics.

API usage

Dynamics 365 limits API requests per user (for example 6,000 requests in a five-minute window), plus a daily allowance that depends on your licence. When Dynamics asks CRED to slow down, CRED waits the time Dynamics gives and retries.

Troubleshooting

Dynamics error	What it means	What to do
Privilege or access denied	The connected user's security role can't read or write this entity or field.	Add the privilege to the role, or check field security profiles.
Required field missing	A business-required field wasn't sent.	Map that field, or mark it Is Required? in CRED so records without it are held back.
Duplicate detected	A Dynamics duplicate detection rule blocked a new record.	Link the existing record in CRED (see Matching), or adjust the rule.
Business rule or plugin error	A business rule or plugin rejected the value.	Check the rule or plugin named in the error, then fix the value.
HTTP 429	The connected user hit Dynamics' request limit.	CRED retries automatically. If it keeps happening, use a dedicated integration user.

The tile says Relink Needed. Microsoft revoked or expired CRED's access. Click Relink and sign in again. No data is lost.

A choice (option set) value doesn't sync. Dynamics stores choice values as numbers. The value in CRED has to match one of the field's options in Dynamics.

A lead, task or note change didn't reach Dynamics. CRED only writes back accounts, contacts and opportunities.

For record-level errors and missing required fields, see Fixing CRM sync issues. When you contact support@credplatform.com, include the record name, the field, and the error from Data Sync Log or Sync Health.