Dynamics 365 vs Salesforce pricing: what each CRM costs over a three year term.

Dynamics 365 lists lower than Salesforce at the main enterprise tier, but the seat price rarely decides the bill. Platform charges, add on clouds, ramp clauses and your Microsoft agreement do, so compare three year totals.

Both products price per user per month, and at list the Dynamics 365 seat is the cheaper one. The seat rate rarely settles the contract, though. Platform charges, add on clouds, ramped seat commitments and your existing Microsoft agreement decide the bill, and those are the lines where CRM budgets go wrong.

The Dynamics 365 pricing page and the Salesforce editions pricing page publish the seat rates. Neither shows the bundling around the seat.

How do Dynamics 365 and Salesforce list prices compare in 2026?

At list, Dynamics 365 Sales Enterprise at $105 per user per month sits well below Salesforce Core at $195, both billed annually. Enterprise buyers rarely pay list on either side, so compare quoted net rates. Core also bundles collaboration, analytics and a premium support plan, so part of that gap pays for items outside the CRM seat.

Dynamics 365 editions

Dynamics 365 splits into Sales, Customer Service and the broader apps such as Field Service, Finance and Supply Chain Management. Each user needs either a full license for the app or the cross app Team Members license for light use. The Microsoft Dynamics 365 documentation sets out the use rights.

One licensing rule shapes the bill. When one user needs several apps, the first license must be the highest priced one (the base), and each further app is bought as a cheaper attach license. That attach pricing is why a second Dynamics app costs far less per user than the first.

Salesforce editions

Salesforce splits into Sales Cloud and Service Cloud. For years the editions were Professional, Enterprise and Unlimited, and existing contracts still carry those names. Per the Salesforce site, most enterprise features sit at Enterprise and above, which is where a fair comparison with Dynamics happens.

On September 3, 2026 Salesforce published new Core, Advanced and Max editions. They bundle Slack, Tableau Next, the Premier Success Plan and an annual pool of Flex Credits per org (500,000 in Core, 1 million in Advanced), and existing customers keep legacy edition pricing. Expect a renewal proposal that pushes the new editions.

• Dynamics full user. Comparable to Salesforce Enterprise on core CRM: accounts, contacts, opportunities, cases, workflow and reporting.
• Dynamics Team Members. Low cost light access with narrow rights, meant for reading data and designated tasks such as updating contacts or entering expenses.
• Salesforce Enterprise. The common enterprise baseline edition on existing contracts, and the fair comparison point for a Dynamics full user.

Why does bundling decide the real cost?

Bundling decides the cost because both vendors build the bill from layers stacked on the core seat, and the layers differ far more than the seats do. The seat rate is the visible part. The table below shows where the two diverge.

Platform and add on fees on the Salesforce side

Salesforce adds platform fees, API limits and separately licensed clouds for marketing, CPQ and data. Over three years they become a large share of the bill. Several of the charges are priced as a percentage of your net spend, so they grow every time the seat line grows.

• Sandboxes. A Full Copy sandbox lists at 30 percent of net spend, Partial Copy at 20 percent and Developer Pro at 5 percent. Enterprise Edition includes Developer sandboxes and one Partial Copy, so a Full Copy for realistic testing is an extra charge; Unlimited includes one.
• Shield. The security bundle lists at 30 percent of net spend. Bought separately, components run from 10 percent (Event Monitoring) to 20 percent (Platform Encryption).
• Premier Success. 30 percent of net license fees, bundled with Unlimited and the new editions.
• API calls. Enterprise orgs get 100,000 calls per 24 hours plus 1,000 per Salesforce license (5,000 on Unlimited). Integration heavy teams outgrow that and buy more.
• Data storage. 10 GB per org plus 20 MB per user on Enterprise. Large case or activity volumes push you into paid storage.

What does your Microsoft agreement change?

