Platform pain
Base, attach, and the costliest Dynamics licensing error
The costliest Dynamics 365 licensing error is paying full base price for users who should sit on a cheaper attach license, then letting duplicate base licenses pile up across teams that nobody reconciles. In the base and attach model each user needs exactly one base license, priced at their most expensive app, and pays a small attach fee for every other app they touch. Get the pairing wrong and you overpay every month, indefinitely.
How does base and attach actually work?
Microsoft prices Dynamics 365 per user, but not every app a user touches is charged at full rate. The first qualifying app is the base, billed at list price. Every additional app is an attach, billed at a steep discount, on one condition: the base must be the highest-value license that user holds. You cannot attach a $210 app under a $30 one. As documented in the Encore Business licensing guide, Finance and Supply Chain Management run about $210 per user per month as base (as of September 2025), a second Finance or SCM app attaches at $30, a Customer Engagement app attaches at roughly $20, and the Premium tier lists at $300.
| License | Role | Per user / month (as of Sep 2025) |
|---|---|---|
| Finance or Supply Chain Management | Base | ~$210 |
| Second Finance / SCM app | Attach | $30 |
| Customer Engagement app | Attach | ~$20 |
| Finance / SCM Premium | Base | $300 |
| Finance & SCM seat floor | Minimum | 20 full users |
On paper the discount is generous: a $30 attach against a $210 base is an 85 percent markdown for the second app. The trap is that the model assumes someone is actively assigning the cheapest valid combination to every person. Nothing in the tenant does that for you. Assignments are made by hand, at onboarding, by whoever happened to be provisioning that week, and they are almost never revisited once the user can log in.
Why is a duplicate base license the costliest error?
Redress Compliance is blunt about which mistake hurts most, calling duplicate base licenses:
the most common and most expensive Dynamics mistake
It happens structurally, not through carelessness. One business unit provisions a user with a Finance base; another later gives the same person a Sales base for pipeline work, when a Customer Engagement attach under the existing base would have covered it. Two admins each buy a base because neither can see the other's assignments. A role change adds an app but never demotes the old one. The gap between a $210 base and a $30 attach is $180 per user per month, roughly $2,160 a year for a single misassigned seat. Multiply that by a few hundred office and depot users and the leak is a line item, not a rounding error.
You do not have to take the framing on faith. Independent reviews find real money sitting in these assignments: license audits routinely
recovered 15 to 28 percent of annual license cost
per Redress Compliance. When a third party can reclaim a quarter of your annual spend just by rereading who holds what, the default state of a Dynamics tenant is over-licensed, not right-sized. The savings are not a clever optimisation; they are the correction of an error that compounded quietly for two renewal cycles.
What does the 20-user minimum add?
Finance and Supply Chain Management carry a 20 full-user minimum (as of September 2025). Pilot F&O in a single region with eight users and you still pay for twenty. The floor turns a cautious pilot into a commitment before you have proven any value, and it interacts badly with base misassignment: the twenty seats you are forced to buy are exactly the ones most likely to be mispriced, because a rushed pilot is where nobody stops to check whether each user needs a base or an attach. It is the same class of platform behaviour we picked apart in 500 seconds and no log: batch jobs in F&O — the system runs by its own rules regardless of your operational reality, and the surprise lands on your side of the invoice.
Is the CRM side any simpler?
No. A G2 reviewer describes the Sales side directly:
Licensing is a maze (Professional vs. Enterprise vs. Premium + Copilot add-ons), and it's easy to overbuy
as recorded in G2 reviews. Professional, Enterprise and Premium are stacked tiers, each with a Copilot add-on layered on top, and the decision is made per seat. Your field reps rarely need the Enterprise feature set they get assigned by default, but every over-tiered seat is recurring cost that renews itself unless someone actively steps it down. The field client is where over-provisioning hides best, because it is the tool nobody in finance ever opens — the same weak link we examined in 1.9 stars: when the field app is the weakest link.
Why does this keep happening?
Because the model is optimised for the vendor's revenue floor, not your consumption, and nothing in the default tooling pushes back. Renewals roll last year's assignments forward untouched. There is no native alert flagging the forty users paying base when they qualify for attach. Business units procure independently, so the same person can end up with two bases and no single owner to notice. And the attach rules themselves shift between releases, so a mapping that was optimal two years ago quietly is not anymore. It is the familiar shape of a platform commitment that outlives the fit it was bought for — the same trap we described in when your commerce platform goes end-of-life under you. The complexity is not a bug in the licensing; it is the product working as designed, and the design does not have your budget as its objective function.
The direction out is unglamorous. Reconcile assigned licenses against actually consumed apps every quarter, pin each user to a single correct base, treat the 20-user floor as a go/no-go gate before a pilot rather than a discovery after the first invoice, and ask the harder question of whether every route-to-market workflow belongs on a per-seat platform at all. Some of ours run cheaper on the event-driven route-to-market suite we build and own, with the SAP financial core left untouched.
Licensing maths will not fix itself, and the next renewal cycle will quietly re-propose whatever you signed last time. The teams that come out ahead into 2026 will be the ones treating license assignment as a monitored, event-driven data problem — one more feed on the bus, reconciled continuously against real usage — rather than a spreadsheet someone opens the week before renewal, once the numbers are already locked in.
Frequently asked questions
What is the difference between a base and an attach license in Dynamics 365?
A base license is a user's most expensive app, billed at full list price. An attach license covers each additional app at a steep discount, but only while a base of equal or greater value sits on that same user. Every full user needs exactly one base.
Why are duplicate base licenses so costly?
A base runs about $210 per user per month against roughly $30 for an attach (as of September 2025). Assigning two bases where one base plus an attach would do wastes around $180 per user monthly — over $2,000 a year per seat, compounding across hundreds of users.
Does the Dynamics 365 Finance 20-user minimum apply to pilots?
Yes. Finance and Supply Chain Management carry a 20 full-user minimum (as of September 2025), so an eight-person pilot still pays for twenty seats. Treat that floor as a go/no-go gate before committing, not a surprise discovered after the first invoice arrives.
Stuck with exactly this?
BrewOS builds the full route-to-market stack for global brewers — order capture, stock, loyalty, returnables, delivery and analytics on one event bus, run by a team of ~20 engineers. Bring us the feature that’s been stuck the longest and we’ll show you how we’d ship it in days.
Book a 30-minute walkthrough