Contents
Key takeawaysBase and attachFull users and Team MembersChecking your licensesAvoiding overbuyingWhat we have seenRenewalWhat to do nextFAQDynamics 365 charges each user one full price base license, which must be their highest priced app, plus low cost attach licenses for extra apps. Mapping every role to the cheapest license that covers it saves more than a deeper discount.
- One base per user. Each user pays full list once for a base license, and it must be the highest priced app that user holds.
- Extra apps attach cheaply. A second app for the same person costs $20 per user per month as an attach, against $105 as a base.
- Team Members covers light roles. At $8 it allows reading all data and editing activities and contacts, in designated apps only.
- Any device is included. One user license covers web, mobile and Outlook access, so no one needs a license per client.
- Channel changes flexibility. An Enterprise Agreement and CSP differ on price, payment terms and how far seats can flex.
- Renewal is a price defense. Microsoft raised Dynamics list prices on October 1, 2024, so benchmark any uplift.
- Role mapping comes first. Most Dynamics overspend is recovered by fixing the seat mix before discussing volume discounts.
Dynamics 365 pricing looks simple on Microsoft's web page. Most of the cost sits in how you assign licenses to people. Give each role the right base license and the model works in your favor. Get it wrong and you pay full list price for the same person more than once.
How does Dynamics 365 base and attach licensing work?
Each user holds one base license at full list price, then adds any further Dynamics 365 apps as attach licenses at a much lower price. Microsoft's licensing guide also requires the base to be the highest priced app that user needs.
The base license
The base is the user's first qualifying Dynamics 365 application, charged at full list. Microsoft publishes these rates on the Dynamics 365 pricing page. Current annual commitment prices per user per month include Sales Professional at $65, Sales Enterprise at $105 and Sales Premium at $150.
On the service side, Customer Service Professional is $50, Customer Service Enterprise $105 and Field Service $105. Finance and Supply Chain Management are $210 each. Pick the base that matches the user's primary role, then check it is also the most expensive app they hold.
The attach license
Once a user holds a qualifying base, extra apps attach at a steep discount. Sales Enterprise, Customer Service Enterprise and Field Service attach at $20 per user per month. A user may hold several attach licenses, but only while the same person holds a qualifying base, so Team Members cannot carry one.
Base versus attach in practice
The table prices the same two apps for one user, depending on how you buy the second one. Use it as the reference point for every role mapping decision.
| Approach | First app | Second app | Monthly cost | Relative cost |
|---|---|---|---|---|
| Two base licenses | Sales Enterprise, $105 | Customer Service Enterprise, $105 | $210 | Highest |
| Base plus attach | Sales Enterprise, $105 | Customer Service Enterprise attach, $20 | $125 | Much lower |
| Team Members only | Team Members, $8 | Read access and light edits included in scope | $8 | Lowest |
The highest priced rule matters most for users who work in both ERP and CRM. Someone who needs Finance and Sales Enterprise carries Finance as the base at $210 and adds Sales as a $20 attach, for $230. Two bases would cost $315, and a Sales base with Finance attached is not a valid assignment.
How to Prepare for Your Microsoft EA Renewal in 2027
What is the difference between full users and Team Members?
Full users run the complete business process in an app. Team Members users read data and make limited updates, at $8 per user per month against $105 or more for a full user. How you split people between the two decides most of the bill.
Full user licenses
A full user can run everything the app offers, from creating opportunities to processing service cases and posting journals. Microsoft sets out qualifying use per app in its Dynamics 365 licensing guide, which Microsoft points to, alongside the Product Terms, whenever use rights are in question.
Team Members licenses
Team Members covers read access to all Dynamics 365 data plus a short list of edits. Its scope is fixed and narrow, and Microsoft limits it both by task and by app.
- Allowed. Read any Dynamics 365 record, create and update contacts, activities, notes and personal views, and log and follow their own cases in the Customer Service Team Member app.
- Not allowed. Changing accounts, opportunities, orders, quotes or invoices, working other people's cases as a service agent, and scheduling or dispatch work.
- App limits. Users can open only designated apps such as Sales Team Member, Customer Service Team Member and Project Resource Hub. Sales Hub and Customer Service Hub return an invalid license error once enforcement is on.
- No custom apps. A custom app built on Dataverse needs a Power Apps license on top, so price the two together.
Operations Activity and device licenses
Finance and operations apps have a middle tier. Operations Activity is a named user license for people who need more than Team Members but less than a full user, for example people who approve documents or run a narrow set of tasks.
Device licenses suit shared stations. Operations Device lists at $85 per device per month, and Customer Service Device, Sales Device and Field Service Device at $160. Microsoft says a Customer Service Device license carries the rights of the Enterprise user license, limited to that one device.
Mapping roles to the right license
A role by role review is the fastest saving in any Dynamics deployment. Sort every user into one of these groups before you look at price:
- Full user. Owns the process and needs full create and edit rights on core records.
- Team Members. Reads, reports and makes limited updates to activities and contacts.
- Device or frontline. Shift workers who share a station may fit a device license or another frontline plan.
- Administrator. The Power Platform Administrator and Dynamics 365 Administrator roles in Entra, and System Administrator in Dataverse or finance and operations, need no license to configure the system.
The Microsoft EA renewal white paper
Our guide to the 2024 to 2026 EA cycle, from renewal timing to the price holds to request. Read it in your browser.
Get the white paper →How do you check which Dynamics 365 licenses your users need?
Start with Microsoft's own reports, which compare assigned licenses with what each user's security roles require. The finance and operations side matters most, because Microsoft blocks sign in for users without the required license once license validation starts.
- Microsoft 365 admin center. Billing, then Licenses, shows purchased and assigned counts per SKU and the named users holding each one.
- Power Platform admin center. Licensing, then Finance and Operations, opens the User License Consumption report, which lists unlicensed, under licensed and over licensed users.
- Finance and operations apps. System administration, then Security, then Security Governance, then License usage summary, shows the minimum license each role, duty and privilege requires.
- Activity data. Microsoft Entra sign in logs and Dataverse user access auditing show who signs in and when.
Read the over licensed list first, since it shows full users on roles a cheaper license covers. One privilege added to a custom role can raise the required license for everyone in that role, so fix role design before you buy.
How do you avoid overbuying Dynamics 365 licenses?
License people for the work they do each week, measured from usage data. The model gives you several cheaper paths if you map roles carefully and use the rights each license already carries.
Use the access rights every user license includes
A Dynamics 365 user license grants a named user access from any device. The same person can work in the web app, the mobile app and the Outlook client without a separate license for each.
Microsoft uses the term dual use rights for something else. In the Microsoft product terms, dual use rights allow a customer with active Dynamics 365 subscriptions to install the matching on premises server software, which helps if you keep an on premises instance during a migration.
Buy attach, not duplicate base
When a user needs a second app, buy the attach license rather than a second base. Duplicate base licenses are the most common and most expensive Dynamics mistake we find, and they often come from two projects ordering licenses for the same people.
Run a usage review before renewal
Pull active usage by user and app, then reassign or drop seats that show no real activity. Do this before the renewal quote arrives.
- Inventory. List every assigned license by user and app.
- Match. Map each user to the cheapest qualifying license.
- Reduce. Remove or downgrade seats with no real usage.
- Confirm. Rerun the consumption report so no user ends up under licensed.
Why we would not start with a bigger volume commitment
The standard partner advice is to consolidate spend, commit to more seats and negotiate a deeper percentage discount. We think that sequence is backwards. In roughly 6 of 10 Dynamics deployments we have reviewed, the discount was healthy and the seat mix was wrong, with full users doing Team Members work and second apps bought as duplicate bases.
Fix the role mapping first. Removing the wrong licenses is worth far more than another two points off the right ones, as the example below shows, and a clean seat count shortens the discount conversation too.
A worked example for 400 sales users
Say a company licenses 400 people on Sales Enterprise at $105. Sixty of them also work service cases and were given Customer Service Enterprise as a second base. A review finds 80 users who only read records and log activities, and switches them to Team Members.
| Line | Before | After |
|---|---|---|
| Sales Enterprise base, $105 | 400 users, $42,000 | 320 users, $33,600 |
| Customer Service Enterprise for dual role users | 60 bases at $105, $6,300 | 60 attach at $20, $1,200 |
| Team Members, $8 | None | 80 users, $640 |
| Monthly total | $48,300 | $35,440 |
| Annual total | $579,600 | $425,280 |
The saving is $12,860 a month, or $154,320 a year, about 27 percent of the bill. Two extra points of discount on the original $579,600 would be worth $11,592 a year.
Common mistakes that inflate the bill
- Keeping leavers' licenses. Seats stay assigned after people leave or change roles, and an annual CSP subscription cannot shrink mid term.
- Getting the base order wrong. A lower priced app set as the base, with a dearer app attached, will not survive a compliance review.
- Buying Premium for everyone. Premium tiers add Copilot Credits and agent features, which pay off only for the users who run those agents.
What have we seen in Dynamics 365 reviews in 2024 and 2025?
Across roughly 25 to 35 Dynamics 365 customers we benchmarked in 2024 and 2025, role mapping recovered 15 to 28 percent of annual license cost before any discount was negotiated. The median saving was 24 percent, and about 1 in 4 full seats fit a lighter license.
The same three patterns turned up again and again:
- Full seats on light roles. Users held a full base license where Team Members covered their real tasks, in 20 to 30 percent of seats.
- Attach bought as base. Second apps were bought as full base licenses, inflating the cost of multi app users by 40 to 60 percent.
- Uplifts accepted without a review. Renewal uplifts of 10 to 18 percent were signed without the usage review that would have cut the seat count first.
Dynamics pricing is decided in the seat mix, where one full user who should hold a Team Members license is repeated across hundreds of people.
What changes at a Dynamics 365 renewal?
Renewal is where price increases land and where a stale seat count gets locked in for another term. Prepare it the way you would any negotiation, starting with the numbers you control.
Price uplifts
Microsoft has raised Dynamics list prices, so the renewal quote often carries an uplift on top of your current spend. The last broad change took effect on October 1, 2024.
| Product | Before | From October 2024 |
|---|---|---|
| Sales Enterprise | $95 | $105 |
| Sales Premium | $135 | $150 |
| Customer Service Enterprise and Field Service | $95 | $105 |
| Finance and Supply Chain Management | $180 | $210 |
| Human Resources and Project Operations | $120 | $135 |
| Sales, Customer Service or Field Service Device | $145 | $160 |
| Operations Device | $75 | $85 |
Benchmark the quoted rate before you accept it, and check which of these increases your current term already absorbed.
Agreement and channel
Whether you renew through an Enterprise Agreement or through a partner on CSP changes price points, payment terms and your freedom to flex seats during the term. Microsoft designs the EA for organizations with at least 500 users or devices, and additions go into a true up order due 60 to 30 days before the anniversary.
- CSP annual terms. Seats can be reduced only within seven days of purchase.
- CSP monthly terms. Cancel at the end of any month, at a higher unit price.
- Minimums. Finance, Supply Chain Management, Commerce and Project Operations each carry a 20 license minimum in the Product Terms.
A 150 user CRM deployment usually fits CSP with a mix of annual and monthly terms. A 3,000 user ERP and CRM customer tends to get firmer price holds inside an EA. Our EA versus CSP guide compares the two in detail.
Timing the review
Start the usage review three to six months before renewal. The reduced, correct seat count becomes your negotiating baseline rather than a concession you ask for later.
| When | What to do |
|---|---|
| 6 months before | Export assigned licenses, run the consumption reports and start role mapping with app owners. |
| 3 months before | Agree the cleaned seat count, test Team Members users in the designated apps and request the quote. |
| 60 to 30 days before (EA) | Submit the true up order and any reductions your enrollment allows at the anniversary. |
| Final month | Close on price holds and contract terms, and check the quote against the cleaned count line by line. |
What the account team will say, and how to answer
- "Anyone who uses Dynamics needs a full license." Ask them to name, role by role, the tasks that fall outside the Team Members scope in the licensing guide.
- "Premium includes Copilot, so it pays for itself." Sales Premium adds 1,000 Copilot Credits per user per month for $45 more than Enterprise. Count who will run agents and price credits for that group through Copilot Studio.
- "License validation will block your users, so buy now." Run the User License Consumption report yourself. Security role changes often close the gap without new licenses.
- "A larger commitment earns a deeper discount." Agree the seat count first, then negotiate the rate on that number.
Contract terms to ask for
- Price hold for the term. Keeps a mid term list increase off your invoice.
- Cap on renewal uplift. Limits the next increase to an agreed percentage.
- Right to swap license types. Allows you to move full users to Team Members or attach licenses when roles change.
- Stated attach pricing. Fixes the attach price for apps you may add later, so a new project does not arrive at base rates.
For the full negotiation sequence, see our guide to negotiating Dynamics 365 contracts, the Microsoft EA renewal guide if Dynamics renews alongside Microsoft 365, and the list of common Dynamics 365 licensing mistakes.
What to do next
- Export. Pull every assigned Dynamics license by user and by application.
- Map. Assign each user the cheapest license that covers their real tasks, with the highest priced app as the base.
- Convert. Change duplicate base licenses for multi app users into attach licenses.
- Stop double counting. Rely on the any device access in each user license so no one is licensed twice across clients.
- Clean. Run a usage report and remove or downgrade inactive seats.
- Benchmark. Test any renewal uplift against the market and compare Enterprise Agreement against CSP.
- Review. Check the result against the EA versus CSP guide and the renewal guide.
- Get a second opinion. Engage independent Microsoft advisory before you sign the renewal.
Frequently asked questions
What is base and attach licensing in Dynamics 365?
Every user needs exactly one base license at full list price, and it has to be the most expensive Dynamics app that person uses. Further apps for the same person are bought as attach licenses at a reduced rate, so choosing the base correctly is where the model rewards you.
What is a Dynamics 365 Team Members license?
It is the light license for people who mostly consume data. It gives read access across Dynamics 365, edits to contacts, activities and notes, and the Team Member versions of the Sales and Customer Service apps. Users can log their own cases, but changing accounts, opportunities, quotes or orders needs a full license.
When should I use an attach license instead of a base?
Whenever the user already holds a qualifying base and needs one more app. A second base for the same person buys no additional right and can nearly double what that user costs, so ask your partner to show base and attach lines separately on every quote.
What are Dynamics 365 dual use rights?
In the Microsoft Product Terms, dual use rights let a customer with active Dynamics 365 subscriptions install the matching on premises server software. Web, mobile and Outlook access is a separate matter, covered by the user license on any device, so neither should be paid for twice.
Is it cheaper to buy Dynamics through an EA or CSP?
It depends on size and how often headcount changes. An EA is designed for 500 or more users or devices and suits stable, larger customers. CSP suits smaller or changing teams, but annual CSP seats cannot be reduced after the first seven days, so compare flexibility as well as unit price.
How much can role mapping save on Dynamics 365?
In our benchmarks it recovered 15 to 28 percent of annual license cost before discount talks began. Most of that came from moving light users to Team Members and from converting duplicate base licenses into attach licenses for people who work in two apps.
What happens when a Dynamics 365 subscription comes up for renewal?
List price increases reach your invoice, and last term's seat count rolls forward unless you change it. Customers whose agreements predate October 2024 often see the new rates for the first time. Clean the seat count months ahead and negotiate price holds on that number.
Should we get independent advice on Dynamics 365 licensing?
It helps when the seat count is large or the quote carries an uplift. Resellers and account teams are paid on what you buy, so they have little reason to move users to cheaper licenses. An independent adviser builds the seat plan and price benchmark with no stake in the result.