The Base-and-Attach Model
Dynamics 365 licensing is governed by one rule that decides most of the bill: base and attach. A user's first qualifying application is licensed at full price — the base licence — and every additional qualifying application for that same user is an attach licence at roughly $20 to $30 per user per month instead of full price. Get this right and a user running both Sales and Customer Service costs about $135 a month; get it wrong and the same user costs $210. Across a few thousand seats, that difference is the entire Dynamics negotiation, and it sits within the wider advanced Microsoft estate where the same per-user discipline applies everywhere.
The applications share a Dataverse foundation — the same platform behind Sustainability Manager — which is why Microsoft can offer the attach discount: the second app reuses infrastructure the first already paid for.
Sales vs Customer Service Editions
Both flagship modules come in Professional and Enterprise editions, and the Enterprise tiers are priced identically.
| Application | List price (per user/month) | Headline capability |
|---|---|---|
| Sales Professional | $65 | Core SFA, limited customisation |
| Sales Enterprise | $105 | Advanced customisation, custom apps, embedded intelligence |
| Customer Service Professional | $50 | Core case management |
| Customer Service Enterprise | $105 | Unified routing, insights, deep customisation |
The Professional editions are not a cut-down trial — for teams with standard processes they are genuinely sufficient, and the $40-to-$55 monthly saving per user over Enterprise is real money at scale. The Enterprise tier earns its premium only where you need custom applications, advanced automation or the embedded AI features. Tier to the process, not to the org chart.
Where the Savings Are
For a 2,000-seat deployment where every user needs both Sales and Customer Service, licensing the second app at the attach rate of about $30 rather than the full $105 saves roughly $1.8M a year. The base-and-attach rule is the largest single lever in Dynamics 365 pricing — and it is routinely missed.
The discipline is to designate one base application per user — the one they use most — and attach the rest. The trap is buying two full base licences for users who Microsoft's own rules would let you cover with one base and one attach. Map every user's true application mix before the renewal and structure the order around base-and-attach, because the channel will not restructure it for you after the fact.
The Team Members Trap
The Team Members licence, at roughly $8 per user per month, is the cheapest Dynamics seat and the most misused. It is a deliberately limited, light-use licence for read access and basic record updates — not a back-door full CRM seat. Microsoft has tightened the technical enforcement of Team Members scope, and over-reaching on it is one of the most common findings in a Dynamics audit. If a Team Members user is doing real sales or service work, they need a full or attach licence, and pretending otherwise converts a small saving into a compliance liability. The same audit-exposure logic that governs government and regulated tenants applies to Dynamics: under-licensing is found, and found expensively.
Capacity, AI and Hidden Add-Ons
The per-user licence is the start of the Dynamics bill, not the end. Every Dynamics 365 environment consumes Dataverse capacity — database, file and log storage — and while each enterprise subscription includes a base allocation, large deployments routinely exceed it and pay for additional capacity packs on top. Database storage is the expensive line, billed per gigabyte per month, and a CRM that has accumulated years of records, attachments and audit logs can carry a five-figure annual capacity bill that nobody priced at purchase.
AI is the fast-growing add-on. Copilot for Sales and the agent capabilities layered onto Dynamics are licensed and metered separately, with consumption-based pricing for automated agent actions rather than a flat per-user fee. That model can scale unpredictably: an organisation that routes high volumes of service interactions through AI agents should model the consumption carefully, because it behaves more like cloud metering than a traditional seat licence. The same AI commercial dynamics we analyse for Azure OpenAI apply here.
There are also device licences for Customer Service — a shared-device option for contact centres where multiple agents use the same workstation across shifts — and a range of capacity add-ons for AI Builder, portals and Power Platform integration. None of these is large in isolation, but together they can add 15 to 25% to a Dynamics bill that was costed on seat licences alone.
The practical defence is a full bill-of-materials before signing: every user's edition and base-or-attach status, the Dataverse capacity forecast against included allocation, the AI consumption assumptions, and any device or capacity packs. Quote each as a line item. A Dynamics estate priced on per-user licences alone is almost always underestimated, and the gap surfaces as a mid-term true-up rather than a renegotiation you control.
Negotiating Dynamics
Dynamics 365 belongs in the Enterprise Agreement conversation, not a standalone CRM quote. The levers are the base-and-attach structure, the Professional-versus-Enterprise mix, capacity add-ons priced separately, and the AI features increasingly bundled or sold alongside — the same commercial dynamics covered in our Azure OpenAI enterprise terms analysis. Benchmark the per-seat rate against the Microsoft vendor intelligence hub and the Microsoft Enterprise Agreement Guide, and confirm your Team Members assignments are defensible before signing. To right-size a Dynamics estate against current benchmarks, request a confidential briefing.