Dynamics 365 Licensing and Procurement: Partner vs. Direct, and How Partner Margins Work
A decision guide for the person who has to sign: the buying channels for Dynamics 365 and Power Platform, how partner margins actually work in the CSP model, what that margin funds, where it creates a conflict of interest, and the total cost of ownership underneath the seat price.
Buying Dynamics 365 and Power Platform through a Microsoft partner usually costs the same as buying direct, because the partner margin is funded by the discount Microsoft gives the partner rather than added to your invoice. In the Cloud Solution Provider (CSP) program, the partner buys your subscriptions at a partner price, sells them to you at the price you agree, and keeps the gap. That single mechanic explains why partner pricing is negotiable at all, why some partners have no reason to rightsize your seats, and why the cheapest quote is not always the lowest total cost of ownership. This guide covers the buying channels, what the margin does and does not pay for, and what to ask before you sign. Solzet does not resell licenses and holds no margin on any customer subscriptions, so nothing below is written to defend one.
A note on numbers. Microsoft sets partner program rates in agreements that partners sign and are not free to publish, and it revises those rates, the incentive programs, and the program names regularly. This guide therefore explains the mechanics and the levers rather than quoting a margin percentage, because a fixed number would be a snapshot of a program that has since moved. Confirm anything commercial against your own Microsoft agreement, your partner quote, and the current Microsoft licensing guide before you commit.
The three ways a Dynamics 365 subscription reaches you
Before the price conversation there is a channel conversation, and most buyers skip it. These are the three routes, described by who invoices you and what you give up. None of them is the right answer for everyone, and for a team with Microsoft administration already in house, buying direct is a perfectly good decision.
Direct from Microsoft
You buy the subscription yourself in the Microsoft admin center, or through a Microsoft seller if the deal is large enough to attract one. You own the tenant, the subscription, and the billing relationship, and you administer license assignment yourself.
- Who invoices you
- Microsoft invoices you, in the currency and on the terms Microsoft sets.
- Best for
- Teams with in house Microsoft 365 administration who already know the license mix they want, and organizations that want no intermediary in the commercial relationship at all.
- What to watch
- There is nobody between you and the SKU list. Self service pricing is list pricing, support for the application sits with Microsoft support rather than a named person, and nobody is contractually motivated to notice that half your seats are the wrong type.
Through a Cloud Solution Provider partner
A partner in the CSP program buys the subscriptions from Microsoft and resells them to you. The partner is the seller of record: it provisions the subscriptions against your tenant, sets your price, and carries a support obligation to you as a condition of the program.
- Who invoices you
- The partner invoices you, which is often the reason to use one. A partner in your region can usually invoice locally, in local currency, with local tax presented the way your finance team expects, and on payment terms Microsoft would not offer you.
- Best for
- Organizations that want one commercial contact, local invoicing, or consolidated billing across Microsoft 365, Dynamics 365, Power Platform and Azure, and smaller buyers who will never get Microsoft attention on their own.
- What to watch
- The partner sets your price, so the discount you get depends entirely on how much of its margin it is willing to give back. And its revenue grows with your seat count, which is the conflict of interest this guide keeps coming back to.
On an enterprise volume agreement
Larger organizations buy under a negotiated volume agreement covering the whole Microsoft estate, usually placed through a licensing solution provider rather than bought online. Pricing, term, and true up mechanics are negotiated across the entire relationship rather than per app.
- Who invoices you
- Your licensing solution provider or Microsoft, depending on the agreement vehicle, typically annually against a committed volume.
- Best for
- Organizations with a large Microsoft estate and a genuine procurement function, where Dynamics 365 is one line among many and the leverage comes from the total commitment.
- What to watch
- Commitment is the price of the discount. Multi year commitments made against a headcount forecast are exactly where the over licensing this guide describes gets locked in for years rather than for one term.
How Dynamics 365 partner margins actually work
This is the part nobody explains to you, usually because the person explaining it earns it. There is nothing improper about partner margin, but you cannot weigh licensing advice without knowing how the person giving it gets paid. Six mechanics, none of which require a percentage to be useful.
The margin lives in the gap between the partner price and your price
Microsoft publishes an estimated retail price for each Dynamics 365 and Power Platform subscription and sells to CSP partners below it. The partner then sets what you pay. If it sells at the retail price, you pay exactly what you would have paid Microsoft directly and the partner keeps the whole discount as margin. If it sells below retail, it is giving part of that discount back to win or keep your business. This is why a partner quote can be lower than Microsoft list pricing and why the answer to how much a partner earns on your seats is always a range rather than a rate.
Your price is set by the partner, which means it is negotiable
When you buy direct at self service, list price is list price and there is nothing to discuss. When you buy through a partner, the price on the quote is a decision that partner made, so it is a conversation. The lever is not asking Microsoft for a discount, it is asking the partner how much of its margin it will trade for a longer term, a larger seat count, a consolidated estate, or an implementation contract signed alongside. Ask for the license line and the services line to be quoted separately, so you can see which one is really being discounted.
Margin is not the only money, and the rest never appears on your invoice
Beyond the buy and sell gap, Microsoft pays partners incentives and rebates tied to program status, to what you buy, and in places to whether your users actually use it. Those are earned after the fact, paid by Microsoft, and invisible to you. They are not a scandal, they are how the channel is funded, but they explain behaviour that otherwise looks irrational: why a partner pushes a particular app, a particular edition, or an annual commitment over a monthly one. The exact programs change names and rules regularly, so the useful question is not what they are called but simply whether your partner earns anything from Microsoft on your account beyond the price difference, and to say so plainly.
The partner of record and the partner that invoices you can be different companies
A partner can be recorded against your Dynamics 365 and Power Platform subscriptions as the partner of record and earn Microsoft incentives from that association without being the company that sells you the licenses. This matters in two directions. It means an implementation partner can be rewarded for your success without taking a cent of license margin, and it means the firm attached to your tenant may not be the firm you think you chose. The claim mechanism has been renamed and rebuilt several times, so ask both questions directly: who invoices us, and who is recorded as our partner of record today.
What the margin legitimately pays for
A CSP partner carries real obligations. It provisions and manages your subscriptions, it handles billing and can carry payment terms and local currency risk, and it is the first line of support for the products it sells you, escalating to Microsoft on your behalf. Good ones also do license management as an ongoing service: watching assignment against usage, flagging seats that should change type, and warning you before a renewal rather than after. That work has a cost, and margin is a perfectly reasonable way to fund it. The test is not whether the partner earns margin, it is whether you can name what you receive for it.
Where the margin creates a conflict of interest
A partner whose license revenue scales with your seat count earns more when you are over licensed and less when you are rightsized, so a recurring license review is work that costs it money to do well. Put the implementation contract on top of the same signature and the tension doubles: the same firm now benefits from more seats and from more build days, and it is the firm advising you on how many of each you need. Most partners handle this honestly. You still want it named out loud rather than assumed away, and you want the advice separable from the transaction if the numbers are large.
The practical takeaway is not to avoid partners. It is to know that your price was a decision somebody made rather than a fixed fact, and to ask for it accordingly.
Partner vs. direct, line by line
Score these rows against how your organization actually operates rather than against which column looks better. Payment terms and local invoicing decide this question far more often than price does.
| What you are deciding | Buying direct from Microsoft | Buying through a CSP partner |
|---|---|---|
| Who invoices you | Microsoft, in the currency and on the terms Microsoft sets. | The partner, often locally, in local currency, with local tax presented the way your finance team expects. |
| Price on day one | List price at self service. Negotiated only if the deal is large enough for a Microsoft seller to engage. | Set by the partner out of its margin, so it is negotiable at any size, including small ones. |
| Payment terms | Microsoft terms, typically card or invoice on Microsoft cycles. | Partner terms. This is frequently the deciding factor for organizations that cannot pay a foreign card charge monthly. |
| First line of support | Microsoft support, through the standard channels, with no named person. | The partner, contractually, escalating to Microsoft on your behalf. Quality varies enormously, so make it a scored question. |
| Who administers licenses | You do, in your own admin center, which is fine if you have that skill in house. | The partner can provision and reassign, which helps if you do not, and which you should still be able to audit yourself. |
| Consolidating the wider Microsoft estate | Separate management for each product you buy, on Microsoft cycles. | One invoice and one renewal conversation across Microsoft 365, Dynamics 365, Power Platform and Azure, if that is worth something to you. |
| Incentive to rightsize you | None either way. Nobody is watching your assignment data, so the drift is entirely yours to catch. | Structurally negative, because fewer seats is less revenue, unless the partner has committed to a review in writing. |
| Changing quantities mid term | Governed by the New Commerce Experience term rules you agreed to, handled by you. | Same rules, handled by the partner. The rules are Microsoft rules, so a partner who implies otherwise is worth a second look. |
| Who to call when the system is down | Microsoft support for the platform. Nobody at all for your configuration, integrations, or customizations. | The partner, if it is also your implementation partner. If your seller and your builder are different firms, know in advance which one owns which failure. |
One row is worth reading twice. Nobody in either column has a commercial reason to reduce your seat count, which is why the license review has to be a named responsibility held by somebody rather than an assumption.
Total cost of ownership: the eight lines, not the one
Procurement negotiates the subscription because it is the line with a price on it. For a real Dynamics 365 deployment it is rarely the largest number in year one. Size all eight of these before you compare offers, because a discount on line one does not survive contact with lines four through seven.
| Cost line | How it is charged | What to know |
|---|---|---|
| Dynamics 365 subscriptions | Per user, per month, by app and edition, for the length of the term you commit to. | The line everyone negotiates. Get the seat mix right before you get the price right, because a ten percent discount on the wrong license type is worse than list price on the right one. |
| Power Platform licensing alongside it | Per user or per app plans for Power Apps, plus Power Automate and Power Pages where the workload sits outside a Dynamics 365 app. | Decide deliberately whether a given workload needs a Dynamics 365 seat at all. Getting this boundary wrong is one of the more expensive quiet mistakes in a first year budget. |
| Dataverse capacity beyond the entitlement | Per GB, per month, for database, file, and log capacity above what your tenant and your seats accrue. | Small at the start and easy to grow into. Attachments, audit logs, and a migration that brings twenty years of history are what move it. |
| Implementation | A one off project: discovery, configuration, data migration, integration, testing, go live and hypercare. | Routinely a multiple of the first year subscription cost for a real deployment. Quoted as effort at a day rate, and best fixed after a paid discovery rather than guessed before one. |
| Integration and custom development | Per interface and per custom component, whether plug-ins, Power Automate flows, or PCF controls where standard configuration will not do the job. | The line most often left out of a procurement business case, and the line most likely to be the reason the project is late. |
| Support and change after go live | Monthly, from a part time consultant up to a managed team, covering release wave updates, enhancements and fixes. | A platform nobody maintains decays quietly through two release waves a year. Budget it from the start rather than discovering it in month four. |
| Your own people | Internal time for discovery, decisions, data cleaning, user acceptance testing, training and adoption. | Never on any quote and never free. The projects that fail rarely fail on license price, they fail because nobody costed the internal time and it was not made available. |
| The cost of over licensing across the term | Seats assigned but unused, and full licenses held by people who need a narrower or lighter one, multiplied by every month of the term. | This is the number partner margin discussions usually distract from. It is normally larger than the discount being argued over. |
For published per user list prices on a worked example, including the arithmetic for a mixed team of full agents and light users, see the seat pricing table in our Dynamics 365 licensing cost and renewal negotiation guide. That page is the one to read if you already own Dynamics 365 and the renewal came back higher. This page is the one to read if you have not bought yet.
Eight questions to ask before you sign
Lift these straight into an email or an RFP. A good partner answers all eight without hesitation, and several will volunteer the answers before you ask. How a firm handles the fifth one tells you most.
1. Are you selling us these licenses yourself, or are we buying direct with you advising?
The first answer means the firm has a margin on your seats. The second means it does not. Neither is wrong, but you cannot weigh any subsequent advice without knowing which one you are in.
2. Who will be recorded as our partner of record on these subscriptions?
It is not always the firm invoicing you, and an association can be attached without a conversation. Ask, and ask again after go live, because it can change.
3. Will you quote the licenses and the services as separate line items?
A bundled number lets a discount on one hide a premium on the other. Separate lines let you compare the license price against buying direct and the day rate against another firm.
4. What exactly do we get for the margin, and is any of it in the contract?
Provisioning, billing, first line support, and a periodic license review are all reasonable answers. Verbal answers are not. Get the support response commitment and the review cadence written down.
5. Will you commit in writing to a license review before every renewal?
This is the single question that tells you most about a partner, because a genuine review costs the partner revenue. Willingness to sign up to it is the strongest signal you will get.
6. What happens to our subscriptions if we stop working with you?
Subscriptions can be transferred to another partner or to a direct relationship, and you want the process, the notice period, and the timing understood before you need it, not during a dispute.
7. Which of these seats could be a narrower or lighter license type?
A partner that answers this well before the sale is telling you it will answer it well at renewal. A partner that puts everyone on a full license by default has answered a different question.
8. What is the total first year cost including implementation, integration and support?
Sold as seat price alone, Dynamics 365 looks like a subscription decision. It is a project decision, and the subscription is usually not the largest number in year one.
Red flags in a Dynamics 365 licensing proposal
- •A single bundled number covering licenses, implementation and support, with no breakdown offered when you ask for one.
- •Everyone on the same full license type in the proposed seat mix, with no attach licenses and no lighter license for read mostly users, which usually means nobody mapped roles to licenses.
- •A multi year commitment pushed hard before any discovery has established what you actually need, when the term shape is presented as a discount rather than as a constraint on reducing seats later.
- •A discount that appears only when the implementation contract is signed at the same time, which is the license margin and the services margin being traded against each other in a way you cannot see.
- •A quote that includes an app or an add-on you did not ask about and cannot get a plain answer on why you need.
- •Reluctance to say who is recorded as your partner of record, or to put the support commitment in the contract.
- •Microsoft program rules described as if they were partner policy, particularly around mid term seat reductions, which are governed by the New Commerce Experience terms rather than by any partner.
- •No mention anywhere in the proposal of Dataverse capacity, integration work, or what happens after go live.
How to run the procurement, in order
The order is the whole point. Sizing comes before pricing and channel comes before negotiation, because a discount agreed against the wrong seat count is a discount on a mistake you then pay for every month of the term.
Establish what you need before you ask anyone what it costs
List the roles that will use the system and what each one genuinely does: full app users, users who need a second app, single app or process users, and read mostly users. That list is the seat mix. Doing this first is what stops the entire procurement anchoring on a number produced from a headcount rather than from a requirement, and it is the input every later step depends on.
Map each role to the narrowest license that still does the job
Put a target license type next to every role: a full license only where broad app use is real, an attach license where the same person needs a second qualifying app, an app scoped or per app plan for single process users, and a limited license for genuinely light users. Our renewal guide covers this mapping in detail. The output is a defensible seat count you can put in front of any seller.
Decide the channel deliberately, before you collect quotes
Choose whether you want to buy direct, through a CSP partner, or on a volume agreement, based on whether you need local invoicing, payment terms, consolidated billing, and a contractual first line of support, or whether you have that capability in house already. Deciding the channel first means the quotes you collect are comparable rather than three different shapes of proposal.
Ask every candidate partner the disclosure questions
Ask whether they are selling you the licenses or advising while you buy direct, who will be the partner of record, what the margin buys, and whether they will commit to a license review before each renewal. Ask for licenses and services on separate lines. The answers separate a firm that has thought about the conflict of interest from one that would rather you did not.
Price the total, not the seat
Build the first year and three year picture: subscriptions, Power Platform licensing, Dataverse capacity, implementation, integration, ongoing support and your own internal time. Then compare offers on that total. A partner charging list price on seats while delivering a cleaner implementation for fewer days is very often cheaper than the partner who discounted the seats.
Negotiate the term shape as carefully as the price
Under the New Commerce Experience, the term you commit to and the payment cadence affect both the rate and your ability to reduce seats mid term. A longer commitment made against an uncertain headcount is where over licensing gets locked in. Decide how much of the estate genuinely needs to be flexible and buy that portion accordingly, even at a higher unit price.
Write the review into the contract, then run it
Agree in the contract that assigned licenses will be reviewed against actual usage before every renewal, name who produces that analysis, and put a date on it. Then actually run it. Whether it is your partner, an independent advisor, or your own team, this single recurring habit reliably saves more than the discount most procurements spend their energy on.
If step one is where you are stuck, because nobody has yet established whether you need an implementation partner at all, our hire a consultant versus do it yourself decision guide is the question underneath this one. If you already have a system and want to know what it is really costing you before you renew anything, start with a health check and technical audit.
Where Solzet sits, and the bias we do have
You should apply this whole guide to us as well, so here is the disclosure we have been asking you to demand from everyone else.
We do not resell licenses
Solzet is a Dynamics 365 Customer Engagement and Power Platform consultancy in Yerevan, Armenia. We are not a Cloud Solution Provider and we hold no margin on any customer subscriptions. When we tell you a role can sit on a lighter license, or that a workload belongs on Power Platform rather than on a Dynamics 365 seat, or that you should buy direct, none of those conclusions cost us anything or earn us anything.
The bias we do have, stated plainly
We are paid for delivery: implementation, custom development, migration, project rescue and support. So our commercial interest is in build days, not in seats. Judge our licensing advice with that in mind, exactly as you would weigh advice from a reseller against the margin it earns. The practical consequence is the one worth knowing: we have no reason to inflate a seat count and every reason to be honest about a build, which is the opposite bias from the one most licensing advice carries.
What we actually do at the procurement stage
We size the seat mix from the roles and the process rather than from headcount, we tell you where a workload should sit to avoid a heavier license, we review a partner proposal against what the implementation genuinely requires, and we scope the build so the number in your business case is a number rather than a hope. If you want a CSP partner for local invoicing and payment terms, we will say so, and we will work alongside whoever you pick.
Directly or behind another partner
We work on straightforward B2B contracts, either directly for the organization using Dynamics 365 or on a white-label basis for another Microsoft partner delivering to its own client. Partners who do hold the license relationship use us for the engineering, which is a large part of our work and another reason we have no interest in competing for the license margin on your seats.
More on how we work and who we are is on the Dynamics 365 partner in Armenia page, and the delivery itself is described under Dynamics 365 consulting and white-label subcontracting for Microsoft partners.
Frequently Asked Questions
How do Dynamics 365 partner margins work?
In the Cloud Solution Provider program, the partner buys your Dynamics 365 subscriptions from Microsoft at a partner price that sits below the published estimated retail price, then sells them to you at a price it sets. The difference is its margin. If it sells at retail, you pay what you would have paid Microsoft directly and the partner keeps the whole discount. If it sells below retail, it is handing part of that discount back to win or keep the account. On top of the buy and sell gap, Microsoft pays partners incentives and rebates tied to program status and to what you buy and use, which are paid after the fact and never appear on your invoice. Microsoft sets these rates in partner agreements that are not public and revises them regularly, so treat any fixed percentage you read as a snapshot rather than a rule.
Is it cheaper to buy Dynamics 365 direct from Microsoft or through a partner?
Usually it is the same or cheaper through a partner, which surprises most buyers. The partner margin is funded by the discount Microsoft gives the partner, not added on top of list price, so a partner can sell at list and earn the full gap, or sell below list and earn less. Buying direct at self service means paying list with nothing to negotiate unless the deal is large enough for a Microsoft seller to engage. The real cost difference is rarely the seat price anyway: it is the seat mix, the implementation, and whether anyone reviews your licenses before each renewal. A partner charging list price while sizing your licenses correctly costs far less over three years than a discounted quote that puts everyone on a full license.
What is the CSP model in Microsoft licensing?
The Cloud Solution Provider program is the channel through which Microsoft partners buy cloud subscriptions, including Dynamics 365 and Power Platform, and resell them to customers. The partner becomes the seller of record: it provisions subscriptions against your tenant, sets your price, invoices you directly, and carries a contractual obligation to be your first line of support, escalating to Microsoft on your behalf. Within CSP, the New Commerce Experience governs term lengths, payment cadence, and the rules for changing seat quantities mid term, and those rules are Microsoft rules rather than partner policy. The practical benefits of buying this way are local invoicing, local currency, payment terms Microsoft would not offer directly, consolidated billing across your Microsoft estate, and a named commercial contact.
Does buying through a Microsoft partner cost more than buying direct?
No, not by default. The partner margin comes out of the discount Microsoft gives the partner, so the same subscription bought through a partner at retail price costs you the same as buying it from Microsoft. What varies is what the partner chooses to charge, which is why a partner quote is negotiable in a way that self service list pricing is not. Where a partner arrangement can genuinely cost you more is indirectly: if the seat mix is wrong, if a multi year commitment is signed before anyone established what you need, or if nobody reviews assigned licenses against actual usage between renewals. Those cost far more over a term than any margin argument.
What does a Dynamics 365 partner actually do for its licensing margin?
A CSP partner provisions and manages your subscriptions, handles billing and can carry local currency and payment terms, and is contractually your first line of support for what it sells you, escalating to Microsoft when needed. The better ones also run license management as an ongoing service: watching assigned licenses against real usage, flagging seats that should change type, and raising the renewal conversation before the renewal rather than after it. That work has a genuine cost and margin is a reasonable way to fund it. The test is not whether a partner earns margin, it is whether you can name what you receive for it and point to where it is written down.
Is there a conflict of interest when my implementation partner also sells my licenses?
There is a structural one, and it is worth naming rather than assuming away. A partner whose license revenue scales with your seat count earns more when you are over licensed, so a thorough license review is work that costs it money. Add the implementation contract to the same signature and the same firm benefits from more seats and more build days while advising you on how many of each you need. Most partners handle this honestly and plenty of them will rightsize you without being asked. You still want the conflict acknowledged, the license and services lines quoted separately, and a review commitment in the contract. If the numbers are large, consider separating the advice from the transaction entirely.
Who is our partner of record, and does it have to be the partner that invoices us?
It does not. A partner can be recorded against your Dynamics 365 and Power Platform subscriptions as the partner of record and earn Microsoft incentives from that association without selling you a single license, and the firm that invoices you is a separate question. This cuts both ways: it means an implementation partner can be rewarded for your success without taking license margin, and it means the firm attached to your tenant may not be the one you think you appointed. The claim mechanism has been renamed and rebuilt several times over the years, so rather than tracking program names, ask your partner directly who is recorded today and ask again after go live.
What is the real total cost of ownership of Dynamics 365 beyond the license price?
Budget eight lines, not one. Dynamics 365 subscriptions by app and edition, Power Platform licensing where a workload sits outside a Dynamics 365 app, Dataverse capacity above your entitlement, the one off implementation covering discovery through hypercare, integration and custom development where standard configuration will not do the job, ongoing support and change after go live, your own internal time for decisions, data cleaning, testing and adoption, and the standing cost of any seats that are assigned but unused. For a real deployment the implementation is routinely a multiple of the first year subscription cost, and internal time is never on any quote and never free. This is why negotiating the seat price hard while ignoring the other seven lines is the most common procurement mistake we see.
What should we ask a Dynamics 365 partner before signing a licensing agreement?
Ask whether they are selling you the licenses or advising while you buy direct, because that determines whether they hold a margin on your seats. Ask who will be recorded as your partner of record. Ask for licenses and services to be quoted as separate line items so a discount on one cannot hide a premium on the other. Ask what the margin buys and which parts of that are in the contract, particularly the support commitment. Ask whether they will commit in writing to a license review before every renewal, which is the question that reveals the most because a genuine review costs them revenue. Ask what happens to your subscriptions if you part ways. And ask which of the proposed seats could be a narrower or lighter license type.
Can Solzet advise on licensing if you do not sell licenses?
Yes, and not selling them is the point. Solzet is a Dynamics 365 Customer Engagement and Power Platform consultancy in Yerevan, Armenia. We are not a Cloud Solution Provider and hold no margin on any customer subscriptions, so we size the seat mix from roles and process, tell you where a workload belongs to avoid a heavier license, and review a partner proposal against what the implementation genuinely requires. Our bias, stated plainly, is that we are paid for delivery days rather than seats, so weigh our advice accordingly. We work directly for organizations and on a white-label basis for other Microsoft partners, including partners who hold the license relationship themselves.
Want a second opinion on a quote from someone with no margin in it?
Send us the proposal and the roles it is meant to cover. We will size the seat mix from what those people actually do, tell you where a workload belongs so it does not need a heavier license, and say plainly whether the build being quoted matches the requirement. We do not resell licenses, so the answer costs us nothing either way. Directly for your organization, or on a white-label basis behind your own partner.