Dynamics 365 renewals. On the buyer's terms.

Dynamics 365 renewals reward buyers who audit the base plus attach structure early, because misassigned licenses and dormant seats compound quietly inside an EA or CSP term.

How does Dynamics 365 base plus attach licensing work?

Every full user needs one base license, the most expensive app they use, and can attach additional apps at a reduced rate. Microsoft publishes the structure on its Dynamics 365 pricing page.

The order matters: the base must be the highest priced app in the user's stack. Setting a cheaper app as base and attaching the expensive one is non compliant and surfaces in true ups.

Where does the structure go wrong in practice?

• Misordered base: cheaper base with premium attach, flagged at true up.
• Stacked full licenses: two base licenses where base plus attach was available.
• Forgotten attaches: attach eligibility lapses unnoticed when the base app changes.

Who actually needs a full Dynamics 365 user license?

Only users who operate the app: create, configure, and process core records. Light users who read data, update basic records, or approve belong on Team Members licenses, whose boundaries Microsoft defines in the Dynamics 365 licensing documentation.

How do you find misassigned seats?

Pull per user activity from the admin center and map actions against license rights. Users whose ninety day history fits Team Members boundaries are immediate downgrade candidates.

What hidden costs surface at a Dynamics renewal?

Three line items grow silently through the term: Dataverse storage overages, priced per the capacity documentation, premium connector and Power Platform dependencies, and sandbox environments licensed as production.

• Dataverse capacity: database, file, and log storage accrue past entitlement; archive before renewal, not after.
• Power Platform dependencies: flows and apps built against Dynamics data can require their own licensing.
• Environment sprawl: sandboxes and copies multiply, each consuming capacity entitlements.

Why does storage matter at the negotiation table?

Because Microsoft prices overage at list while capacity packs are discountable inside the renewal. Walking in with a storage remediation plan converts a penalty into a negotiated line.

How do you run the Dynamics 365 renewal negotiation?

Open 9 months out with a seat audit, a downgrade plan, and the storage remediation case; that package cut renewals 18 to 28 percent in our file. Check current promotions and repricing on the Microsoft Product Terms site before pricing anything.

1. Audit seats and activity 9 months before term end.
2. Downgrade misassigned full users to Team Members or app licenses.
3. Fix base plus attach ordering before Microsoft finds it.
4. Archive Dataverse data and price capacity packs into the deal.
5. Benchmark unit rates and bring the EA vs CSP comparison.
6. Close against Microsoft's June 30 fiscal year end.

Where the common advice on Dynamics 365 renewals is wrong

The standard partner advice is to true up generously and tidy the estate after renewal, because compliance risk dwarfs license waste. We disagree. In roughly 11 of the 15 plus Dynamics renewals Morten Andersen benchmarked in 2024 to 2025, the post renewal cleanup never happened, and the inflated count became the baseline every subsequent negotiation anchored on. Waste locked in at renewal compounds for the life of the relationship. The buyer side move is to audit and downgrade before the count, accept the smaller compliance exposure of a documented remediation, and never let a true up set next term's baseline.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Pull per user activity for the trailing ninety days from the admin center.
2. Map every user against full, Team Members, and app license boundaries.
3. Correct base plus attach ordering across the estate.
4. Quantify Dataverse overages and build the archive plan.
5. Benchmark unit rates and compare EA against CSP for your size.
6. Open the renewal 9 months out and close against June 30.

White Paper · Microsoft

Microsoft Dynamics 365 Enterprise Licensing

The buyer side guide to Microsoft Dynamics 365 enterprise licensing: how to right size Sales, Customer Service, Finance, and Supply Chain modules. Read it free.

Read the white paper

Frequently asked questions

How does base plus attach work in Dynamics 365?

The most expensive app a user needs is licensed as their base; every additional qualifying app attaches at a steep discount. The base must always be the highest priced app.

What can Team Members licenses actually do?

Read data, update limited records, and approve. They cover light users at a fraction of full user cost, and the rights boundary is technically enforced.

What share of full user licenses are typically misassigned?

In our 2024 to 2025 file, 15 to 25 percent of full user seats showed activity that fit Team Members or app specific licenses.

Why do Dataverse storage costs surprise buyers at renewal?

Capacity accrues silently past entitlement through the term, and Microsoft prices overage at list. An archive plan converts the penalty into a negotiable line.

When should a Dynamics 365 renewal start?

Nine months before term end, with a seat audit and activity data. The audit package funded reductions of 18 to 28 percent in our engagements.

Is EA or CSP better for Dynamics 365?

It depends on size and flexibility needs. EAs suit large stable estates; CSP offers monthly flexibility. Bring the comparison to the renewal either way.