Dynamics 365 is a family of applications, each licensed per user, with a cheaper attach price once a user holds a qualifying base. Map the role first, then license to it.
Dynamics 365 is licensed per user, per application, with base and attach pricing that rewards buyers who map real roles to use rights before they buy. This guide explains the model, the per user math, the overpayment traps, and how to cut the bill.
Dynamics 365 is not one product with one price. It is a family of applications, each licensed per user, with a cheaper attach price once a user already holds a qualifying base license.
Get the base and attach math right and the bill is reasonable. Get it wrong and you pay full price for seats that should have cost a fraction.
Dynamics 365 is licensed per named user, per application, per month. A user who needs two applications buys one at the base rate and the second as a cheaper attach license, provided the first qualifies.
The base license is the first full price application a user holds. Any additional qualifying application that user needs is an attach license at a much lower monthly rate. Microsoft sets the qualifying base list in the Dynamics 365 licensing guide.
Not every user needs a full application license. The Team Members license covers light, read mostly and basic write tasks across applications. It is a fraction of a full seat but its use rights are deliberately narrow, as set out across the Dynamics 365 product line.
A Dynamics 365 subscription includes the right to run the workload in Microsoft cloud, and in defined cases on premises. The use rights that govern this sit in the Microsoft Product Terms, which override any sales summary.
Published list pricing is per user per month. The base rate applies to the first application, the attach rate to the second, and Team Members sits well below both.
The line splits into customer engagement applications and the finance and operations applications. Microsoft lists current rates on the Dynamics 365 pricing page, and they move, so always price against the live sheet.
Illustrative Dynamics 365 per user pricing structure (confirm live rates before any quote)
| Application | Role | Licensing note | Buyer side move |
|---|---|---|---|
| Sales Enterprise | Seller | Common base license | Confirm Premium is genuinely needed |
| Customer Service Enterprise | Agent | Base or attach | Attach to Sales where a user does both |
| Finance / Supply Chain | Operations | Higher base, first one full | Attach the second operations app |
| Team Members | Light | Restricted use rights | Map roles before assuming it fits |
Overpayment rarely comes from the list price. It comes from assigning full base licenses where an attach or Team Members seat was the correct fit, and from leaving seats provisioned after roles change. The Microsoft licensing resources set the rules, but the assignment errors are yours to fix.
When two applications are bought as two base licenses, the buyer pays full price twice. If the first qualifies, the second should be an attach at a fraction of the rate. This single mapping error recurs in most estates we review.
Team Members is cheap because it is limited. Used for work it does not permit, it becomes a compliance exposure that surfaces at renewal or in a review, converting a saving into a back bill.
The standard reseller pitch is to standardize the whole user base on full Enterprise licenses because it keeps administration simple. We disagree. Across the Dynamics estates we have benchmarked, a large share of assigned full seats were doing work that an attach license or Team Members covered, and the simplicity argument quietly funded a double digit overspend. The buyer side move is to map real roles to use rights first, then license to the role, not to the convenience of a single uniform SKU. Uniformity is a vendor preference, not a buyer saving.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Dynamics 365 list price is rarely the problem. The license type assigned to each user is. Map the role before you buy the seat.
The work is a role to license reconciliation. You match real usage to the cheapest license that legally covers it, then remove what no one uses.
Pull every assigned Dynamics 365 license and the role behind it. Flag full seats doing attach or Team Members work, and Team Members seats doing full work. Both are corrections, in opposite directions.
A base license is the first full price Dynamics 365 application a user holds. It sets the qualifying entitlement that lets any additional application be bought at the lower attach rate, which is why the first application choice drives the rest of the user cost.
Attach licensing lets a user who already holds a qualifying base application add a second application at a much lower monthly rate. The base must appear on the Microsoft qualifying list, so confirm eligibility before assuming the attach price applies.
Team Members covers light, read mostly and basic write tasks across applications at a fraction of a full seat. Its use rights are narrow and published, so assigning it to a user doing full operational work is a compliance exposure, not a saving.
No. Copilot for Dynamics 365 is priced on top of the base application, not bundled by default. Assign it only to users with proven recurring need, because org wide Copilot assignment is one of the most common sources of unused spend we see.
Dynamics 365 is priced per named user, per application, per month, with a base rate for the first application and a lower attach rate for the second. Microsoft publishes current rates on its pricing page, and they change, so price against the live sheet.
Sales Enterprise is the common base seller license, while Sales Premium adds advanced features such as built in intelligence at a higher rate. Many sellers never use the Premium features, so confirm genuine need before standardizing the whole team on Premium.
Most overpayment comes from assigning full base licenses where an attach or Team Members seat fit, and from leaving seats provisioned after roles change. The list price is rarely the issue, the license type assigned to each user is.
Reconcile every assigned license against the real role, move qualifying users to attach pricing, keep Team Members inside its use rights, cap add ons to proven need, and reclaim dormant seats before renewal. Map the role before you buy the seat.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
