What Is Dynamics 365 Customer Engagement? CRM Naming Explained [2026]

Microsoft Dynamics 365 Customer Engagement (CE) is the name for the CRM side of Dynamics 365 — the sales, service and field-operations apps that share Microsoft's Dataverse data platform. It is a grouping of apps, not one product with one price. Microsoft's documentation states that the “Dynamics 365 for Customer Engagement” license plan stopped being available to online customers in October 2019, which is why the name still appears in documentation and partner conversations but not as something you buy.

This guide is an independent explainer for buyers who have seen “Customer Engagement” in Microsoft's documentation or a quote and want to know how it relates to “CRM”. It covers what the name means, which apps sit under it, what they share, and how they are licensed. Every factual claim links to a Microsoft source; there are no vendor statistics or ranking claims.

What “Customer Engagement” Means in Dynamics 365

Microsoft has used the phrase in three different ways, and most of the confusion comes from mixing them up.

Term	What it refers to	Source
Customer engagement apps	A collective term in Microsoft Learn for the Dynamics 365 CRM-side apps. Microsoft's implementation guide, for example, has separate product-specific guidance for “customer engagement apps” and for finance and operations apps.	Microsoft Learn: Secure your Dynamics 365 data and apps; Manage data for customer engagement apps
Dynamics 365 for Customer Engagement	The earlier online license plan. Microsoft states it is no longer available to online customers as of October 2019, and that it no longer uses the term “Dynamics 365 for Customer Engagement apps” for the collection of online apps.	Microsoft Learn: Customer Engagement (on-premises) help, version 9.0 note
Dynamics 365 Customer Engagement (on-premises)	The official name of the on-premises product that provides sales, service and marketing features.	Microsoft Learn: Customer Engagement (on-premises) help

For online customers, Microsoft says these apps “run on Microsoft Dataverse and use Power Apps model-driven app design” (Microsoft Learn). That shared foundation is the practical meaning of the name today.

CE vs. CRM: Same Idea, Different Names

“CRM” is the general software category: customer relationship management. People searching for a Microsoft CRM, partners quoting a project and Microsoft's own migration pages all use it. Microsoft describes Dynamics 365 Customer Engagement (on-premises) as “a customer relationship management business solution” for marketing, sales and customer service (Microsoft Learn), and its migration guidance refers to moving a “Dynamics CRM (on-premises)” database to Dynamics 365 and Microsoft Dataverse (Microsoft Learn: Migrate to Dynamics 365 online).

So the two names point at the same kind of software. In practice:

• “Dynamics 365 CRM” is the shorthand buyers and partners use, including on this site, for the customer-facing Dynamics 365 apps.
• “Customer Engagement” is the grouping name in Microsoft's documentation and licensing history.
• Neither is a single product you add to a cart. You choose apps, and each app has its own editions.

Our hub page, Dynamics 365 CRM: The Complete Guide, covers the product category as a whole. This page only settles the naming.

The CE Application Family

Microsoft's 2019 note lists the apps that made up the collection at that time: Sales, Customer Service, Marketing, Field Service and Project Service Automation (Microsoft Learn). Microsoft's Partner Center today groups “Sales, Sales Insights, Customer Service, and Field Service” under its Customer Engagement workload (Microsoft Partner Center: Solutions Partner for Business Applications). The product lineup changes between release waves, so treat any list as a snapshot. As of 2026-10-29, the CRM-side apps this site covers are:

• Dynamics 365 Sales helps teams “keep track of your accounts and contacts, nurture your sales from lead to order” and create sales collateral (Microsoft Learn: Welcome to Dynamics 365 Sales). See our Dynamics 365 Sales guide.
• Dynamics 365 Customer Service tracks customer issues through cases, shares a knowledge base, routes work with unified routing and manages conversations across channels, including voice (Microsoft Learn: Welcome to Dynamics 365 Customer Service). See our Customer Service guide.
• Dynamics 365 Field Service helps “deliver onsite service to customer locations” with work orders, scheduling and a mobile app (Microsoft Learn: Overview of Dynamics 365 Field Service). See the Field Service hub.
• Dynamics 365 Customer Insights has two parts: Customer Insights – Data, which Microsoft calls its customer data platform, and Customer Insights – Journeys, for trigger-based customer journeys (Microsoft Learn: Customer Insights documentation). See Customer Insights & Marketing.
• Dynamics 365 Contact Center is described as bringing intelligence and automation to engagement channels “in the customer relationship management (CRM) solution of your choice” (Microsoft Learn: Dynamics 365 Contact Center overview).

