Before connecting Dynamics 365 to Enginy, make sure your organization meets the following requirements. This article covers what you need on the Dynamics side — for step-by-step connection instructions, see How to Configure Your Dynamics 365 Integration.
What Enginy will do with your Dynamics 365
With the granted permissions, Enginy will be able to:
Read, create, and modify accounts in your instance.
Read, create, and modify leads or contacts (depending on how you configure Enginy).
Create tasks, phone calls, and emails to log your campaign activity.
Read system users (needed to assign record owners).
Read saved views and queries in order to import lists from them.
Supported plans and versions
Before connecting, check that your Dynamics is compatible with Enginy.
Product | Compatibility | Details |
Dynamics 365 Sales (Microsoft cloud) | ✅ Compatible | Full integration |
Dynamics 365 Customer Service (Microsoft cloud) | ✅ Compatible | Full integration |
Dynamics 365 Marketing | ⚠️ Partial | You can connect, but only standard contacts, accounts, and activities work. Marketing-specific entities are not integrated. |
Dynamics 365 Field Service | ⚠️ Partial | You can connect, but only standard contacts, accounts, and activities work. Field Service-specific entities are not integrated. |
Dynamics AX (all versions) | ❌ Not compatible | — |
Dynamics 365 on-premise (customer's own servers) | ❌ Not compatible | — |
Dynamics 365 Finance & Operations (F&O) | ❌ Not compatible | — |
Dynamics 365 Business Central | ❌ Not compatible | Uses a different technical platform |
Dynamics on government clouds (Microsoft Cloud for US Government, GCC / GCC High) | ❌ Not compatible | — |
Dynamics on the China cloud (operated by 21Vianet) | ❌ Not compatible | — |
Not sure which version you have?
If you try to connect an unsupported environment, Enginy won't tell you directly "your version is not compatible" — you'll see a generic connection error and won't be able to complete the process.
If you're unsure which product or edition your company uses, or if you've seen an error while trying to connect, talk to our support team before trying again — we'll help you confirm compatibility faster than you could figure it out on your own.
User Permissions
Once connected, Enginy checks certain required Dynamics security roles and shows the results in an informational panel, to help you diagnose permission issues.
Note: this check runs after connecting and doesn't block the initial authorization — it's a diagnostic tool, not a prerequisite gate. If you run into sync issues after connecting, check this panel first.
Authentication
Enginy connects via OAuth 2.0 over Azure AD (Microsoft Entra ID) using MSAL (Microsoft Authentication Library). The requested scopes are:
openid,profile,offline_access— Microsoft Identity standard scopes for identity and refresh tokens.https://disco.crm.dynamics.com/.default— used only for the initial discovery step (locating your Dynamics instance within the tenant).After that, an instance-specific scope:
${apiUrl}/.default(for example,https://yourcompany.crm.dynamics.com/.default).
What .default means
Enginy uses Microsoft Identity's .default pattern. This means no permission is requested per operation — instead, all permissions granted to the Enginy app in your tenant are requested at once. This is Microsoft's recommended pattern for application integrations.
Sandbox testing
Not supported.
Security
Tokens refresh automatically.
Removing the integration from Enginy clears the credentials from our systems. However, the Enginy application remains registered in your Microsoft Entra ID tenant until you remove it there manually. To fully disconnect, revoke access manually from Microsoft Entra ID in the Azure Portal (formerly Azure AD).