Most Dynamics 365 savings are decided months before the renewal meeting, not in it. Once you're inside the window, you're negotiating price on a seat count you've already accepted. This is a 12-month playbook for right-sizing licenses, cleaning up what you pay for, and walking into renewal with options.
The short answer
- Start 12 months out. In finance and operations apps, licenses follow security roles, so right-sizing means redesigning roles, and that takes time.
- The biggest levers are usually user-type changes, removing departed users and unused attach licenses, and trimming environments, add-ons, and partner retainers.
- Renewal is often your only chance to reduce seats. If the same workflows keep driving cost, plan to replace them rather than renegotiate them every term.
Know when you can actually reduce
The timing rules depend on how you buy.
- Enterprise Agreement. Microsoft describes the EA as a three-year agreement. It says only the Subscription Enrollment lets you increase or decrease subscription counts annually. True-up orders are due 30 to 60 days before your anniversary. Microsoft's own suggested timeline starts the conversation 120 days out.
- Cloud Solution Provider (CSP). Under Microsoft's new commerce policy, per-user subscriptions can be cancelled for a prorated refund within seven days of purchase. That window "doesn't reopen until the subscription itself renews into a new term."
Either way, the renewal date is when lower counts take effect. If your analysis isn't finished by then, you carry the old count for another term. Confirm the exact reduction rights for your SKUs in your agreement and Microsoft's Product Terms.
- 12–9 moBuild the real baseline
- 9–6 moRight-size users and apps
- 6–4 moClean up capacity and spend
- 4–0 moNegotiate with the facts
Months before your renewal date.
Month 12 to 9: Build the real baseline
Pull three lists and reconcile them:
- What you own. Licenses purchased and assigned, from the Microsoft 365 admin center.
- What roles require. In finance and operations apps, the security roles you assign decide the license each user needs, according to Microsoft Learn. The License usage summary, under System administration > Security > Security Governance, shows how roles map to license requirements.
- What people actually do. Sign-in and usage data for each user.
This matters more since Microsoft tightened enforcement. Its September 2025 announcement says license validation for finance and operations apps begins for customers whose renewal or anniversary falls after January 15, 2026, and unlicensed users lose access. Microsoft's own advice is to use the License Usage Summary to remove unnecessary entitlements from roles. That's the cost work and the compliance work in one.
Add the non-license spend to the baseline too: partner retainers, ISV add-ons, Azure, and extra environments. They often sit in other budgets.
Month 9 to 6: Right-size users and apps
Change user types where the work allows it
Microsoft's licensing guide describes Team Members as read-only access plus designated light tasks. Operations – Activity sits between Team Members and a full license. ERP Research lists Finance and SCM full users at $210, activity users at about $50, and attach licenses at $30. Find the people whose roles carry full-license privileges they never use. Build narrower roles, test them in a sandbox, and move those users down.
Remove what nobody uses
- Departed and inactive users. Microsoft Learn recommends disabling users who leave or aren't actively using the apps, so they stop counting toward licensing requirements.
- Attach licenses for apps a user hasn't opened in months.
- Whole apps or modules bought for a project that never fully rolled out.
An illustrative result
Take the 500-user company on our site: 350 full users and 150 activity users, about $972,000 a year at list price. Suppose the review finds the following:
- 50 full users who can move to activity: 50 × ($210 − $50) × 12 = $96,000 a year.
- 25 departed users still holding full licenses: 25 × $210 × 12 = $63,000 a year.
- 40 unused attach licenses: 40 × $30 × 12 = $14,400 a year.
That's $173,400 a year, or about 18% of the license bill, before any price negotiation. These are illustrative numbers. Your own baseline gives you the real ones.
Month 6 to 4: Clean up capacity and spend
Check storage in the Power Platform admin center before you buy more. Microsoft's storage guidance lists 15 ways to free space, such as recurring bulk-deletion jobs for old workflow logs, email attachments, and audit logs. Two cautions from the same page: deletions can't be undone, and storage figures can take up to 72 hours to update. Agree retention rules with finance and legal before you delete anything.
Then review the rest:
- Environments. Retire sandboxes nobody has refreshed in a quarter.
- ISV add-ons. Cancel or consolidate those that duplicate standard features.
- Partner retainers. Compare hours billed with hours used, and rebid if the gap is large.
Month 4 to renewal: Negotiate with the facts
By now you know your true seat count, and you've proved you can run on it. Use that position:
- Lead with the right-sized count, not last term's number.
- Ask for price protection across the full term. Microsoft has raised list prices before, as in October 2024, and those increases applied to existing customers at renewal.
- Ask for reduction rights at each anniversary, in writing, if your agreement doesn't already give you them.
- Don't add new products to win a discount unless you'd buy them anyway.
- Be ready to say what you'd do instead. A credible alternative, even for part of the estate, changes the conversation.
When the right answer is to replace, not renegotiate
Right-sizing trims the bill without changing what drives it. If the same workflows push you onto full licenses, extra add-ons, and partner change requests at every renewal, consider moving them off the per-user meter. Good candidates share three traits. They're heavily customized. They're used by many people who need only a slice of Dynamics. And they differentiate how you operate. Finance and payroll move to proven cloud products rather than being rebuilt. Replacement takes longer than one renewal cycle, so start it early and stage it. You then cut seats at each renewal as workflows move. We offer this, so weigh our view accordingly. Our Escape Path does this in waves, with AI agents built into each workflow, and switches Dynamics 365 off in 24–30 months. Pricing depends on scope, so we model it with your own numbers first.
Your renewal checklist
- Find your renewal date and reduction rights for each SKU, 12 months out.
- Reconcile owned, required, and used licenses using the License Usage Summary.
- Redesign roles and move users down where the work allows, then test.
- Disable departed users and remove unused attach licenses and apps.
- Clean up storage, environments, add-ons, and retainers, with retention rules agreed.
- Open the renewal conversation at least 120 days out, with your right-sized count and price-protection asks.
- Decide which workflows to replace before the next term, not during it.
Where to go from here
Run your current and right-sized numbers through the model, then compare them with replacing your costliest workflows. If you'd like a second opinion before renewal, tell us what you run and what you pay, and we'll be honest about where the savings are. You can also see how a staged approach works on our Escape Dynamics 365 page.
Sources
- Microsoft: Enterprise Agreement licensing guidance
- Microsoft Learn: New commerce experience cancellation policy
- Microsoft Learn: Stay compliant with user licensing requirements
- Microsoft: Improved user license validation for Dynamics 365 finance and operations
- Microsoft: Dynamics 365 Licensing Guide (November 2026)
- ERP Research: Dynamics 365 Finance and Operations price list
- Microsoft Learn: Free up storage space
- Microsoft: New pricing for Dynamics 365, effective October 2024