Most of the money wasted on a Dynamics 365 purchase is not wasted on the wrong application. It is wasted on buying the right applications the wrong way: two full licenses for one person who was entitled to a discounted second one, a cheap license for someone whose job that license does not permit, or storage overages nobody planned for.
This guide covers what each application and tier unlocks, and where the structure quietly costs money. We link to Microsoft's pricing pages rather than reprint figures, because a number in an article ages badly. The authoritative source is the Dynamics 365 Licensing Guide, checked here against the June 2026 edition, with the Product Terms as the binding document.
The applications, in plain terms
Dynamics 365 Sales manages the pipeline: leads, accounts, opportunities, quotes, orders, and forecasting.
Dynamics 365 Customer Service manages the support desk: cases, entitlements, service level agreements, knowledge articles, queues, and routing.
Dynamics 365 Project Operations manages project delivery: project quoting and contracts, resourcing, timesheets, expenses, project accounting, and billing. It suits firms that sell work rather than goods, and it reaches further into finance than the other two.
Dynamics 365 Field Service manages on-site work orders, dispatch, and technicians. It is not the focus here, but it runs through the licensing rules below.
All four sit on the same database and platform, called Dataverse. That shared foundation is why one person can hold several of these sensibly, and why the storage and extensibility rules below apply across all of them at once.
A fifth product, Dynamics 365 Customer Insights, combines a marketing and customer journey tool with a customer data platform. It is licensed per tenant rather than per user, and its capacity works in entirely different units. We cover it separately; treat it as a related purchase rather than a component of the three above (Customer Insights).
Choosing a tier in Dynamics 365 Sales
This decision sets your per-seat cost for every seller you will ever hire (Sales pricing page).
Sales Professional is what Microsoft calls essential sales force automation for organizations without complex sales processes. Leads, contacts, accounts, opportunities, quotes, orders, and invoices are all there. What it lacks is customization: users are capped at 15 custom tables, five customized business processes, and five custom reports or dashboards, and cannot use the Sales Hub application where several advanced features are configured.
Sales Enterprise removes those caps, adds embedded intelligence and manual forecasting, and includes Copilot in Dynamics 365 Sales, conversation intelligence, the sales accelerator worklist, and predictive lead and opportunity scoring, each with a metered allowance.
Sales Premium adds the full Sales Insights set (predictive forecasting, relationship analytics, pipeline intelligence, notes analysis, and connection insights) plus uncapped use of the features Enterprise meters.
The test: if you need to model your own sales process, add your own tables, or report beyond a handful of dashboards, you need Enterprise. If leadership will act on predictive forecasting and call analysis at scale, Premium earns its keep. Otherwise Professional is the correct product rather than a compromise. One constraint catches people: Enterprise and Professional users may not share an environment, so you cannot mix tiers to economize on lighter users.
Choosing a tier in Dynamics 365 Customer Service
Customer Service has three tiers, not two (pricing page).
Customer Service Professional provides case management, knowledge management, mobile access, lead creation, and a self-service website for customers. Customization is limited, as in Sales.
Customer Service Enterprise adds unified service desk, embedded intelligence, context-driven suggestions, analytics, multisession support, portals, and Copilot in Dynamics 365 Customer Service. It also grants rights to schedule and dispatch service, create teams, and manage resources through integration with Field Service and Project Operations, plus a monthly unified routing allowance.
Customer Service Premium bundles Customer Service Enterprise with Dynamics 365 Contact Center (digital and voice channels). One asymmetry: Customer Voice is included with Enterprise but not with Premium.
The dividing line is routing and channels. A team picking cases off a shared queue is well served by Professional. A team that needs work distributed automatically, or that answers on live phone and messaging channels, needs Enterprise.
Project Operations is sold as a single tier rather than a ladder (pricing page).
Base and attach: the part most buyers get wrong
This is where the money is. If one person needs two Dynamics 365 applications, you should not pay full price twice, and many organizations do exactly that for years.
How it works
When you buy multiple Dynamics 365 applications for a single named user, the first must be the highest priced one. That is the base license. Every additional application for that same user can then be bought at a substantially reduced attach price.
The detail that makes the saving so large: base and attach licenses are identical in their core capabilities and differ only in price. What attach licenses do not carry is platform entitlements; they ride on the storage and capacity that came with the base license.
Which applications qualify
Not every combination is permitted, and direction matters. The licensing guide publishes a grid:
| Base license | Can attach |
|---|---|
| Sales Professional | Customer Service Professional |
| Sales Enterprise | Customer Service Enterprise or Professional, Field Service, Business Central Essentials |
| Sales Premium | Customer Service Enterprise or Professional, Field Service, Project Operations, Human Resources |
| Customer Service Enterprise | Sales Enterprise or Professional, Field Service, Business Central Essentials |
| Customer Service Premium | Sales Enterprise or Professional, Field Service, Business Central Essentials |
| Project Operations | Sales Enterprise or Professional, Customer Service Enterprise or Professional, Field Service, Human Resources |
| Field Service | Sales Enterprise or Professional, Customer Service Enterprise or Professional, Business Central Essentials |
Read that grid alongside the highest-price-first rule and the sequencing becomes clear. Sales Enterprise cannot have Project Operations attached, because Project Operations is the more expensive of the two. If someone needs both, Project Operations must be the base. Buy them in the wrong order and you pay the full rate twice for the same person.
Attach is per person, not per company
An attach license is assigned to a named user who already holds a qualifying base license. It is not a tenant-wide discount, and Microsoft enforces this in the software: an administrator cannot assign an attach license to a user who lacks the required base. The base must also stay active on that user; remove or reassign it and the attach license has nothing to sit on.
A single user may hold more than one attach license. Because base and attach are per person, a mixed team is the normal outcome: some people on a Project Operations base with Sales Enterprise attached, some sellers on Sales Enterprise alone, some agents on Customer Service Enterprise, and the rest on Team Members.
A worked example
Consider a sales manager who owns a book of accounts and also handles escalated support cases, because in a business of that size the person who sold the contract is the person the customer calls. She needs Sales Enterprise for her pipeline, and Customer Service Enterprise to work cases properly rather than just read them.
The naive purchase is two full licenses. The correct purchase is one Sales Enterprise base plus one Customer Service Enterprise attach, at a fraction of the cost, with identical capabilities. If four people share that dual role, the difference repeats four times, every month.
Why so many businesses miss it
There is no error message for overpaying. Buy two full licenses for one person and everything works and everything is compliant. The only signal is the invoice, where the line items look reasonable. Attach pricing also depends on buying the specific attach product in the right order, which rarely happens when two applications are bought months apart or for two different projects.
Team Members: what it genuinely covers
Team Members is the license people reach for when a full seat feels excessive, and the one most often bought for someone who cannot use it for the job they were hired to do. It is a deliberately constrained license, not a discount edition of a full one.
Per the licensing guide and Microsoft's Team Members overview, it grants a named user, for their own use and not on behalf of others:
- Read access across all Dynamics 365 application data
- Create, read, update, and delete on contacts, activities, and notes
- Updating their own employee information
- Recording time, materials, and expenses
- Approving time, expenses, materials, and vendor invoices
- User reporting and dashboards
- Participating as a consumer of the service, such as responding to surveys
Access runs through lightweight apps: Sales Team Member, Customer Service Team Member, and Project Operations Team Member, with up to 15 additional tables customized for them. The phrase "not on behalf of others" does a lot of work: the license does not grant a manager the right to perform these actions for direct reports.
Where it stops
On sales. A Team Members user can read leads and opportunities linked to accounts. They cannot create or update leads, opportunities, or accounts. Anyone whose job includes working leads needs a Sales license.
On service. They can create, update, and delete their own case, as an employee raising an internal request, and read knowledge base articles. They cannot work as an agent on other people's cases: no create or update on the general case table, no entitlements, no service level agreements, and no routing. Anyone answering customer tickets needs a Customer Service license.
On field work. They can create work orders for employee self-service and internally on behalf of customers, but cannot resolve or close them.
Where Team Members genuinely fits: project resources submitting time and expenses, approvers signing off timesheets and vendor invoices, employees updating their own records, and executives reading dashboards. In Project Operations, Microsoft names the timesheet roles as Team Members territory and the project manager, resource manager, account manager, and project accounting roles as full-user work.
Device licensing and shared workstations
Device licensing saves money in one scenario and costs money everywhere else.
A device license covers a dedicated shared machine rather than a named person, and any number of users can work through it. Microsoft offers Sales Device, Customer Service Device, and Field Service Device licenses, each carrying the same rights as the equivalent Enterprise user license, limited to that device. All three support shared logins, such as a counter workstation with one credential, at the cost of being unable to track individual usage. Project Operations has no equivalent; the Operations Device license covers only point-of-sale, warehouse, production floor, and store manager devices.
Device licensing only pays when several people who each need full capability share one machine and never need access elsewhere. Device licenses also sit outside the base and attach structure, which is built on user licenses.
Dataverse, storage, and the capacity you did not plan for
Storage is a common source of an unexpected invoice, because the entitlement arrives quietly and the overage does not.
Your subscription includes three separate Dataverse pools: database capacity for records, file capacity for attachments, and log capacity for auditing. Capacity arrives in two layers.
First, a per-tenant default, unlocked by your first base license for a product. This does not stack, and a second base license does not double it. Per the June 2026 guide, Sales Enterprise, Customer Service Enterprise, and Field Service each carry 30 GB of database, 40 GB of file, and 2 GB of log capacity per tenant. Sales Premium carries 45 GB and 60 GB. Project Operations carries 90 GB and 80 GB.
Second, a per-license accrual on top. Sales Enterprise, Customer Service Enterprise, and Field Service accrue 250 MB of database and 2 GB of file per user license. Sales Premium accrues 500 MB and 2 GB. Project Operations accrues 5 GB of each.
Three consequences follow. The Professional tiers accrue nothing, so a large Professional deployment gets the same 30 GB as a small one. Attach licenses accrue nothing either, so growing headcount through attach grows your data without growing your allowance. And log capacity never accrues, so auditing fills first.
Exceeding any pool triggers an add-on purchase, sold in 1 GB increments and pooled at the tenant level. Microsoft's Dataverse capacity documentation shows current consumption, worth checking before a data migration.
Where Power Apps and Power Automate licensing starts
This is an expensive accidental purchase, because the line is invisible until someone audits it.
Your Dynamics 365 licenses include limited Power Apps and Power Automate rights so you can customize and extend what you bought. The Power Platform Licensing Guide states the boundary precisely: use of these included capabilities must be only within the context of and in the same environment as the licensed Dynamics 365 application.
Included: a flow that triggers on a Dynamics 365 record and reads or writes data the application already has rights to, or a customization that extends a Dynamics 365 form, table, or process. Not included: a flow with nothing to do with the application, such as one moving data between two unrelated systems on a schedule. That needs a full Power Automate license regardless of who built it.
The subtler version involves custom applications on the same data. A Power Apps user may read, create, update, or delete any non-restricted Dataverse table with a Power Apps license alone. But Microsoft designates a set of restricted tables belonging to the Dynamics 365 applications, and any user who creates, updates, or deletes rows in those must hold the corresponding Dynamics 365 license (full list).
That is the trap. A business builds a lightweight custom app so warehouse or field staff can update a couple of fields, reasoning that a full CRM license would be excessive. If those fields live on a restricted table, every one of those users needs a Dynamics 365 license anyway.
Two further points. Dynamics 365 Professional licenses carry no Power Apps or Power Pages use rights at all. And all Power Apps and Power Automate usage counts against the Power Platform request limits your licenses provide, with overage charges possible.
Portals for customer-facing self-service
External users do not need Dynamics 365 user licenses, but they may not access the interfaces of Sales, Customer Service, Field Service, or Project Operations. A portal is the supported route.
That is Power Pages, licensed separately on two monthly meters: authenticated users per website, meaning people who sign in, and anonymous users per website. Capacity is assigned to the environment (pricing).
Be careful who counts as external. Microsoft's definition excludes employees, contractors, vendors, agents, and affiliates performing business processes on your behalf. Contractors working more than 30 hours a week on average, or onsite every working day, are internal users and need licenses.
Production and sandbox environments
Production environments run the live business. Non-production environments cover user acceptance testing, sandboxes, and testing, and may not process live or real-time data in connection with ongoing business operations. A sandbox is not a cheap second production system.
For the Dataverse-based applications, environments draw on your tenant's Dataverse capacity rather than arriving as a fixed count, so every sandbox consumes capacity from the pool the live system uses. Project Operations includes one production environment and one sandbox, with further tiers as add-ons.
Buying: term, seat changes, minimums, and channel
Term length and billing frequency. Dynamics 365 is sold on monthly, annual, and multi-year commitments through every channel, and the billing frequency (invoiced monthly, or once up front for the year) is a separate setting from the term. Commit annually and pay annually. The annual term carries a lower per-seat rate, paying up front turns 12 invoices and 12 approvals into one of each, and it fixes your rate for the term.
Mid-term seat changes. Adding seats mid-term is straightforward. Removing them is not. License-based subscriptions carry a self-service cancellation and reduction window of seven calendar days from purchase, and it does not reopen until the subscription renews. An annual commitment therefore locks your seat count for the year, which is the one real cost of committing annually. Size that commitment to the headcount you are confident about and add seats above the line as you need them, rather than paying the month-to-month premium across the whole team (cancellation policy).
Minimum seat counts. Some products require a minimum purchase to activate a subscription. Project Operations is licensed per user with a minimum number of users required, and Microsoft Relationship Sales carries a ten-seat minimum. Sales and Customer Service carry no published minimum in the current guide, and the Product Terms is the authority.
Channel. You can buy direct from Microsoft online, through Microsoft's sales team, or through a partner in the Cloud Solution Provider program, all at the same subscription lengths. A partner puts one point of accountability across licensing, implementation, and support, and makes the base and attach sequencing someone's job.
Two release waves a year
Updates are not optional, and treating them as optional is how a customization breaks on a Tuesday morning.
Wave 1 covers features releasing April through September, generally available from April 1. Wave 2 covers October through March, generally available from October 1 (release plans). For Sales, Customer Service, and Field Service, every environment receives the new version automatically through a staged rollout. You can shift timing within limits by managing your maintenance window, but you cannot decline the update.
You can test first: early access lets you validate a wave in a sandbox, and for any business with meaningful customization those two windows belong on the calendar (release schedule).
Step-up paths and promotional pricing
Tier changes are supported. The licensing guide describes stepping up from Sales Enterprise to Sales Premium as the route to uncapped Sales Insights capacity, and the same applies between Professional and Enterprise, subject to the rule that the two cannot share an environment.
Microsoft has historically run migration and promotional offers for customers moving from older Dynamics products or competing systems. These change frequently, are not published in the licensing guide, and were not listed on the Sales pricing page at the time of writing. Ask what is current rather than assuming last year's offer still exists.
The gotchas, collected
- Two full licenses for one person. A second application should almost always be an attach license.
- Buying in the wrong order. The higher-priced application must be the base, so Project Operations comes before Sales Enterprise.
- Team Members for people who work leads or cases. It does not permit working the pipeline, acting as a support agent, or acting for a team.
- Professional-tier storage does not grow, attach licenses add none, and nothing adds log capacity.
- A custom app that writes to restricted tables. Every user of it needs a Dynamics 365 license anyway.
- A flow that leaves the application. Unrelated automation needs full Power Automate licensing.
- Professional tiers have no Power Apps or Power Pages rights, and cannot share an environment with Enterprise users.
- Long-term or onsite contractors treated as external users. They are internal and need licenses.
- Size the annual commitment to your trough, not your peak. Seats are easy to add mid-term and hard to remove.
- Sandboxes drawing on production capacity. Test environments share the live system's pool.
Where to start
Nearly all of this resolves into one exercise: list every person who will touch the system, the specific actions each will perform, and which license permits those actions. Whether they create leads or only read them. Whether they resolve cases or only raise their own.
If you are sizing a Dynamics 365 purchase, or you suspect an existing estate is not structured well, bring us your user list and your current license bill. We will map each person to the license their work requires and show you where the two differ. If your current setup is already correct, that is a short conversation and a useful one.