Microsoft Dynamics 365: Per-User Licensing Costs

Microsoft Dynamics 365’s CRM-side apps — Sales, Customer Service, and the rest — license per user per month across a tiered structure, similar in shape to Salesforce or HubSpot. What’s different is the “base-and-attach” pricing model: your first Dynamics app for a given user is licensed at full tier price, and each additional Dynamics app attached to that same user is discounted to a flat attach rate. That structure quietly rewards buying more modules for users you’ve already licensed, which is a different upsell lever than the seat-tier jumps or feature gates covered elsewhere on this site.

How the per-user model actually works

• Tiered per-user pricing by capability level. Reported Dynamics 365 Sales tiers run from around $8/user/month for a light Team Member license up to roughly $65 for Sales Professional, $105 for Sales Enterprise, and $150 for Sales Premium (which adds Copilot and conversation intelligence), billed annually.
• Base-and-attach discounting. The first Dynamics app a user is licensed for is priced at its full tier rate; each additional qualifying Dynamics app attached to that same user is reportedly discounted to around $30/user/month — a mechanic designed to encourage expanding module footprint on users already on the platform rather than adding new seats.
• Team Member licenses gate most write access. The $8/month tier covers light, read-mostly usage; anyone who needs to create or edit records meaningfully needs a full Professional-tier-or-above license, which is where the real per-user cost lives.
• Premium features sit behind the top tier. AI-assisted selling and conversation intelligence are bundled only into the Premium tier, so unlocking them means moving every relevant user up the full tier ladder, not adding a smaller add-on.

Where the licensed platform still earns its keep

Deep integration with the Microsoft 365 and Power Platform ecosystem — Outlook, Teams, Power BI, Power Automate — is Dynamics 365’s real differentiator, and that integration work reflects genuine platform engineering that a custom build shouldn’t try to replicate. The core sales-pipeline and case-management data model built on that ecosystem is usually not where the savings opportunity lives.

Where the per-user math changes

	Dynamics 365 CRM apps	Custom-built portal on flat fee
Pricing	Per user, tiered, with base-and-attach module discounting	Flat monthly fee, independent of user count
Light/occasional users	Still require a Team Member seat to view records	No per-seat cost for occasional access
Best fit	Full pipeline and case-management workflows tied to Microsoft 365	Self-service portals, light reporting, and workflows outside the core CRM
Adding a module	Discounted attach rate, but still a new per-user line item	One build, one fee, no per-module stacking

Where the fix actually lives

The light-user and self-service workload sitting around a Dynamics 365 deployment — status lookups, request forms, reporting dashboards for people who don’t need full edit access — doesn’t need a Team Member or Professional seat at all. A custom-built portal synced to Dynamics via API can carry that workload on one flat monthly fee instead of licensing every occasional user. See how to reduce per-seat CRM licensing costs and the seat-cost-vs-custom-portal comparison for the same pattern applied to another major CRM.

Model the numbers for your own user count with the savings calculator, and see HubSpot vs. Salesforce true cost of ownership for how another CRM pair compares.

Frequently asked questions

Does a custom portal replace Dynamics 365 entirely?

No — it’s built to sync with Dynamics via API. The core sales pipeline, case management, and Microsoft 365 integration stay in Dynamics; the portal covers light-user and self-service access that doesn’t need a full per-user license.

What is the “base-and-attach” model, exactly?

It’s Microsoft’s discounting structure for users licensed across multiple Dynamics 365 apps: the first app for a user is billed at full tier price, and each additional app attached to that same user is billed at a lower flat rate — an incentive to expand module footprint on existing licensed users.

Do occasional or read-only users need a paid license?

Generally yes — Microsoft’s Team Member tier covers light, mostly-read usage at a lower per-user rate, but anyone creating or editing records meaningfully needs a Professional-tier-or-above license, which is the more expensive part of the per-user bill.