Dynamics 365 draws on your existing Microsoft agreement, identity in Entra ID and the Power Platform. If you already run a Microsoft enterprise agreement, the incremental cost of Dynamics can be lower than its list rate suggests. It is negotiated inside a relationship worth far more to Microsoft than the CRM line alone.

Dynamics has its own layers. Several Enterprise licenses accrue 250 MB of Dataverse database capacity per user, and Team Members accrue none. Extra capacity is sold separately, as are Copilot Credits beyond what Sales Premium includes. Our Dynamics 365 licensing guide covers the base and attach rules in detail.

Why we do not start with the lower seat price

The usual advice is to pick the platform with the lower per user list rate. We disagree. In more than half of the comparisons we have run, the lower sticker carried the higher three year total once platform fees, add on clouds and ramp clauses were counted.

The better course is to model the full three year cost for both, with every attached fee and your existing agreements. Then negotiate both vendors against that model. Neither vendor's proposal puts the platform charges next to the seat price, so you have to add them yourself.

What have we seen in recent Dynamics 365 and Salesforce comparisons?

Across roughly 20 to 30 CRM selection and renewal engagements we ran in 2024 and 2025, the headline list rate predicted the winner in fewer than half. Of the 25 or so that reached a full head to head model, the lower sticker also had the lower three year cost 45 percent of the time. Three patterns recurred.

• Salesforce extras. Platform and add on cloud fees added 30 to 60 percent on top of the core CRM seat over a three year term.
• Dynamics inside the agreement. Dynamics 365 deals improved 10 to 20 percent when folded into an existing Microsoft enterprise agreement instead of bought on their own.
• Ramped seats. Salesforce ramp clauses committed buyers to seat growth that later ran 15 to 25 percent ahead of actual hiring.

The cheaper CRM is the one with the lower bill after the platform fees, the add on clouds and the ramp clause, whatever the seat price says.

What does a three year CRM cost model look like?

A usable model puts both vendors on the same term and seat forecast, each charge on its own line. Say you run Salesforce Enterprise Edition for 400 sales users, and the hiring plan reaches 520 by year 3. A realistic forecast is 430 in year 2 and 450 in year 3. The quotes below are hypothetical.

• Salesforce quote. $120 net per user per month, ramped to 400, 460 and 520 seats. A Full Copy sandbox at 30 percent of net spend (applied here to the seat line only), and a quoting add on (CPQ) for 100 users at $75 net.
• Dynamics quote. Sales Enterprise at $95 net on its own, or $82 once folded into the Microsoft enterprise agreement, with seats bought as hiring happens. A $150,000 allowance covers extra Dataverse capacity, Copilot Credits and a partner CPQ app.

On the Salesforce side, the sandbox and quoting lines add $866,160, or 43.6 percent on top of the ramped seat cost. Removing the ramp saves $187,200: $144,000 in seats and $43,200 in sandbox charges that move with them. Folding Dynamics into the agreement saves $199,680, 13.7 percent of the standalone seat cost.

The seat gap in this example is an assumption, and a Salesforce team facing a live Dynamics quote can close a good part of it. Feature fit may justify the rest. The point of the model is that you negotiate against totals, line by line, with the ramp and the percentage based charges visible.

What will each account team say, and how should you answer?

Expect each vendor to argue from the layer that favors it: Salesforce from the seat discount, Microsoft from the relationship. These are the lines we hear most, with the replies that work.

Salesforce lines

• "The ramp locks today's price for the seats you will add." Ask for a price hold on additional seats at the same net rate for the full term, with no committed quantity. You get the price protection without paying for empty seats.
• "This discount needs signature before quarter end." Salesforce's fiscal year ends on January 31, so the pressure peaks from November to January. Plan your timeline so that deadline helps you, and do not accept terms you have not modeled.
• "Core bundles Slack, Tableau Next and Premier Success, so it is better value." Price only the components you would actually buy. If you would not pay for Premier Success or Slack today, the bundle is a higher seat price.

Microsoft lines

