Microsoft Dynamics 365 - CRM on Make Enterprise
Microsoft Dynamics 365 - CRM is a CRM or customer system. Leads, accounts, deals and cases. Most enterprise automation starts or ends here. Here is what Make lists for it, what we build around it, and what to settle before you automate it.
What does Make list for Microsoft Dynamics 365 - CRM?
Make's page lists 1 trigger, 5 actions, 1 search by name.
Triggers
- Watch Records
Actions
- Create a Record
- Delete a Record
- Get a Record
- Make an API Call
- Update a Record
Searches
- Search Records
Module lists change as Make updates the app. Treat this as a snapshot and confirm on Make's page before you scope work.
What do we build around Microsoft Dynamics 365 - CRM?
These are the kinds of scenarios we build for crm and customer systems. They describe our work, not features of Microsoft Dynamics 365 - CRM.
- Lead routing, enrichment and follow-up
- Two-way sync between the CRM, billing and support
- Ownership and duplicate rules for every connection
- Alerts when a deal or case sits untouched
Example flows
- A form submission creates the lead, enriches it and assigns an owner by territory
- A closed-won deal creates the billing customer and the onboarding project
- A case that breaches its target notifies the account owner
What should you settle before automating Microsoft Dynamics 365 - CRM?
Settle these before the first production scenario so builders can start without waiting on a later security review.
- Which system owns each field when two disagree
- Who may add or change a CRM connection
- How duplicates are handled before records sync
- Which objects a scenario may delete, if any
Platform-level controls such as SSO, roles, encryption and log retention are Make's own published terms; see make.com/security and our Make Enterprise page for how we scope against them. Make describes the Enterprise plan itself at make.com/enterprise.
Frequently asked questions
Can Make connect to Microsoft Dynamics 365 - CRM?
Yes. Make has a Microsoft Dynamics 365 - CRM app, and its page states that it is supported and maintained by Make. It is listed in Make's Enterprise integrations category. The modules and names on this page are what Make shows on its own Microsoft Dynamics 365 - CRM page as of November 5, 2026, so check Make's page for the current list.
What do you build around Microsoft Dynamics 365 - CRM?
We build the scenarios around it: lead routing, enrichment and follow-up; two-way sync between the CRM, billing and support; ownership and duplicate rules for every connection. Scope is set on a call, and each scenario is documented in plain language before hand-over.
What should we decide before automating Microsoft Dynamics 365 - CRM?
Start with the guardrails: which system owns each field when two disagree; who may add or change a CRM connection; how duplicates are handled before records sync. Settling these first lets builders start without waiting on a security review later.
Does the connection need Microsoft Dynamics 365 - CRM admin access?
That depends on what the scenarios do and on Microsoft Dynamics 365 - CRM's own permission model. We aim for a dedicated service account with the narrowest role that works, and we record which scenarios write and which only read. Your Microsoft Dynamics 365 - CRM administrator decides what that account may reach.
Consultants in a Box is a Make partner. This page is written by us and is not published by Make or by Microsoft Dynamics 365 - CRM's vendor. Microsoft Dynamics 365 - CRM, Make and related names are trademarks of their owners. Statements about Make's platform are the ones Make publishes.
Planning to automate Microsoft Dynamics 365 - CRM?
Book a call. We map your systems to the pages here, agree the guardrails and give you a written scope and price afterwards.