Customer Engagement is the customer-facing half of Dynamics 365 - Sales, Customer Service, Field Service and Customer Insights, sharing one customer record. Here is what each application does and how to choose where to begin.
Microsoft Dynamics 365 Customer Engagement is the group of applications that manage everything facing your customers: attracting them, selling to them, supporting them and servicing them on site. It is what most people mean when they say Dynamics 365 CRM, and Microsoft uses both names for the same set of products.
The important thing is that it is a suite, not a single product. Sales, Customer Service, Field Service and Customer Insights are licensed and deployed separately, but they all write to the same underlying data platform. A contact created by a marketing campaign is the same record a salesperson works, the same record a service agent opens a case against, and the same record an engineer sees on a job.
That shared foundation is the practical difference between Dynamics 365 and stitching together separate best-of-breed tools. There is no integration to build and no synchronisation to maintain, because there is only ever one version of the customer. It also means you can start with one application and add the next when the business is ready, rather than buying a platform you grow into slowly.
Each application is licensed separately and can be deployed on its own. They share the same customer records, so the suite grows with you rather than needing to be bought all at once.
Pipeline, forecasting and account management for sales teams. The most common starting point for organisations moving off spreadsheets or a lightweight CRM.
Case management, knowledge and omnichannel support so inbound queries are tracked, routed and resolved against agreed service levels.
Work orders, scheduling and mobile engineer access for anyone delivering service on site rather than over the phone.
Marketing automation and a customer data platform in one. Builds unified customer profiles, then runs journeys and campaigns against them.
You do not need the whole suite on day one. Pick the application that answers your loudest operational problem, prove it, then attach the next one.
| If this sounds familiar | Start with | Why |
|---|---|---|
| We cannot see the pipeline or forecast reliably | Sales | Opportunity stages, weighted forecasting and activity tracking give you a pipeline you can trust before you automate anything else. |
| Customer queries are lost in shared inboxes | Customer Service | Cases, queues and SLAs turn scattered email threads into tracked work with an owner and a deadline. |
| Engineers, vans and site visits are scheduled by hand | Field Service | Work orders, scheduling and a mobile app replace whiteboards and phone calls, and feed job history back to the customer record. |
| Marketing and sales are working from different lists | Customer Insights | A unified profile and shared segments mean campaigns and sales activity run off the same data rather than two exports. |
Adding a second application later costs far less than the first, because Microsoft charges additional apps for the same user at a reduced attach rate. The numbers are set out in our Dynamics 365 CRM pricing breakdown.
The value of Customer Engagement sits less in any single application and more in what they share underneath.
Marketing, sales, service and field teams all read and write the same accounts and contacts in Dataverse. No exports, no duplicate records, no arguments about which system is right.
Outlook, Teams, Excel and SharePoint connect out of the box, so activity capture, meetings and documents happen where your teams already work rather than in a separate CRM window.
AI assistance is embedded in each application, drafting emails, summarising cases and opportunities and surfacing next steps from data you already hold rather than a separate AI tool.
Power BI reads the same data platform, so you can report on marketing spend, pipeline, case resolution and field productivity in a single dashboard instead of four.
Roles, permissions and audit trails are defined once at the platform level and apply across every application, which matters for regulated sectors and for anyone managing GDPR obligations.
Power Apps, Power Automate and Power Pages build on the same foundation, so custom screens, approvals and customer portals are configuration work rather than a separate development project.
A phased rollout consistently beats a big-bang deployment across all four applications.
Deploy the first application, migrate clean account and contact data, and get one team using it daily. Everything afterwards depends on this data being trusted.
Add the application that shares the most data with the first, typically Customer Service after Sales. Attach pricing keeps the cost of the second app low.
Once the data is reliable across teams, layer on Power Automate flows, Copilot and cross-application Power BI reporting. Automating early, on poor data, is what derails projects.
Customer Engagement is Microsoft's name for the customer-facing applications within Dynamics 365: Sales, Customer Service, Field Service and Customer Insights. They share one data platform, so a single customer record carries through marketing, selling, support and on-site service.
In practice, yes. Microsoft retired the standalone Dynamics CRM product and split its functionality into separate applications grouped under Customer Engagement. Most buyers still call it Dynamics 365 CRM, and both names describe the same suite.
No. Each application is licensed separately and works on its own. Most organisations start with one, usually Sales or Customer Service, and add others as the need appears. Because everything sits on the same data platform, adding an application later is a licence and configuration change rather than a fresh implementation.
All four write to the same Dataverse tables. Accounts, contacts and activity history are shared rather than synchronised between systems, so an open opportunity, a support case and a scheduled site visit all appear against the same customer record with no integration work.
Customer Engagement handles the customer side: marketing, sales, service and field operations. Business Central handles the back office: finance, purchasing, inventory and operations. They connect, so a quote raised in Sales can become an order in Business Central and finance data can inform account management.
Customer Engagement is built on the same foundation as Power Apps, Power Automate and Power BI. That means you can extend the applications with custom apps, automate processes across them, and report on everything without a separate integration layer or third-party toolset.
Copilot is embedded across the applications. In Sales it drafts emails, summarises opportunities and prepares meeting notes. In Customer Service it suggests case responses and surfaces knowledge articles. It works from your own data in Dataverse, so the quality of the output tracks the quality of your CRM records.
For the full platform overview, capabilities and case studies, see our main Dynamics 365 CRM hub. If you are costing a deployment, the Dynamics 365 CRM pricing breakdown sets out per-user licensing and attach rates across the suite.
Tell us how your sales, service and marketing teams work today and what is getting in the way. We'll match you with a Microsoft partner who can recommend the right applications and sequence, with no obligation.