• "Dynamics is almost free on top of your enterprise agreement." It is still licensed per user. Ask for the Dynamics line priced separately in the proposal, so you can see the discount and hold it at renewal.
• "Take Sales Premium so everyone has Copilot." Premium costs $45 more per user than Enterprise and includes 1,000 Copilot Credits per user per month. Buy it only for the users who will run agents, and keep the rest on Enterprise.

Which contract terms should you ask for?

Ask for terms that cap what the model shows as risk: seat commitments, percentage based charges and renewal pricing. Each of these is a normal request in an enterprise CRM deal.

1. No ramp, or a capped ramp. Strike the ramp unless the hiring plan is contracted. If you keep it, tie each step to a headcount trigger you control.
2. Price hold on added seats. The same net rate for new seats and new users of the same edition until the end of the term.
3. Fixed fees for sandboxes and support. Convert percentage of net spend charges into fixed amounts, so a seat increase does not raise them automatically.
4. Renewal price cap. A written limit on the renewal uplift for every product on the order form, not only the core seat.
5. Co terming. Every add on cloud ends on the master agreement end date, so you renegotiate one contract, once.
6. Reduction rights at renewal. The right to cut seats and drop add ons at renewal without losing the discount on what remains.

For the full Salesforce clause list, see our guide to Salesforce contract terms. On the Microsoft side, the Microsoft EA Renewal Playbook covers the 2024 to 2026 enterprise agreement cycle that a Dynamics purchase would sit inside.

How should you decide between Dynamics 365 and Salesforce?

Decide on fit with the systems and agreements you already have, and on the three year total that fit produces. Features rarely separate the two at the core CRM level.

Where you start from

If you run mostly on Microsoft, Dynamics often wins on incremental cost and on identity, since users, security and Power Platform are already in place. If your teams live in Salesforce and depend on AppExchange apps, the switching cost can outweigh a license saving.

• Microsoft heavy. Dynamics 365 usually carries the lower incremental cost.
• Salesforce embedded. Weigh migration, retraining and integration rebuild costs against the license gap.
• Greenfield. Model both on a clean three year total.

How company size changes the answer

A 300 user sales team often buys Dynamics through a Cloud Solution Provider partner, with less room to fold it into an agreement, so the seat rate matters more. Our note on Dynamics 365 in an EA versus CSP covers that choice.

A 5,000 user organization has agreement pricing to apply and enough Salesforce spend for sandbox, storage and API charges to add up, so the extras usually decide.

How do you check your own usage before the quotes arrive?

Check actual usage in both systems before you forecast seats, because the quote is only as good as your count. Both vendors give you the data in the admin consoles.

In Salesforce

Setup, Company Information shows total, used and remaining licenses by type. System Overview shows API requests over the last 24 hours against your limit, and Storage Usage shows data and file storage by object. A user report filtered on last login finds paid seats that no one has used in 90 days.

In Microsoft

The Microsoft 365 admin center shows assigned and available Dynamics licenses. In the Power Platform admin center, Licensing then Dataverse shows database, file and log usage against your entitlement, and the See Dataverse capacity per license button breaks out the per license accruals. Our Microsoft 365 license optimizer helps size the wider Microsoft spend that Dynamics would sit inside.

What to do next

1. Start 6 months out. Build a three year total cost model for each platform with every fee on its own line.
2. Load the Salesforce extras. Add platform fees, API limits, sandboxes, storage, success plans and add on clouds to the Salesforce side.
3. Load the Microsoft agreement effect. Price Dynamics both standalone and inside your enterprise agreement, plus Dataverse capacity and Copilot Credits.
4. Remove the ramp. Strike or cap any Salesforce ramp clause not backed by a contracted hiring plan.
5. Keep both quotes live. Let each vendor know a priced alternative exists until you sign.
6. Co term everything. Align all add on clouds with the master agreement end date.
7. Size the Microsoft side. Run the Microsoft 365 license optimizer to see how Dynamics fits your existing agreement.
8. Get an independent review. Have CRM advisors check both contracts before you sign either one.

Frequently asked questions