Dynamics 365 Under an Enterprise Agreement (EA)
An Enterprise Agreement is a volume licensing contract for large organisations — typically requiring 500+ users or devices. It covers a 3-year term (occasionally 5 years) and is designed for enterprises standardising on Microsoft's suite. When Dynamics 365 is included in an EA, you commit to a set quantity of licences for the term, with negotiated pricing that locks in rates for the duration.
Commitment and Price Lock
You commit upfront to a set number of Dynamics 365 licences by product for a 3-year period. You can increase counts via annual true-ups, but you cannot decrease until renewal. This provides cost predictability — you know your base Dynamics 365 cost for 3 years — but it is inflexible if your needs drop. The EA locks pricing for the term, protecting you from list price increases on committed quantities. Additional licences added during the term are typically available at the same negotiated rate.
Volume Discounts
EAs typically provide 15–30 % below list pricing for Dynamics 365, depending on total commitment and negotiation. Microsoft extends volume discounts within the EA, and enterprise customers can negotiate custom discounts on top of standard pricing. This discount level is not available through CSP or Web Direct channels. For large deployments (500+ users), the per-user savings over a 3-year term can represent $500K–$2M+ compared to list-rate CSP subscriptions.
Annual True-Up Process
EAs handle changes via annual true-up rather than monthly adjustments. If you exceeded licensed quantities during the year, you report and pay for additional usage once per year, backdated to when it was first used. If you scaled down, you cannot receive credit until renewal. The EA trades flexibility for stability — it assumes an upward or steady trajectory, not downsizing. For growing organisations, this is efficient; for organisations in transition, it creates waste.
Enterprise-Wide Reassignment
EA licences are enterprise-wide — you can reassign them internally without changing the agreement. If one division's user count drops and another's increases, you can shuffle licences since the EA is an org-wide contract. This internal flexibility partially offsets the lack of true-down: the total count is fixed, but allocation within the organisation is fluid.
Dynamics 365 via Cloud Solution Provider (CSP)
The Cloud Solution Provider programme is Microsoft's channel for purchasing cloud services on a subscription basis through a partner. CSP offers monthly or annual terms per licence, with the ability to add or remove subscriptions at each billing cycle — a fundamentally different model from EA's multi-year commitment.
Subscription Flexibility
CSP allows you to add or remove licences at each billing cycle — monthly for monthly subscriptions, or at the end of the annual term for annual subscriptions. This "pay only for what you use" model is ideal for variable staffing or seasonal usage. If you hire 100 contractors for a 6-month project who need Dynamics access, under CSP you add 100 licences for those months and remove them afterward. Under an EA, you would true-up and then be committed to those licences until the end of the 3-year term.
True-Down Capability
CSP's ability to reduce licence counts is its single biggest advantage over EA. If your company undergoes a reorganisation and 100 Dynamics users are no longer needed, you reduce those subscriptions and stop paying — effective at the end of the current billing period. In an EA, you continue paying for those 100 until the 3-year term ends. For organisations experiencing headcount volatility, M&A activity, or uncertain Dynamics adoption, this flexibility can save hundreds of thousands of dollars compared to being locked into an EA minimum.
List-Rate Pricing
CSP pricing is generally based on Microsoft's current list price (MSRP). Partners may offer a small discount (typically 3–8 % from their margin), but the deep negotiated discounts achievable in an EA (15–30 %) are not available. However, CSP's cost advantage comes from eliminating waste: many enterprises find that the savings from trimming unused licences via CSP's flexibility outweigh the higher per-licence price. Microsoft's New Commerce Experience (NCE) now offers 1-year and 3-year CSP terms that can lock pricing, blurring the line between CSP and EA.
Partner-Managed Support
With CSP, your first line of support is the CSP partner — not Microsoft directly. Microsoft expects partners to handle customer issues, escalating to Microsoft only when needed. This can be advantageous if the partner has strong Dynamics expertise (more personalised support), or a disadvantage if the partner is not responsive (an extra layer between you and Microsoft). Many large CSP partners include managed services, training, and adoption support as part of their value proposition.
EA vs CSP — Head-to-Head Comparison
| Dimension | Enterprise Agreement (EA) | Cloud Solution Provider (CSP) |
|---|---|---|
| Commitment | 3-year contract, 500+ user minimum | Monthly or annual per licence — no minimum |
| Pricing | Negotiated volume discounts (15–30 % below list) | List pricing with minor partner discounts (3–8 %) |
| Price lock | Locked for 3-year term | Subject to list price changes (unless 1/3-year NCE term) |
| Scaling up | Add via annual true-up (backdated) | Add anytime, pay prorated going forward |
| Scaling down | No reduction until renewal | Reduce at next billing cycle |
| Payment | Annual upfront | Monthly billing (or annual pre-pay) |
| Support | Separate Unified Support agreement | Partner-provided (often included) |
| Relationship | Direct Microsoft account team | Through CSP partner → Microsoft |
| Administration | Full customer self-service | Self-service (some changes may involve partner) |
| Renewal | Major renegotiation every 3 years | Continuous — switch partner or model anytime |
| Best for | Large, stable deployments valuing best pricing | Variable, growing, or uncertain deployments valuing flexibility |
"The EA vs CSP decision is not binary — the most sophisticated enterprises use both. Core stable users on EA for maximum discount, variable and project-based users on CSP for flexibility. The hybrid approach captures the strengths of both models while mitigating their weaknesses."
The Hybrid Strategy — Best of Both Models
Stable Base on Enterprise Agreement
Place your permanent, predictable Dynamics 365 user base on the EA: the 500 Sales Enterprise users who will be there for the full 3-year term, the 200 Finance users running core ERP processes, and the 300 Customer Service users in your contact centre. These users benefit from the EA's 15–30 % volume discount without risk of paying for unused licences. The EA commitment for this stable base also contributes to your total Microsoft spend, which strengthens your negotiation position for Azure discounts, M365 pricing, and other EA components.
Flexible Layer on CSP
Place variable, seasonal, and project-based Dynamics 365 users on CSP subscriptions: contractors who need 6-month access, seasonal staff during peak periods, new business units where adoption is uncertain, and pilot groups for new Dynamics modules. CSP's monthly true-down capability means you only pay for these users when they are active. The slightly higher per-user cost (list rate vs EA discount) is more than offset by the elimination of waste. A 100-user CSP layer that averages 60 users over the year costs 40 % less than committing to 100 EA licences used at 60 % utilisation.
Cost Comparison — When Each Model Wins
The financial comparison between EA and CSP depends on two variables: per-user discount rate and licence utilisation rate. EA wins on price; CSP wins on waste elimination. The breakpoint determines which model delivers lower total cost.
| Scenario | Users Committed | Avg Monthly Active | Utilisation | EA Annual Cost (25 % discount) | CSP Annual Cost (list) | Winner |
|---|---|---|---|---|---|---|
| Stable enterprise | 500 | 480 | 96 % | $1,350,000 | $1,728,000 | EA (22 % cheaper) |
| Growing company | 500 | 400 | 80 % | $1,350,000 | $1,382,400 | Close — EA slightly cheaper |
| Variable workforce | 500 | 300 | 60 % | $1,350,000 | $1,036,800 | CSP (23 % cheaper) |
| Seasonal/project | 500 | 200 | 40 % | $1,350,000 | $691,200 | CSP (49 % cheaper) |
| Breakpoint | At ~80–85 % utilisation, EA and CSP costs converge. Above 85 %, EA wins. Below 75 %, CSP wins decisively. | |||||
These calculations assume Sales Enterprise at $95/user/month list price with a 25 % EA discount. Actual figures vary by product, negotiated rates, and partner terms — but the utilisation-driven dynamic is consistent across all Dynamics 365 modules. The strategic implication: before committing to either model, measure your actual utilisation rate across at least 6 months of data.
Considerations When Switching Between Models
EA to CSP — Timing and Transition
If you are moving Dynamics 365 from an EA to CSP, the optimal transition point is at EA renewal. Do not renew the Dynamics 365 component in the new EA; instead, establish CSP subscriptions to take effect when the current EA term ends. Key considerations: (1) Ensure continuity of service — CSP subscriptions should be active before EA licences expire. (2) Negotiate with your CSP partner for best available pricing, particularly if committing to annual or multi-year NCE terms. (3) Verify that all Dynamics 365 data, configurations, and integrations are unaffected by the licensing channel change — the product itself does not change, only the billing and entitlement mechanism.
CSP to EA — Consolidation for Discounts
If your Dynamics 365 usage has grown and stabilised, consolidating from CSP into an EA can reduce per-user costs by 15–30 %. The optimal moment is when you can confidently predict your minimum user count for a 3-year period. Negotiate the EA to include only the stable minimum — any users above that threshold can remain on CSP for flexibility. When transitioning, align the CSP subscription end dates with the EA start date. Cancel CSP subscriptions only after confirming EA licences are active and assigned.
Running Both Simultaneously — Governance
If using a hybrid model, implement clear governance to prevent confusion and double-licensing. Maintain a single licence management system that tracks which users are on EA versus CSP. Establish rules for when new users are added to EA (true-up) versus CSP (flexible subscription). Ensure procurement, IT, and finance all understand the two channels and their respective cost implications. Without governance, organisations risk paying for the same user on both EA and CSP — an expensive and common mistake in hybrid environments.
✅ CIO Recommendations — EA vs CSP for Dynamics 365
- Analyse your user stability: If 80 %+ of Dynamics 365 users are permanent and predictable, EA delivers better value through volume discounts. If more than 30 % of users are variable, CSP's flexibility may save more than EA's discount
- Consider the hybrid approach: Place your stable minimum on EA (at negotiated discount) and your variable layer on CSP (with monthly flexibility). This captures the best of both models
- Negotiate EA Dynamics 365 pricing separately: Within your EA, negotiate Dynamics 365 discounts as a distinct line item — do not let Microsoft bundle D365 pricing into an overall discount that obscures the per-product rate
- Evaluate CSP partner value-add: If using CSP, select a partner based on Dynamics 365 expertise, support quality, and willingness to pass through margin as discount — not just the lowest headline price
- Plan transitions at EA renewal: Any shift between EA and CSP should be timed to EA renewal. Mid-term transitions create overlap costs and administrative complexity
- Use CSP for new module pilots: When evaluating new Dynamics 365 modules (Field Service, Project Operations, etc.), use CSP's monthly subscriptions for the pilot — then move to EA if the module is adopted at scale
- Account for total Microsoft spend: Dynamics 365 EA commitment contributes to your total Microsoft spend, which affects Azure discount tiers and M365 pricing. Factor this "EA halo effect" into your cost comparison
- Implement licence governance for hybrid: If running EA and CSP simultaneously, maintain a single source of truth for licence assignments to prevent double-licensing and ensure cost accountability per department
Microsoft's New Commerce Experience (NCE) — Blurring the EA/CSP Line
Microsoft's New Commerce Experience (NCE) has introduced annual and multi-year term options within CSP that significantly blur the traditional distinction between EA and CSP. Understanding NCE is essential for CIOs evaluating their Dynamics 365 procurement strategy.
NCE Annual Subscriptions
NCE annual terms offer a 20 % discount compared to monthly CSP pricing — narrowing the gap with EA volume discounts. An NCE annual subscription locks the per-user price for 12 months and provides a predictable cost basis. However, cancelling an NCE annual subscription mid-term incurs early termination fees (you pay for the remaining months). This means NCE annual is a middle ground: more flexible than EA (1-year vs 3-year commitment), cheaper than monthly CSP, but less flexible than monthly CSP for true-down. CIOs should use NCE annual for "semi-stable" users — those likely to remain for 12 months but where 3-year commitment is not justified.
Three-Tier Procurement Strategy
With NCE, the optimal approach becomes a three-tier model: (1) EA for the permanent base (maximum discount, 3-year commitment), (2) NCE annual CSP for semi-stable users (moderate discount, 1-year commitment), (3) monthly CSP for truly variable users (list pricing, maximum flexibility). This three-tier structure captures 90 %+ of the cost optimisation opportunity while maintaining flexibility where it is needed. Map each Dynamics 365 user segment to the appropriate tier based on expected tenure and usage predictability.