Note: Connect Dynamics with a user who has access to the environment and records you will use. The integration inherits that user's security limits.
Connect Microsoft Dynamics
In Enginy, open
Integrations.Find Microsoft Dynamics and enable the integration.
Click
Connect Dynamics.If needed, complete
API URL (default if not provided)andTenant ID (default if not provided).Continue with Microsoft, choose the correct account, and accept the permissions.
When you return to Enginy, open
Dynamics Setupand review the initial configuration.
Connecting the CRM does not automatically import or export records.
When to enter the API URL
The API URL identifies the Dataverse environment. It usually has this format: https://yourorg.crm4.dynamics.com
Use the environment's base URL. Do not add /api/data/v9.2 or any later path.
We recommend entering it when:
You have access to several environments.
You need to connect production and not a sandbox.
Automatic detection chooses a different environment.
Your admin has provided a specific URL.
If you leave the field empty, Enginy queries the discovery service and uses the first available environment returned by Microsoft. There is currently no selector to choose between several results.
Important: If you have more than one environment, entering the API URL helps avoid connecting the wrong environment by accident.
When to enter the Tenant ID
In most commercial tenants, you can leave Tenant ID (default if not provided) empty. Enter it if your organization needs to direct sign-in to a specific tenant or if your admin asks you to.
Use the Microsoft Entra Directory (tenant) ID, not the domain name or the Dynamics environment ID.
What to review after connecting
Open Dynamics Setup and check:
Sync configuration: Contacts or Leads, matching, and associations.Field mapping: Contact or Lead fields and Account fields.Campaign mapping: activity that will be logged from campaigns.User mapping: owners and identities.Permissions: granted and missing privileges.
Then run an import and export with a few records.
How credentials are protected
Enginy stores the authentication data needed to renew access in encrypted form. It does not store your Microsoft password.
Microsoft can invalidate authorization because of security changes, consent revocation, tenant policies, or account changes. In that case, Enginy marks the connection as expired and you need to reconnect it.
Reconnect Dynamics
Reconnect when:
Enginy says authentication has expired.
The connected user has changed their password or access policies.
An admin has revoked and approved consent again.
You want to use another account in the same environment.
From Integrations, open Microsoft Dynamics and use Reconnect. Complete the Microsoft sign-in again.
If you reconnect the same integration, Enginy normally keeps the Dynamics configuration, including mappings and preferences. Still review it if the environment, entity, or user has changed.
If you switch from another CRM to Microsoft Dynamics, Enginy resets the previous CRM-specific configuration to avoid incompatible mappings.
Disconnect Dynamics
When you disable the integration, Enginy removes the credentials it used to access Dynamics. This does not delete:
Contacts, Leads, or Accounts in Dynamics.
Contacts, Companies, or lists in Enginy.
Activities already created.
The application consent registered in Microsoft Entra.
If you also want to remove consent in Microsoft, an admin or the user must do it from Microsoft's application settings.
The mapping configuration may remain saved in Enginy for a future reconnection, but no operation can access the CRM while it is disconnected.
Common connection issues
What you see | What to review |
Microsoft blocks consent | Admin consent policy and app approval in Microsoft Entra. |
The wrong environment is connected | Enter the exact API URL instead of using discovery. |
The URL is not valid | Use the environment's HTTPS base URL, without |
The connection works, but no records appear | User role, business unit, and Read depth. |
A read works, but an export fails | Write, Create, Append, Append To, Assign, and the user selected in |
The connection appears expired | Use |
What to send to support
If the issue continues, include:
The API URL, without credentials or tokens.
The approximate time of the attempt and your time zone.
The environment name.
The user who connected it.
A screenshot of the full message.
Whether the failure occurs when connecting, importing, exporting, or logging activity.
The affected entity type: Contact, Lead, Account, Email, Task, or Phone Call.
Important: Do not share access tokens, refresh tokens, or passwords.