Dynamics 365 licensing explained

Dynamics 365 licensing is one model applied to three quite different product families, and most confusion comes from mixing up which family's rules you're reading about. This guide is the umbrella: the shared base-and-attach model, how each family tiers its users, and a picker table for matching licences to what people actually do. The authoritative source is Microsoft's Dynamics 365 Licensing Guide, a PDF re-issued several times a year — every number below is a rough 2026 range, not a quote.

The base + attach model

Every full user needs exactly one base licence — the first Dynamics 365 app they use, at full list price. Any further qualifying apps for the same user are attach licences at a flat, heavily discounted rate (roughly $20–30 per user per month, versus $65–210 for a base).

Two rules do all the work:

1. The most expensive app must be the base. A user who needs Finance and Sales licenses Finance as base and attaches Sales — not the other way round.
2. Base and attach are per user, not per team. Attach pricing never applies to a second person; it applies to a second app on the same person.

Base + attach is where mixed CRM-and-ERP shops either save or waste real money. Model it per user before accepting any quote — the difference between "everyone gets two bases" and a correct attach structure is routinely five figures a year at even modest headcounts.

Three families, three licensing personalities

Business Central (SMB ERP) is the simplest: two full-user SKUs — Essentials and Premium — plus Team Member, Device, and a free External Accountant licence. One hard rule: all full users in a tenant must be on the same SKU. Full users run roughly $70–110 per user per month. The detail lives in Business Central licensing and pricing and Business Central pricing tiers explained.

Customer Engagement (Sales, Customer Service, Field Service, Customer Insights) tiers by capability: Professional SKUs (cheaper, capped features, can't mix with Enterprise in the same tenant for the same app), Enterprise (the default), and Premium (Enterprise plus the AI bundle). Expect roughly $65–105 for Professional/Enterprise bases and meaningfully more for Premium. Channel add-ons complicate service scenarios — see omnichannel licensing for Customer Service.

Finance and Operations (Finance, Supply Chain Management, Commerce, Project Operations) has the highest per-user prices — roughly $180–210+ per base — but also the richest set of reduced-access options: Activity users (limited transactions), Device licences for shared shop-floor and warehouse terminals, and Team Members. F&O also carries minimum purchase requirements for the first app, which is why it rarely makes sense below the mid-market — a point covered in the edition comparison.

The license picker

Find the row that describes what the person actually does — not their job title:

Three habits keep the table honest. First, licence the behaviour, not the org chart — "manager" is not a licence type. Second, re-check twice a year: people drift from full use into approval-only, and licence optimisation is mostly harvesting that drift. Third, treat Team Member as a compliance boundary, not a discount trick — Microsoft has tightened its enforcement steadily, and a Team Member quietly posting journals is the most common audit finding across all three families.

What the licence does not include

The per-user fee is the visible part. Budget separately for:

• Dataverse and F&O storage beyond the pooled entitlement — database capacity is the expensive tier, and attachments belong in cheaper file storage.
• Power Platform — standalone Power Apps, premium Power Automate connectors, and Power Pages capacity are licensed separately; the Power Apps rights included with a Dynamics licence only cover apps in the same environment extending the licensed app.
• Copilot and AI — some AI features ride along with Premium tiers, Microsoft 365 Copilot is always a separate licence, and the boundary moves every release; the current state is tracked in licensing updates for Dynamics 365 in 2026.
• Additional environments — extra production environments are paid add-ons in every family.

For how licences fit the full cost picture — implementation, ISVs, integration, run — see TCO modelling, and for negotiating the ongoing bill, the renewal strategy guide.

Common licensing mistakes

The mistakes recur across implementations because they follow the shape of how buyers think, not the shape of the rules:

1. Two bases for one user. The most common overspend — sales gave everyone a Sales Enterprise licence, finance gave everyone a Finance base, and nobody stacked attach on top. Any user needing more than one app should have exactly one base (the pricier of the two) and every other app as an attach.
2. The wrong app as base. Attach is a flat rate applied to the cheaper app. Licensing Sales as base and Finance as "attach" is a licensing violation, not a discount; a Microsoft audit finds it. The base is always the most expensive app the user needs.
3. Team Member used as a cheap full user. Team Member is a defined entitlement: read, approve, time and expense, edit own contact and personal info. Posting an invoice, processing an order, or running a batch is not on it. Microsoft has tightened enforcement steadily — a Team Member quietly posting journals is the most common audit finding across all three families.
4. Mixing Essentials and Premium in a Business Central tenant. All full users in a Business Central tenant must be on the same SKU. If one department needs manufacturing or service management, the entire tenant is Premium — model both scenarios before choosing.
5. Professional and Enterprise in the same app. Customer Engagement Professional SKUs cannot be mixed with Enterprise for the same app in the same tenant. Adopting Professional as a "starter" tier locks that choice in until the whole app is uplifted.
6. Forgetting attach across families. Attach works across families — a Sales Enterprise user can attach Business Central Essentials, and vice versa. Buyers routinely miss this because the two families feel like different products; the licence rule treats them as one estate.
7. Under-licensing external portal users, then bolting on individual licences. Customers and suppliers using a portal are covered by Power Pages capacity (anonymous or authenticated), not per-user Dynamics licences. Buying individual licences for external users is almost always the wrong shape.
8. Ignoring storage until the alert lands. Dataverse and F&O database entitlements are pooled at the tenant level, and once the pool tips over the add-on rates are much higher than the per-user headline suggests. Keep attachments in file capacity, not database, and see Dataverse storage types explained.
9. Free Copilot assumptions. Some AI features ride with the Premium tier; many do not. The boundary moves at every wave, and it is the single most under-modelled line item in a Dynamics quote today.
10. No annual optimisation review. People drift from full use into approval-only; departments come and go. Licence optimisation is mostly harvesting that drift twice a year — the biggest single lever after the base-and-attach structure is set.

If any of the top three describe your current estate, the annualised recovery from fixing them usually pays for the optimisation exercise inside the first quarter.

How to buy

Same channels as the rest of Microsoft's cloud: direct online at list price, through a CSP partner (most common for Dynamics, since you likely have an implementation partner anyway), or on an Enterprise Agreement / MCA-E at volume. Discounts are negotiated, not published, and they concentrate on the big-ticket F&O SKUs. If you're still deciding which apps to license in the first place, start with how to choose the right Dynamics 365 product — the licence follows the product decision, never the reverse.