I have sat in more Dynamics 365 licensing conversations than I care to remember. A business wants to implement the platform, their Microsoft reseller sends over a quote, and suddenly everyone is staring at a spreadsheet of licence names that reads like a legal document. Sales Enterprise. Customer Service Professional. Team Member. Power Apps per app. Power Automate per flow. It is chaos, and I suspect that is not entirely accidental.
Microsoft makes this complicated by design. The licensing model is structured to maximise revenue rather than to make your life easy. But once you understand the basic shape of it, things become a lot clearer and you stop paying for things you do not actually need.
Understanding what Dynamics 365 actually is
The first thing to get straight is that Dynamics 365 is not a single product. It is a family of business applications, each sold and licensed separately. Sales, Customer Service, Field Service, Finance, Supply Chain Management, Project Operations, and a few others. Each has its own licence, its own price point, and its own feature set.
This matters because organisations often come into an implementation thinking they need "Dynamics 365" without specifying which part. Getting that wrong early means paying for the wrong licences, or realising six months in that you need a completely different application. The first conversation any good implementation partner should have with you is about which application or combination of applications actually fits what you are trying to do.
Full licences versus Team Member licences
Within each Dynamics 365 application, there are broadly two kinds of user licences. Full application licences and Team Member licences. This is where a lot of organisations get into serious trouble.
The Team Member licence looks attractive on paper. It costs a fraction of a full licence. The problem is that it barely lets you do anything useful. Team Member licences give users read access to data, the ability to run reports, and a limited ability to update their own records. They cannot create records across most entities, cannot run meaningful workflows, and cannot access the full functionality of any application.
I have seen organisations licence twenty people on Team Member to save money, then wonder why adoption is terrible and the system is sitting unused. You saved on licences and wasted it on a system nobody can work in properly. That is a genuinely false economy.
Team Member licences do have a legitimate place. People who genuinely only need to view records occasionally. Employees outside the core team who need occasional read access. But be honest with yourself about whether that actually describes your users before you commit to it. Most of the time, if someone is supposed to work in the system, they need a full licence.
Enterprise versus Professional
Within the full licence tier, most Dynamics 365 applications come in two flavours. Enterprise and Professional. Enterprise gives you everything. Professional strips out some of the more advanced features and costs meaningfully less.
For a lot of small and mid market businesses, Professional is entirely sufficient. The features removed tend to be things like embedded intelligence, advanced configuration options, and high tier API limits. If you are not sure which you need, get a proper feature comparison done against your actual requirements. I have watched businesses pay the Enterprise premium for capabilities they never once used in three years of operation.
Your reseller will often default to quoting Enterprise. It is not necessarily because Enterprise is the right fit. Push back and ask them to justify it against your specific use case.
The base and attach model
Here is something that catches people out when users need more than one Dynamics 365 application. Microsoft uses what they call a base and attach pricing model, and understanding it can save you a significant amount of money.
The first Dynamics 365 application you licence is at full price. That is your base licence. If the same user needs a second Dynamics 365 application, you get it at a heavily reduced attach price. In practice this can be twenty to thirty percent of the base price for that second application.
So if a user needs both Sales and Customer Service functionality, you licence one at full price and the second at the attach rate. Resellers do not always present this clearly. The full price option is better for their margin, so you sometimes have to ask specifically about attach pricing rather than waiting for it to appear on a quote.
What your Dynamics 365 licence already includes for Power Platform
Every Dynamics 365 application licence includes some Power Platform capability by default. Specifically, the right to build and run Power Apps and Power Automate flows that connect to your Dynamics 365 data. A lot of organisations do not realise this and end up buying separate Power Platform licences they did not need.
Where it gets more complicated is when you want Power Apps that connect to data sources outside Dynamics 365, or when Power Automate needs to run at scale with premium connectors. That is when additional licences come into the picture.
Map out what you are actually trying to build before buying anything extra. I have helped businesses unpick situations where they were paying for Power Apps per user licences across the whole organisation when the Dynamics 365 licences already in place covered the use case perfectly well. It is worth having someone check before you spend.
Business Central is a completely different product
Something that trips people up regularly is the relationship between Dynamics 365 Business Central and the rest of the Dynamics 365 family. They are fundamentally different products aimed at different markets, with entirely different licensing models.
Business Central is Microsoft's ERP product for small to medium businesses. It has its own licensing structure, its own pricing tiers, and mostly its own ecosystem. If you are evaluating Business Central, treat it as a completely separate conversation from Sales, Customer Service, or any of the other enterprise applications. They can integrate with each other, but they are not the same product and the licensing works nothing like the rest of the suite.
Questions worth asking before you sign anything
Before you commit to any Dynamics 365 licence agreement, these are the questions you should be able to get a clear answer to. If your partner cannot answer them confidently, that tells you something useful.
What is the minimum licence each user type actually needs? Do not assume everyone needs the same level. Map roles to system usage before assigning licences.
Is Professional tier genuinely sufficient for your use case, or does your specific workflow require Enterprise features? Get the comparison against your actual requirements rather than a generic product brochure.
What Power Platform capability is already included in the Dynamics 365 licences you are buying? You may have more than you think without spending anything extra.
What happens to pricing at renewal? Microsoft licence costs change over time. Understanding your renewal position before you sign is far smarter than dealing with a nasty surprise two years in.
Are there any non profit or charity pricing options available to your organisation? Microsoft has meaningful programmes in this area that partners do not always flag upfront.
Getting the licence mix right
The right licence mix depends entirely on what you are building and who is using it. There is no universal answer. What I can tell you from seventeen years of working in this space is that most organisations over licence in some areas and under licence in others simultaneously. Too many expensive licences for users who do not need full access, and too many cheap Team Member licences for people who genuinely need to work in the system every day.
Getting this right before you go into implementation is significantly cheaper than fixing it after the fact. If you are planning a Dynamics 365 project and want to make sure you are not walking into a licensing mess, that kind of advisory conversation is something I do as part of my Dynamics 365 consulting work. It is the sort of thing that pays for itself quickly.
And if you want to understand the full cost picture beyond just licences, implementation fees, support, and what people do not tell you until after you have signed, I have covered all of that in my guide to what a Dynamics 365 implementation actually costs.
