Microsoft positions Dynamics 365 on Plan SKUs, which bundle Sales, Customer Service, Field Service, Project Operations, and Marketing into a single per user license. The Plan is the highest revenue per seat path Microsoft can offer. It is also the wrong shape for most enterprises. The renewal opportunity is to deconstruct the Plan into per app licenses against the apps each population actually uses. Across our 34 Dynamics engagements, the bundle redesign produces median savings of twenty five to forty percent on the Dynamics line.
The Dynamics 365 license catalog presents two structural options. The full Plan license that bundles five first party apps under a single per user price. The per app license that prices each Sales, Customer Service, Field Service, Finance, or Supply Chain instance independently per user. The breakeven between the two sits around three concurrent apps per user. Most enterprise populations consume two apps. The default Plan renewal is therefore a structural overpay.
The Plan license bundles five first party apps under one per user price. The math works only if each user is consuming three or more of those apps. Telemetry from active engagements consistently shows that population to be a minority.
The Plan breaks even against per app licensing at three concurrent apps per user. Populations below the threshold belong on per app. Populations above belong on the Plan. The bundle work measures the threshold per user and reassigns the entire base.
Four structural moves drive the Dynamics bundle math at renewal. Each move requires app usage telemetry and each surfaces in the anchor letter.
The Plan to per app migration is the highest dollar move on most Dynamics renewals. The bundle work reads app usage per user across the audit window, identifies the users running fewer than three apps, and moves them to per app licensing. The Plan retention list shrinks to the users genuinely consuming the broader bundle.
Dynamics offers attach licensing at a steep discount for the second and subsequent app per user. A user on a Sales base license adds Customer Service at the attach price, not at the full Customer Service price. The bundle work audits the dual app populations and ensures the cheaper attach pricing is applied across the renewal.
The Team Member SKU covers light read mostly users at roughly a tenth of the Plan price. The bundle work audits the active Plan population and identifies the read mostly users (executive viewers, finance approvers, occasional reporters) who can move to Team Member. Microsoft has tightened Team Member use rights over recent years and the audit needs to confirm compliance, but the population that legitimately fits Team Member is consistently meaningful.
Enterprises with legacy CRM or AX on premises footprints have dual use rights during transition. The renewal is the moment to surface those rights, structure the transition timeline in writing, and avoid the double pay window during migration. Microsoft account teams typically do not volunteer the dual use rights at renewal. The buyer side has to raise the question and document the entitlement.
The Dynamics Plan is the cleanest example of a Microsoft SKU that is sold on the assumption you will not measure the underlying usage.Practice principle · Dynamics bundle engagements
The table below summarizes the typical recovery bands we observe across Dynamics renewals when each move is applied cleanly.
| Lever | Telemetry source | Typical recovery |
|---|---|---|
| Plan to per app migration | App access logs per user | 20 to 35 percent of Dynamics line |
| Attach license substitution | Dual app user counts | 5 to 10 percent of Dynamics line |
| Team Member reassignment | Read versus write activity | 5 to 15 percent of Dynamics line |
| Dual use rights surfacing | On premises footprint vs cloud rollout | Variable, prevents double pay |
| Capacity right size on Finance, SCM | Tenant capacity utilization | 10 to 20 percent of platform line |
Across the 34 Dynamics engagements in our practice, the Plan to per app migration is the single most reliable double digit savings move available. Microsoft account teams do not typically surface the migration because the Plan retention is the higher revenue path. The opportunity sits entirely on the buyer side. The work is mechanical. Read app usage per user across a one hundred eighty day window. Identify the population running two or fewer apps. Build the per app reassignment proposal. Surface the result in the anchor letter with the consumption windows cited. The Dynamics line tends to be the smallest line on most EA renewals and therefore receives the least attention from procurement teams. The recovery rate per attention hour spent on the Dynamics line is consistently the highest of any line item on the renewal. Our standing recommendation is to put a dedicated analyst on the Dynamics line at month twelve before renewal. The hours pay for themselves several times over.
The Dynamics bundle redesign has to be executed in a specific order to produce the strongest commercial outcome. Out of sequence work tends to leak value at the renewal table because partial analyses get probed back to the carry forward number.
The first step is the per user app access audit across a one hundred eighty day window. The audit produces the population segmentation that drives the entire bundle math. Without the audit, every subsequent step rests on assumption rather than data and the renewal conversation reduces to negotiation rather than measurement. The audit is operationally simple but it is also the step most often deferred. The buyer side teams that complete the audit at month twelve before renewal land the strongest bundle outcomes.
The second step is the candidate list for Plan to per app migration. The candidates are users running two or fewer apps across the audit window. The list is operationally complete once the population segmentation is done. The candidate list is the input to the anchor letter and the basis for the negotiated bundle.
The third step is the attach pricing audit across the dual app population. The audit identifies users incorrectly licensed at full second app pricing and surfaces the correction to attach pricing. The audit is straightforward and the savings are mechanical.
The fourth step is the Team Member qualification audit. The audit identifies the read mostly users who legitimately qualify for the lower SKU. The use rights are restrictive and the audit must be precise to survive scrutiny, but the qualifying population is consistently meaningful across our engagements.
Three patterns from Dynamics bundle redesigns across the practice. Each affects the renewal outcome.
Across the 34 Dynamics engagements in our practice, the Plan license is the highest revenue Dynamics SKU and the one most aggressively positioned by Microsoft account teams. The positioning typically rests on the assumption that the user population will adopt three or more apps over the term. The telemetry rarely confirms that assumption. Most populations adopt one or two apps and the third app adoption never materializes. The Plan therefore becomes a structural overpay across the entire term. The renewal is the cleanest moment to reset the bundle against measured app usage rather than against forward assumptions.
Dynamics offers attach licensing at a steep discount for the second and subsequent app per user. The attach price is roughly a third of the second app full price. Across our engagements, dual app populations are routinely licensed at full per app pricing because the attach mechanic was not surfaced at the original procurement event. The renewal correction is to apply attach pricing across the dual app population. The savings are mechanical and the Microsoft account team concedes the correction once the request is surfaced in writing.
Microsoft tightened Team Member use rights over recent product cycles and the legitimate Team Member population is smaller than it once was. The population is still real and still meaningfully cheaper than the Plan. Across our engagements, the Team Member candidate population (executive viewers, finance approvers, occasional reporters) sits between five and fifteen percent of the licensed Dynamics base. The audit work is exacting because the use rights are restrictive, but the savings justify the precision.
The Dynamics bundle work converts into negotiated value at the anchor letter and stays codified through the renewal contract amendment. The anchor letter restates the Dynamics base around the per app and attach pricing structure with usage telemetry cited per population. The contract amendment then locks the bundle structure for the term with explicit step up rights, attach pricing protections, and Team Member use right documentation. The buyer side teams that surface the bundle math in the anchor letter and codify it in the contract consistently produce Dynamics line outcomes twenty to forty percent below the carry forward quote. The teams that surface the bundle math without codifying it in writing routinely see the savings erode mid term as the population mix changes and the Microsoft account team has the discretion to apply default Plan pricing on new assignments. The contract codification is what makes the bundle savings durable across the entire renewal term.
Each lever on the renewal interacts with every other lever. The related notes below cover the adjacent posture work.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is on your renewal, and whether we are the right firm for this engagement. Buyer side only. Never affiliated with Microsoft.