A Norwegian tender document lands on the desk and it asks for Dynamics 365 CE, 60 users. Every vendor reading it will price something slightly different, because the term no longer points at one thing. It used to.
The short version: Dynamics 365 CE is not a product you can buy. Microsoft deprecated the Dynamics 365 for Customer Engagement licence plan in October 2019, and licences bought before the deprecation began expiring from 2022. The name lives on, but it means something different today: customer engagement is Microsoft's umbrella term for the apps that run on Dataverse, among them Sales, Customer Service, Field Service and Customer Insights. It describes an architecture family. Dynamics 365 Sales is one of those apps, and it is the one you actually license per user, sold in four forms: Sales Professional, Sales Enterprise, Sales Premium and Microsoft Relationship Sales. The practical consequence for a requirements document is concrete: never write we need Dynamics 365 CE. Write instead which capabilities you need, how many users will create and edit data, and how many will only read.
Why the question still comes up in 2026
The term comes from a time when it did describe something you could buy. When Microsoft gathered the CRM products under Dynamics 365, there was a licence plan called Dynamics 365 for Customer Engagement, giving access to Marketing, Sales, Customer Service, Field Service and Project Service Automation together. Under that plan, customers were allowed to use Marketing if they had at least ten seats of a CRM or ERP app.
That plan was deprecated in October 2019. From 2022, licences bought before the deprecation began to expire, and the individual apps had to be purchased separately.
Even so, we still meet D365 CE in Norwegian tender documents, in vendor presentations and in job adverts. Nobody is being dishonest. The term is useful because it separates the CRM side of Dynamics 365 from the finance and operations side, and the industry has not settled on an equally short replacement. The problem only arises when the word appears in a document that is going to be priced.
In the middle of a CRM procurement? We are happy to read the requirements document before it goes out and point out the wordings that make bids hard to compare. It usually takes an hour.
What customer engagement means at Microsoft today
The term lives on in Microsoft's own documentation, but as an architectural category. Customer engagement apps are the apps that run on Microsoft Dataverse and are built using Power Apps model-driven app design. Dynamics 365 Sales is one of them, and Microsoft states it plainly in the documentation: Sales runs on Dataverse and uses model-driven app design. In practice that means the app is assembled from tables, forms and views you can inspect and change, rather than delivered as a fixed screen set.
This has practical consequences. It means the data model can be extended with your own tables, columns and relationships using the same tools you would use to build a custom app, and that the security model is shared across the apps.
This is also where the common confusion has its root. When someone says we have D365 CE, they usually mean we have the CRM part of Dynamics 365. That is precise enough in a conversation. In a tender document it is not precise enough to price.
The four ways to buy Dynamics 365 Sales
Microsoft sells Sales as four licences. Between Professional and Enterprise, the difference is how much of the data model you get access to. Between Enterprise, Premium and Relationship Sales, it is how much guidance, AI and LinkedIn data is built in.
| Offering | What it gives | When it fits |
|---|---|---|
| Sales Professional | Sales automation with a subset of the tables in Sales Enterprise | The need is straightforward sales follow-up, without heavy customisation of the data model |
| Sales Enterprise | The full sales process from lead to order, forecasting, campaigns and advanced customisation. Also includes limited monthly capacity on Premium features such as the sales accelerator, conversation intelligence and predictive scoring | A need for the whole sales process with advanced customisation. This is also the one we ourselves most often land on for Norwegian mid-sized organisations |
| Sales Premium | Everything in Enterprise, plus guided selling, relationship intelligence and predictive models for lead and opportunity scoring | Sales organisations that already have the data discipline prediction requires |
| Microsoft Relationship Sales | Sales Enterprise combined with LinkedIn Sales Navigator | Outbound selling where LinkedIn is the main channel. Not available for direct purchase; it goes through Microsoft or a partner |
Two details are worth carrying into a budget. The first concerns the LinkedIn part. Microsoft's own documentation names two different editions for the same licence: the buying page says LinkedIn Sales Navigator Enterprise, the overview page says Advanced Plus. The edition decides what your salespeople actually get to see of LinkedIn data, so ask for it to be named in the quotation rather than assuming. The second concerns AI. Sales Enterprise, Sales Premium and Relationship Sales include the basic Sales agent capabilities, while the premium capabilities require a Microsoft 365 Copilot licence on top. That is a separate cost line, and it is often missing from the first budget draft. We have written more about what Copilot actually does in our review of Copilot in Dynamics 365 Sales.
A note on reading Microsoft's pages yourself: the overview page now also lists Sales agent as an offering alongside the four licences. It is presented as a capability you reach through the licences above and a Copilot licence, not as a fifth per-user CRM licence. That is worth knowing before you compare two vendor quotations that count the offerings differently.
What decides the price is user roles, not app names
In the procurements we have been part of, the most expensive mistake is rarely choosing the wrong app. It is giving every user the same licence.
Microsoft has a dedicated lightweight licence, Dynamics 365 Team Members, for users who need access without full capabilities. It grants access through a fixed set of Team Member apps defined by Microsoft, and for the customer engagement apps, Sales Team Member is one of them. The licence has two constraints you need to know before planning around it: a Team Member app can contain at most 15 tables, which Microsoft's documentation still calls entities, and the licence does not give access to custom apps. The table limit applies per app, and Microsoft notes that further tables can still be reached through subgrids, dashboards and lookups, so the constraint sits on the app design rather than on what the user may see.
If a user only needs one app you built yourself on Dataverse, Power Apps is the right licence track, per app or per user depending on how many apps they need.
| User type | What they actually do | Licence track |
|---|---|---|
| Full user | Creates and edits sales data daily, owns opportunities | Dynamics 365 Sales (Professional, Enterprise or Premium) |
| Light user | Reads data, updates in limited scenarios, pulls reports | Dynamics 365 Team Members, within the 15-table limit |
| Custom app user | Works only in an app you built yourself on Dataverse | Power Apps, per app or per user |
Microsoft has also made this auditable after the fact. The Power Platform admin centre provides a report on usage that does not conform to Team Member use rights. It is intended as general guidance rather than a verdict, but it is a useful starting point if you suspect the licence mix has drifted. For how the licence line relates to the rest of the cost picture, see what a Dynamics 365 implementation really costs.
"When a requirements document asks for Dynamics 365 CE, you get bids you cannot compare. Not because the vendors are dishonest, but because the term no longer has a single meaning."
Cartagena, from CRM and Dynamics 365 procurements in the Norwegian mid-market
What this means for your requirements document
Three lines solve most of the confusion, and they cost nothing to include.
The first is capability instead of product name. Write what the process should do, not what the system should be called. Salespeople must be able to follow an opportunity from first contact to signed agreement, with a quarterly forecast is something that can be priced. Dynamics 365 CE is not.
The second is a distinction between user types. State how many will create and edit data, and how many will only read and pull reports. Without that distinction the vendor has to guess, and whoever guesses most expensively loses on price without having done anything wrong.
The third is the integration picture. Which systems the solution must exchange data with, which way the data flows, and who owns the integration after go-live. This is the item that most often blows an estimate, and it is also the one most easily clarified in advance. We have gone through the patterns in how to connect ERP and CRM without losing your mind.
If you are earlier in the process and have not landed on a platform yet, what to consider before choosing a CRM system in 2026 is the place to start. If Dynamics 365 is to be measured against the alternative, we have made that comparison in Dynamics 365 Sales against Salesforce.
Pattern: An organisation with around 60 CRM users writes Dynamics 365 CE, 60 users in the tender. Bid A prices 60 Sales Enterprise. Bid B prices 25 Sales Enterprise and 35 Team Members. Bid C prices 60 Sales Professional. The spread between the lowest and highest licence line becomes wide enough to decide the competition, without any bidder having done anything wrong. The clarification that removes the whole problem is two sentences long: how many will create and edit, and how many will only read.
When it really is right to run several apps on one foundation
The clarification above can look like an argument for buying as little as possible. It is not. The point is to buy precisely, and sometimes the precise answer is several apps.
Because the customer engagement apps share Dataverse, adding Customer Service alongside Sales is a different kind of decision from introducing a separate service desk. The account, the contact and the history are already there. What is added is the case model, the queues and the service levels, not another place to maintain customer data.
That also argues for a sequence that does not require replacing everything at once. If you have a working service system today, it is rarely right to replace it in the same project that introduces CRM. Put Sales into production first, let the two run side by side for a period, and take the consolidation decision once you have real operational experience. Enterprise CRM with Dynamics 365 goes further into what changes when the platform grows into that role.
Frequently asked questions about Dynamics 365 CE and Sales
What is the difference between Dynamics 365 CE and Dynamics 365 Sales?
Dynamics 365 CE is not a product. It is an umbrella term for Microsoft's customer engagement apps running on Dataverse: Sales, Customer Service, Field Service and Customer Insights. Dynamics 365 Sales is one of those apps, and it is the one you license per user. The licence plan actually named Dynamics 365 for Customer Engagement was deprecated in October 2019. Use the app name, not the family name, when you specify.
Can we still buy a Dynamics 365 CE licence?
No. Microsoft deprecated the plan in October 2019, and licences bought before that began expiring from 2022. Today the individual apps are bought separately. If you see D365 CE in a quotation or an agreement in 2026, it describes either an old subscription on its way out, or a vendor using the term loosely about the app family. Ask for the app name to be stated.
Which Sales licence should we choose?
Sales Enterprise is the choice we most often land on for Norwegian mid-sized organisations, because it covers the whole sales process from lead to order and leaves room for customisation. Sales Professional is enough when the need is straightforward follow-up without heavy customisation of the data model. Sales Premium pays off only when data quality is good enough for predictive scoring to give credible answers.
Does every user need a full Sales licence?
No, and this is the most common source of overspending. Users who mainly read data and make lighter updates can often be covered by Dynamics 365 Team Members. That licence gives access through designated Team Member apps, which can be customised but cannot hold more than 15 tables. Team Members does not give access to custom apps either. For a user who only needs an app you built yourself on Dataverse, Power Apps is the right track.
Does the 15-table limit apply per app or per user?
Per app. A Team Member app can contain at most 15 tables, and a user with a Team Members licence can be given access to several such apps. Microsoft also notes that further tables can be reached through subgrids, dashboards and lookups, so the limit constrains how the app is designed rather than how much the user is allowed to see. What the licence does not permit is access to apps you have built yourself.
What should the requirements document say instead of Dynamics 365 CE?
Replace the product name with three concrete lines. One: which capabilities you need, described as process rather than product name. Two: the number of users who will create and edit data, separated from the number who will only read and pull reports. Three: which systems the solution must exchange data with, and who owns the integration after go-live. With those three in place, the bids become comparable.
Sources
- Microsoft Learn, updated 15 July 2025: Deprecation: Dynamics 365 for Customer Engagement. Carries the October 2019 deprecation, the apps in the plan, the ten-seat rule for Marketing, and licences expiring from 2022.
- Microsoft Learn, updated 22 June 2026: Welcome to Dynamics 365 Sales. Carries the four licences, what Premium adds over Enterprise, the limited monthly capacity on Premium features in Enterprise, and that Sales runs on Dataverse as a model-driven Power App.
- Microsoft Learn, updated 24 April 2026: Buy Dynamics 365 Sales. Carries that Relationship Sales is not available for direct purchase, and that the premium Sales agent features require a Microsoft 365 Copilot licence. This page names LinkedIn Sales Navigator Enterprise, while the overview page above names LinkedIn Sales Navigator Advanced Plus.
- Microsoft Learn, updated 30 August 2024: Dynamics 365 Team Members licence overview and FAQ. Carries the 15-table limit, that Team Members does not grant access to custom apps, Power Apps as the right track, and the conformance report in the admin centre.
- Microsoft Learn, updated 1 February 2024: Extend customer engagement apps. Carries that the customer engagement apps share Dataverse and the Common Data Model, and that the data model can be extended with the same tools.
- All five sources were retrieved and read on 14 September 2026 and re-verified against the live pages on 21 September 2026. None of them had been edited in between.
Unsure which licences you actually need?
Our experience is that many buy too many full licences and too few light ones, because nobody has separated users by what they actually do in the system. We map the user roles and lay out the licence picture before you enter negotiations, and we say so plainly if the mix you have today already fits.