Dynamics 365 Overspend Is Structural, Not Accidental
Dynamics 365 licensing overspend is not caused by inattentive procurement teams. It is caused by Microsoft's commercial architecture, which creates systematic incentives for account teams to provision at the highest viable licence tier, and by the complexity of a platform that spans 30+ applications across five product families, each with its own user classification model, attach rate structure, and Copilot integration pricing. Enterprises that manage Dynamics 365 renewals without independent advisory support — relying on their Microsoft account team or system integrator for licence guidance — consistently overpay by 20–40% against the correctly structured equivalent deployment.
This guide sets out the four cost reduction levers that independent advisory firms apply in every Dynamics 365 engagement, with specific mechanics, typical savings ranges, and the order of operations for applying them effectively before an EA renewal.
The Four Cost Reduction Levers
The levers compound when applied together — an organisation that corrects user classification (15% saving), restructures the attach rate (8% saving), removes unused add-ons (10% saving), and negotiates to market-rate discounts (12% saving) achieves a combined reduction of approximately 38% against the status quo renewal. These are not optimistic projections — they are the typical outcomes of a systematic pre-renewal analysis programme.
Lever 1: User Classification Optimisation
Every Dynamics 365 application uses a tiered user licensing model. Full Users pay the highest rate and have full access to all application functionality. Activity Users pay 20–30% of the Full User rate and can perform a defined set of task-based transactions. Team Members pay $8/user/month and have read access plus a small number of lightweight tasks. The commercial gap between Full User and Activity User is enormous: $120–$180 vs $50 per user per month, depending on the application. At scale, the difference between a correctly classified user population and a default over-provisioned one compounds rapidly.
Methodology
Step one is to obtain the transaction log for all licenced users for the prior 12 months from your Dynamics 365 tenant — available through Lifecycle Services (LCS) audit logs for F&O/SCM or through the D365 audit log for Sales and Customer Service. Step two is to categorise each user's transactions by type: initiating transactions (create purchase order, create sales order, create production order) vs confirmatory transactions (approve purchase order, confirm delivery, approve leave request). Step three is to map each user's transaction profile against the published Activity User task list for their specific application. Users whose entire transaction history falls within the Activity User task list are candidates for reclassification.
In practice, 20–35% of users in Finance/SCM deployments and 25–40% of users in Sales/Customer Service deployments qualify for Activity User reclassification based on this analysis. The analysis takes 2–4 weeks with the right tooling and produces a documented, auditable finding that supports the licence count change at renewal without creating compliance exposure.
User classification analysis must be completed before entering renewal negotiations. Microsoft's account team will anchor the renewal conversation on the current provisioned licence count. Once you have accepted the anchor, reclassification savings are harder to negotiate. Completing the analysis first — and presenting it as a formal deliverable — establishes the correct baseline from which negotiation begins. The account team cannot argue against documented transaction data.
Lever 2: Attach Rate Restructuring
When two Dynamics 365 applications are purchased together in an EA, Microsoft applies an attach rate discount on the secondary application. The base application is priced at the full EA rate; the attach application receives a discount (typically 20–30%) for users who need both. The decision about which application is "base" and which is "attach" is not neutral — it is determined by which application has the larger user population, and getting it wrong can cost $15–50/user/month for the user population that requires both applications.
Common attach rate errors found in enterprise Dynamics 365 deployments include Finance designated as attach when Finance has a larger user population than SCM; Customer Service designated as base when Sales has more users; and Business Central add-on licences structured as full-rate purchases rather than as Power Apps attach components for extension scenarios. Each error is correctable at renewal with documented analysis of the user population distribution across applications.
For a 500-user Finance + SCM deployment where Finance has 350 users and SCM has 300 users with 250 users needing both: correctly structured (Finance as base), the cost is 350 × $180 + 50 × $180 + 250 × $126 (SCM at 30% attach discount) = $126,000/month. Incorrectly structured (SCM as base): 300 × $180 + 100 × $126 + 250 × $126 (Finance attach) = $57,600/month additional vs the correct structure. Over a 3-year EA term, the structural error costs $2.07M more than the correctly structured equivalent.
Lever 3: Add-On Module Rationalisation
Every Dynamics 365 application family has add-on modules that extend core functionality at additional cost. These add-ons accumulate in EA agreements through implementation projects, pilot programmes, and account team upselling — and they frequently remain in the agreement after the project that justified them has ended, the pilot that was supposed to expand never expanded, or the functionality was deployed but not adopted.
| Application | Common Add-Ons | Monthly Cost | Adoption Reality |
|---|---|---|---|
| Finance/SCM | Copilot for Finance, Intelligent Order Management, Asset Management | $30–$300+ | Copilot: 30% meaningful ROI in Year 1. IOM: often used for <20% of projected order volume |
| Sales | Copilot for Sales, Sales Premium, Relationship Intelligence | $30–$40/user | Conversation Intelligence active use: typically 40–50% of provisioned users |
| Customer Service | Copilot for Customer Service, Voice Channel, Digital Messaging | $75–$110/user | Voice channel provisioned but primary contact via digital: common in 60% of deployments |
| HR | Viva Suite, Copilot for HR, Ceridian payroll integration | $12–$30/user | Viva Suite tenant-wide deployment when only 3–5 modules actively used by subset |
| Business Central | Copilot for Finance add-on, Industry-specific extensions | $30+ | Copilot for Finance: most adoption in bank rec and cash flow; other modules less active |
The add-on rationalisation process is straightforward: obtain usage telemetry for each add-on from your Dynamics 365 admin centre, identify add-ons with active adoption below 30% of provisioned users, and remove those add-ons from the renewal unless the deployment plan for the remaining 12 months includes a concrete activation programme. Removing unused add-ons at renewal is a standard commercial negotiation — Microsoft will not fight it if you have adoption data to support the decision.
Lever 4: EA Discount Benchmarking
The headline EA discount — the percentage discount from Microsoft's published list price — is the most visible commercial lever, but it is often the last one optimised. Microsoft's account teams open renewal conversations with discounts that reflect the organisation's prior engagement, not the current market rate. For Dynamics 365 applications, current market discounts (as of Q1 2026) for enterprise EA agreements are:
| User Count | Finance/SCM Discount Range | Sales/CS Discount Range | Business Central Discount |
|---|---|---|---|
| 50–200 users | 15–25% | 15–20% | 10–18% |
| 200–500 users | 22–35% | 20–30% | 15–25% |
| 500–1,000 users | 30–42% | 28–38% | 20–32% |
| 1,000+ users | 35–50% | 32–45% | 25–40% |
These ranges represent current market benchmarks across active EA negotiations — not published discount schedules, which Microsoft does not publish. Organisations negotiating Dynamics 365 renewals without access to current market benchmark data will accept whatever discount the account team proposes without knowing whether it is at the bottom, middle, or top of the achievable range. Independent advisory firms with current pipeline data can benchmark your current EA discount against these ranges and identify the gap between what you have and what is achievable.
Combining the Four Levers: A Worked Example
A 400-user combined Finance + SCM deployment, currently paying $108,000/month at list price with a 20% EA discount (effective: $86,400/month). Current annual cost: $1,036,800. Three-year EA commitment at current terms: $3,110,400.
After applying all four levers: user classification reduces Finance/SCM Full Users by 30% to Activity User (saving $23,000/month), attach rate restructuring corrects base-vs-attach designation (saving $8,000/month), removal of Copilot add-ons with low adoption (saving $6,000/month), and EA discount improved from 20% to 35% through competitive benchmarking and relationship leverage (saving $14,000/month). Combined saving: $51,000/month — $612,000/year — $1,836,000 over the 3-year term. Effective cost reduction: 59% relative to the status quo renewal.
This is not a theoretical projection. It is the composite of findings from engagements with similar Dynamics 365 deployments, adjusted to be conservative. The key variable is preparation — all four levers are only available if the analysis is completed before renewal terms are signed. After signature, the leverage disappears for another three years. See our complete Dynamics 365 licensing guide and our EA negotiation complete guide for the full framework that supports this preparation process.