Ask three partners to price a dynamics crm implementation and you will get three numbers that are not comparable, because almost none of the cost is in the thing everyone quotes. The licence price is published by Microsoft, it is the same for everybody, and it is the smallest decision in the project.
What moves the number is a short list: how many applications each user needs, how much of your old system comes with you, and how many other systems have to talk to the new one. This article is about those, and about the capacity question that appears on nobody’s quote and turns up on everybody’s bill.
What the licences actually cost
Microsoft publishes these, per user per month, paid yearly:
| Application | Professional | Enterprise | Premium |
| Sales | $65 | $105 | $150 |
| Customer Service | $50 | $105 | $195 |
Dynamics 365 Contact Center is separate again, at $110 per user per month, with discounting available when it is bought alongside Customer Service Enterprise.
There is no published seat minimum for Sales or Customer Service. That matters when you are comparing against Finance or Supply Chain Management, which carry 20-seat minimums, and it means a genuine ten-user CRM rollout is a real thing you are allowed to buy.
The base and attach rule, which is where quotes go wrong
If a user needs two applications, Microsoft’s rule is specific: the first licence must be the highest priced one. That first licence is the base; anything added after it is an attach licence. The licensing guide is blunt about what the difference is: base and attach licences “are identical in their core capabilities and are only differentiated in price”.
Two consequences a buyer should know before reading any quote.
Attach licences carry no platform capacity. The guide states it plainly: “Attach licenses do not include additional platform entitlements.” They inherit whatever came with the base licence. So a user on Sales Enterprise plus a Customer Service attach brings the storage of one licence, not two.
The attach prices are published, but not where you would look. Neither product pricing page carries an attach column. The figures are in Microsoft’s Dynamics 365 Licensing Guide, which anyone can download without a login from aka.ms/Dynamics365LicensingGuide: in the October 2026 edition the attach matrix is on page 6, and it gives $20 a month for attaching Sales Enterprise, Sales Professional, Customer Service Enterprise, Customer Service Professional, Field Service or Business Central Essentials, and $30 for the Finance and Operations applications. One practical warning: that table is an image, so searching the PDF for the numbers will not find them.
The capacity nobody quotes
This is the Dynamics equivalent of the storage question, and it catches people in the same way.
Dataverse capacity is per tenant, and explicitly not cumulative. Buying more licences does not multiply your starting allowance. Microsoft’s wording: the first base licence “includes its default capacity, which is shared per tenant. Default capacity is not cumulative”.
What you start with, and what each licence adds after that:
- Sales Enterprise and Customer Service Enterprise: 30 GB database, 40 GB file, 2 GB log per tenant, then 250 MB database and 2 GB file accrued per user licence.
- Sales Premium: 45 GB database, 60 GB file, and a more generous 500 MB database accrual per licence.
- Sales Professional and Customer Service Professional: the same 30 GB and 40 GB starting point, and nothing accrued per licence at all.
That last line is the one worth pausing on. A hundred Professional users and ten Professional users have exactly the same database allowance. If your plan is a large Professional rollout with years of history migrated in, the capacity runs out and no amount of extra seats fixes it.
The arithmetic for an Enterprise estate is worth writing down, because it is the only way to tell before you migrate whether you will go over: 30 GB, plus 250 MB per Enterprise user. A 40-seat estate is entitled to 40 GB of database; a 120-seat estate to 60 GB.
Two warnings about numbers you will find elsewhere. Microsoft raised these baselines in December 2025, and a great deal of advice still in circulation quotes the old 10 GB figure, which was correct until then and is now a third of the real entitlement. And database is only one of three meters. Dataverse bills database, file and log separately, each with its own entitlement and its own add-on. Migrated email, notes and attachments mostly land in file, where the entitlement is far larger, at 40 GB plus 2 GB per Enterprise user. The meter that actually bites is database on long-history estates with few seats, which is the opposite of where most people look.
That is not theoretical. In our engagements, migrating off legacy on-premises CRM, the estates that went over on day one were the small ones: 20 to 45 seats, carrying five or more years of relational transaction history, audit trails and activity logs with email bodies and notes held in database tables rather than decoupled to file storage. At that size the entitlement is 35 GB to around 41 GB. Those migrations landed at 45 to 75 GB of database consumed, which is roughly 10 to 34 GB over on the first day. At the published $40 per GB per month, that is an unbudgeted $400 to $1,350 a month, found after cutover rather than before it.
When it does run out, the price is published: $40 per GB per month for database capacity, $2 for file, $10 for log, billed annually. Pay as you go on a linked environment is higher again, at $48, $2.40 and $12. Database capacity is the expensive one by an order of magnitude, which is the reverse of what most people assume, and it is why “migrate everything” is a costly instruction in a CRM.
Where Microsoft helps more than you might expect
One genuine difference from the rest of the Dynamics family: Sales and Customer Service appear on Microsoft’s FastTrack eligible applications list, and Business Central does not.
Be precise about what that buys, because it is routinely oversold. FastTrack does not configure the system, write code, migrate data or project manage. Microsoft is blunt that it has “no formal role on the project”. What it does is solution blueprint reviews and go-live readiness reviews, run by Microsoft solution architects, and it can pull in implementation support from Microsoft engineering teams. That escalation route into the product group is the part worth having, and it is the part nobody mentions until a project is in trouble.
Eligibility also turns on a minimum annual Dynamics 365 spend that Microsoft does not publish. The last figure it stated publicly was a $100,000 annual investment, announced in 2020 and since removed from the documentation, so treat any number you are quoted as your account team’s, not Microsoft’s.
If you are buying a CRM implementation, ask whether the project is being registered for FastTrack and who is running it. A partner who does not mention it is either not eligible or not using it, and both are worth a question. We make the opposite point about choosing a Business Central partner, where no such Microsoft review exists and every assurance has to come from the partner or from you.
What actually moves the price
Four things, in roughly the order they bite.
How many applications per user. The base and attach structure means the shape of your user population, not its size, sets the licence cost. Ten people needing both Sales and Customer Service costs differently from ten people needing one each.
How much history comes with you. The same question as any ERP migration, with a sharper edge, because Dataverse database capacity is $40 per GB per month and CRM history is mostly activity records: emails, calls, notes, attachments. Attachments can often go to file capacity at $2 instead, which is a design decision worth making deliberately rather than by default.
How many systems have to talk to it. A CRM that does not exchange data with finance is unusual. The patterns, and the failure modes, are covered in Dynamics 365 integration patterns, and integration count is the single most reliable predictor of effort we see. Across multi-system CRM builds, interface design, data transformation, conflict resolution and retry telemetry routinely absorb 40% to 50% of the core technical build effort. That is an engineering observation from project post-mortems rather than a timesheet metric, and it is the number we size against when a quote arrives with three systems named in it and no interface detail.
How much of your process survives contact with the product. Every configuration decision is cheap. Every decision to make the product behave like your old system is not.
Our position: buy the applications people use, not the tier that covers everything
In our view the commonest costly mistake in a dynamics crm implementation is licensing for the organisation chart rather than for the work, and it is usually made at the Enterprise tier.
In 22 of the 28 Dynamics CRM estates we have implemented, rescued or audited over the past two years, Sales Enterprise had been bought across the entire sales organisation rather than scoped to the users who needed it. Where we asked why, the answer was usually that sales management wanted the forecasting and the simplest route to it was to buy Enterprise for everybody. The 28 break down as 11 implementations we ran, 9 rescues we inherited and 8 licensing and architecture audits. They are estates that came to us, which skews towards the ones already in difficulty, so read it as a count rather than a market statistic.
We should say plainly that we resell Dynamics 365 licences, so right-sizing an estate reduces our own revenue. We publish it because the alternative is a client discovering it at renewal.
Customer Service Enterprise and Sales Enterprise are the same $105. The temptation is to put everybody on one of them for simplicity, because then nobody is ever blocked. That is a defensible choice when the capability is genuinely needed. It is an expensive one when half the population needed Professional, and it is close to irreversible for a year, because you cannot reduce committed seats mid-term.
The corollary matters more, because the obvious response to over-licensing is to buy Professional and it has hard ceilings that are not obvious until you hit them. Sales Professional allows 15 custom tables per application, 5 customised business process flows, 5 custom reports, charts or dashboards, and 2 customised forms and views. It carries no right to custom apps, and no create or update rights on territories, product hierarchies and relationships, competitors, sales goals or forecasting, which Microsoft bundles on its pricing page as advanced sales force automation. Outgrowing any of those mid-build costs more than the licence ever saved.
Two constraints decide whether right-sizing is even available to you, and both are easy to miss.
Microsoft states that Enterprise and Professional users may not be deployed in the same environment. Moving part of a sales organisation to Professional is therefore not a licence swap. It is a second environment on the same tenant, with its own configuration, and those users cannot see the records in the first one. In practice, splitting tiers means two environments with data synchronised between them, through Dataverse virtual tables or Power Automate, and that architecture typically costs more to maintain than the $40 per user per month the downgrade saves. For most estates it makes right-sizing something you do at a renewal or a replatform, not a change you make mid-flight.
And Team Members is not the answer for anyone who touches a deal. Its rights run to contacts, activities and notes. Opportunities are not in them, so a rep who moves opportunities through stages needs Sales Professional at minimum. Team Members is for the people around the sales team, not in it. Where a business is also choosing between product families rather than tiers, we set out the thresholds in Business Central vs Finance and Operations.
Questions to ask before you sign
- Which users are on which tier, and why? Ask for the count per tier, not a total.
- Where does the attach price come from? Microsoft does not publish one.
- How many GB of Dataverse database does this migration land us on, against our entitlement, and what happens at the next renewal if we are over?
- Is this project registered for FastTrack, and who runs the design review?
- How many integrations are in the price, and what is the cost of the sixth one?
- What is explicitly out of scope?
Veratas implements Dynamics 365 CRM on a fixed-fee basis where the scope supports it, with the licence mix and the capacity position worked out before anyone signs. If you have a quote in front of you and want a second read, talk to our team.
Frequently asked questions
How much does Dynamics 365 Sales cost? Published list is $65 per user per month for Sales Professional, $105 for Sales Enterprise and $150 for Sales Premium, paid yearly. Customer Service is $50, $105 and $195 for the equivalent tiers.
What is an attach licence? When a user needs more than one Dynamics 365 application, the first must be the highest priced one. Additional applications are attach licences, identical in capability and cheaper, but they add no platform capacity of their own.
How much Dataverse storage comes with Dynamics 365 CRM? Sales Enterprise and Customer Service Enterprise include 30 GB database, 40 GB file and 2 GB log per tenant, with 250 MB database and 2 GB file accrued per user licence. The Professional tiers include the same starting capacity and accrue nothing per licence.
What does extra Dataverse capacity cost? $40 per GB per month for database, $2 for file and $10 for log, billed annually. Pay as you go is higher. Database is the expensive one, which is why migrating years of activity history is a cost decision rather than a technical one.
Is there a minimum number of users for Dynamics 365 CRM? No published minimum for Sales or Customer Service. The only CRM-side minimum in Microsoft’s licensing guide is Microsoft Relationship Sales at 10 seats.
Does Microsoft review a Dynamics 365 CRM implementation? Sales and Customer Service are FastTrack eligible, so an eligible project can get Microsoft engineering engagement in the solution design at no extra cost. That is a real difference from Business Central, which is not covered.
Senior Business Intelligence Architect with 22 years of experience designing enterprise analytics and data platforms. Focus areas include Power BI, real-time analytics, and large-scale BI architecture across the Microsoft data stack.