Customer Insights and Contact Center are not named in Microsoft's 2019 note. We include them because they sit beside the other apps in the same customer-facing stack and work with the same customer records, but a Microsoft quote may group them differently. For what each one does in more depth, see Dynamics 365 CRM modules.

The Shared Platform: Dataverse and Model-Driven Apps

Two Microsoft Power Platform concepts explain why these apps feel like one family.

Microsoft Dataverse “lets you securely store and manage data that's used by business applications”, in a set of tables. Microsoft states that Dynamics 365 applications such as Sales and Customer Service “also use Dataverse to store and secure the data they use” (Microsoft Learn: What is Microsoft Dataverse?). Because apps in an environment work against the same tables, a customer record created in one can be used by the others.

Model-driven apps are built by adding components such as forms, views, charts and dashboards to tables. Microsoft notes that you can't create one “without a data model housed within Microsoft Dataverse”, and that the user interface is largely set by the components you add, so people who learn one model-driven app find the next easier to adopt (Microsoft Learn: Overview of building a model-driven app).

Security follows the same pattern. Dataverse uses role-based security to control which apps and data a user can see, and when you deploy Dynamics 365 apps, “each app installs its own set of roles” (Microsoft Learn: Security roles for Dataverse). The practical result is one data model and one security model to design, not one per app. That is also what makes the extension tools in the wider Power Platform, such as Power Apps and Power Automate, usable on CRM data without a separate integration.

How CE Relates to ERP

Dynamics 365 also includes ERP apps. Microsoft's implementation guide uses “finance and operations apps” to cover Dynamics 365 Finance, Supply Chain Management, Commerce, Human Resources and Project Operations (Microsoft Learn: Success by Design). Dynamics 365 Business Central is a separate application, and Microsoft's guide suggests that startups and small businesses might explore it instead (Microsoft Learn: What is the Dynamics 365 implementation guide?).

The dividing line is the job the app does: CE apps handle customer-facing work, ERP apps handle finance and operations. They are licensed separately and sold as separate apps. On data, Microsoft's Dataverse documentation notes that finance and operations apps need the Data Integrator configured to make their data available in Dataverse (Microsoft Learn, page dated 2026-03-31), so connecting CRM and ERP is a project decision, not something that happens automatically. Our Dataverse integration guide covers the options.

How CE Is Licensed

Because the online Customer Engagement plan was withdrawn, you license the apps you need. Microsoft sells Sales per user per month in Professional, Enterprise and Premium editions, and the exact list prices are on our Dynamics 365 CRM pricing page rather than repeated here. Customer Insights works differently: Microsoft documents that it is “licensed per tenant”, with more capacity available through add-on licenses (Microsoft Learn: Product overview for Customer Insights - Data). Edition entitlements for every app are defined in the Dynamics 365 Licensing Guide.

Naming and licensing details as of 2026-10-29. Refresh trigger: the next Dynamics 365 release wave or any change to Microsoft's Customer Engagement documentation or the Dynamics 365 Licensing Guide.

Sources

• Help for Dynamics 365 Customer Engagement (on-premises) (Microsoft Learn)
• Manage data for customer engagement apps (Microsoft Learn)
• Secure your Dynamics 365 data and apps (Microsoft Learn)
• Migrate to Dynamics 365 online (Microsoft Learn)
• Welcome to Dynamics 365 Sales (Microsoft Learn)
• Welcome to Dynamics 365 Customer Service (Microsoft Learn)
• Overview of Dynamics 365 Field Service (Microsoft Learn)
• Dynamics 365 Customer Insights documentation (Microsoft Learn)
• Product overview for Dynamics 365 Customer Insights - Data (Microsoft Learn)
• Dynamics 365 Contact Center overview (Microsoft Learn)
• What is Microsoft Dataverse? (Microsoft Learn)
• Overview of building a model-driven app with Power Apps (Microsoft Learn)
• Security roles for Dataverse (Microsoft Learn)
• Introduction to the Success by Design framework (Microsoft Learn)
• What is the Dynamics 365 implementation guide? (Microsoft Learn)
• Solutions Partner for Business applications (Microsoft Partner Center)
• Dynamics 365 Licensing Guide (Microsoft)

Last reviewed: October 2026. Product names, apps and licensing terms are subject to change. Verify current terms on the official Microsoft pages or with your Microsoft partner before making purchasing decisions.