Get Microsoft Licensing Intelligence
Join enterprise IT leaders receiving our monthly advisory on Microsoft licensing changes, EA negotiations, and cloud cost optimisation.
By Fredrik Filipsson · Microsoft Dynamics 365 Licensing · Updated February 2026 · ~28 min read
01 Dynamics 365 Licensing Models
Microsoft Dynamics 365 is a cloud-based CRM and ERP application suite whose licensing model is both modular and continually evolving. Understanding the core licensing models is the foundation for an effective cost-control strategy.
| Licensing Model | How It Works | Best Suited For | Approximate Cost |
|---|---|---|---|
| Per-User (Full User) | Named user subscription per specific app. Each user requires a licence for each D365 module they access. | Power users: sales reps, finance managers, service agents | CRM: ~$105/user/mo; ERP: ~$210/user/mo |
| Team Member | Low-cost licence for basic read and limited write access across all D365 apps. View data, update contacts, enter timesheets, create notes. | Executives viewing dashboards, HR submitting expenses, assistants with limited data-entry | ~$8/user/mo |
| Attach Licence | Discounted add-on for users who already hold a Full User licence. Provides identical functionality to a full licence at a fraction of the price. | Multi-role users: service manager needing Sales access, finance controller using Supply Chain | ~$20/user/mo |
| Operations Activity | Mid-tier ERP licence bridging Team Member and Full User. Allows approving invoices, updating inventory, workflow participation. | Warehouse supervisors, purchasing clerks, operations staff with defined transactional tasks | ~$50/user/mo |
| Per-Device | Licences a specific shared device (not a named user). Unlimited users can access D365 on that device. | Retail POS terminals, warehouse kiosks, factory floors, call centre workstations | Approximately equal to a Full User licence |
| Legacy Plan (Retired) | Bundled licences such as Customer Engagement Plan or Unified Operations Plan, retired by Microsoft in 2019 in favour of modular base-plus-attach. | Organisations grandfathered on old agreements. Should be reviewed at renewal. | Varies (often more expensive than current modular licensing) |
02 Bundling Strategies and the Base-Plus-Attach Model
The base-plus-attach licensing model is Microsoft's primary mechanism for controlling costs when users need access to more than one Dynamics 365 application. It replaced the retired bundled plans in 2019 and is now the standard approach for multi-app licensing.
How Base-Plus-Attach Works
Every user must have at least one "base" licence at the standard price. This is their primary app. Once a base licence is assigned, any additional Dynamics 365 apps for that user can be purchased as attach licences at ~$20/user/month, regardless of the app's full price. The attach licence provides identical functionality to a full licence.
Critical Rules for Base-Plus-Attach
| Rule | What It Means | Common Mistake to Avoid |
|---|---|---|
| Most expensive app must be the base | The first Dynamics app assigned to a user must be the highest-priced one they need. All cheaper apps are attached. | Assigning a CRM app ($105) as base when the user also needs an ERP app ($210). The ERP must be the base. |
| No limit on attach licences per user | A user can have one base plus multiple attaches: e.g., Finance (base) + Sales (attach) + Customer Service (attach) + Field Service (attach). | Purchasing multiple full licences for the same user instead of using the attach model. |
| Cannot mix Professional and Enterprise | You cannot have Sales Professional and Sales Enterprise users in the same environment. Choose one edition per app for the entire organisation. | Starting with Professional edition to save money, then discovering you cannot attach Enterprise-tier apps. |
| Tenant must have at least one Full User | You cannot run Dynamics 365 solely with Team Member licences. At least one full admin user is required. | Attempting to deploy Dynamics with only Team Member licences for a small pilot. |
Need Help Optimising Your Dynamics 365 Licence Mix?
Our independent advisory team identifies attach opportunities, shelfware, and compliance gaps across your Dynamics 365 estate.
03 Common Pitfalls in Enterprise Dynamics 365 Licensing
| Pitfall | What Happens | Risk | How to Avoid It |
|---|---|---|---|
| Duplicate entitlements | Users end up with two full licences for different apps when an attach licence would suffice, common when departments purchase in silos. | High | Centralise licence management; run reports to find users with multiple full licences. |
| Misclassified users | Power-user licences assigned to dashboard viewers; or Professional chosen when Enterprise features are needed later. | High | Conduct role-based analysis; map each role to minimum required licence tier. |
| Over-licensing (shelfware) | More licences purchased than users who actually log in; modules bought "just in case" go unused. | Medium | Track active vs. assigned users quarterly; reclaim licences from inactive accounts (90+ days). |
| Under-licensing | Users accessing Dynamics functionality without the correct licence through shared logins, wrong security roles, or missing Team Member restrictions. | Critical | Enforce licence-to-role mapping; use Azure AD groups for assignment; note Microsoft's increasing technical enforcement. |
| Not using attach model | Multi-app users carry two or more full-price licences instead of base + attach. | High | Policy: no user gets a second full licence without attach evaluation first. |
| Ignoring Team Member opportunities | All users given full licences out of simplicity, even those who only need read access. | Medium | Identify light users; assign Team Member licences where usage fits within limitations. |
| Multiplexing / indirect access | Custom portals or middleware funnel multiple users through a single licence, violating Microsoft's terms. | Critical | Every internal user who benefits from Dynamics data must be licensed; design integrations with licensing in mind. |
| Overlooking add-on costs | Exceeding included Dataverse storage, API call quotas, or add-on capacity generates unexpected charges. | Medium | Monitor capacity in Power Platform Admin Center; pre-purchase capacity rather than paying overage fees. |
04 Price Optimisation Strategies
Controlling Dynamics 365 costs is an ongoing discipline, not a one-time purchasing decision.
| # | Strategy | Expected Impact |
|---|---|---|
| 1 | Right-size licence types to user needs. Deploy a tiered licensing model. Not every user needs a $105 to $210 full licence. Switching dashboard-only users to Team Member at $8/month yields immediate savings. | Typically 15 to 25% reduction in per-user spend |
| 2 | Maximise attach licence adoption. Audit all users with multiple Dynamics apps and convert second/third licences to attach pricing at ~$20/month. | 10 to 20% cost reduction for multi-app deployments |
| 3 | Eliminate shelfware before renewal. Identify unassigned and inactive licences (90+ days no login). Reduce counts before entering renewal negotiations. | 5 to 15% reduction in total licence count |
| 4 | Consider Power Platform alternatives. For peripheral use cases, a Power Apps per-app licence may be cheaper than a full Dynamics licence, provided users do not access restricted Dynamics entities. | Variable; often $5 to $20/user/month savings for specific roles |
| 5 | Use volume licensing and long-term agreements. Enterprise Agreements (EAs) offer price locks and potential discounts for 3-year terms. CSP subscriptions offer flexibility at slightly higher unit cost. | 3 to 15% savings from commitment-based pricing |
| 6 | Reallocate before purchasing new. When new employees need access, first check for reclaimable licences from departed staff or completed projects. | Avoids incremental spend; maintains budget discipline |
| 7 | Monitor Microsoft promotions. Microsoft runs promotions for competitive migrations, bundle discounts, and new module adoption. Align timing with genuine needs to capture discounts. | 10 to 20% on new module rollouts when promotions align |
05 True-Up Management and Audit Exposure
Enterprises licensing Dynamics 365 through multi-year Enterprise Agreements face annual true-up obligations and potential compliance audits.
How True-Ups Work
Under an EA, you commit to a licence count for a 3-year term. Each year at the anniversary, you report any additional licences added beyond your initial commitment. This is the true-up. Crucially, EAs do not allow reducing licence counts mid-term. Even if usage drops, you pay for the original quantity until renewal. This makes accurate forecasting and active management essential.
Audit Exposure
Microsoft (and its partner auditors) have the right to audit your compliance with licence terms. Cloud telemetry means Microsoft already has visibility into usage patterns. Audits increasingly focus on licence misclassification, multiplexing, and under-licensing rather than simple headcount. Key audit triggers include unassigned active users, excessive use of features beyond licence entitlement, and suspected indirect access scenarios.
06 Renewal Management
The renewal of your Dynamics 365 agreement is the most important commercial moment in your Microsoft relationship. Begin preparations 6 to 12 months in advance.
| Renewal Step | Key Actions | Timing |
|---|---|---|
| Assess current usage | Review all licence types, active user counts, and shelfware. Identify excess that can be cut and underserved areas that need expansion. | 12 months before |
| Forecast future needs | Collaborate with business units to project D365 user counts and module requirements. Factor in new projects, divestitures, and workforce changes. | 9 to 12 months before |
| Review pricing and product changes | Check the latest Microsoft Dynamics 365 Licensing Guide for pricing updates, new SKUs, and retired offerings. | 6 to 9 months before |
| Identify expiring discounts | If your current agreement includes introductory or promotional discounts, these may expire at renewal. Plan to negotiate extensions or tapering strategies. | 6 months before |
| Coordinate with other Microsoft renewals | If D365 is part of a broader EA (with M365, Azure), negotiate holistically. Microsoft considers the full relationship when structuring deals. | 6 months before |
| Initiate renewal discussions | Contact Microsoft or your reseller. Express intent to review and optimise. Early engagement prevents deadline pressure, which always favours the vendor. | 4 to 6 months before |
07 Negotiation Levers and Best Practices
Microsoft expects enterprise customers to negotiate. List price is a starting point, not the final number.
| Lever | How to Use It | Expected Impact |
|---|---|---|
| Competitive benchmarking | Obtain quotes from Salesforce (CRM) or SAP (ERP) and present them credibly. Even if committed to Dynamics, Microsoft sales teams respond to competitive pressure. | 5 to 15% additional discount on contested modules |
| Full Microsoft relationship leverage | Bundle Dynamics negotiation with M365, Azure, and Power Platform. A holistic deal gives Microsoft account teams more room for cross-product discounts. | Variable; often unlocks concessions unavailable on standalone deals |
| Timing to fiscal calendar | Microsoft's fiscal year ends June 30, with quarter-ends in March, June, September, December. Aligning renewal with quarter-end gives sales reps urgency to close. | Quarter-end deals routinely yield 10 to 20% better terms |
| Multi-year commitment | A 3-year EA demonstrates loyalty and gives Microsoft revenue predictability. Use this as leverage for deeper discounts. | 3 to 10% discount for commitment length |
| Escalation to Microsoft leadership | If negotiations stall with your account team, escalating to regional or segment leadership can unlock additional discount authority. | Often the difference between a standard and exceptional deal |
| Flexibility and growth promises | If planning to expand Dynamics usage (new modules, more users), offer this growth commitment in exchange for better pricing on existing licences. | 5 to 15% on existing licences in exchange for growth commitment |
Navigating a Dynamics 365 Renewal or Negotiation?
Our independent advisory team helps enterprises optimise Dynamics 365 licensing, negotiate EA renewals, and eliminate compliance risk. We work exclusively in your interest, never for Microsoft.
08 Governance and Power Platform Integration
Dynamics 365 does not exist in isolation. It sits within the broader Microsoft ecosystem alongside Power Platform, Microsoft 365, and Azure. Effective governance requires understanding the licensing interactions between these products.
Power Platform Licensing Interactions
Dynamics 365 licences include certain Power Platform entitlements, such as the right to use Power Apps and Power Automate within the context of the Dynamics app. However, if users build Power Apps or Power Automate flows that access Dataverse tables outside of their licensed Dynamics 365 app, additional Power Platform licences may be required. This is a frequent compliance gap that catches organisations by surprise.
| Governance Area | Recommended Practice |
|---|---|
| Licence ownership | Assign a licensing manager or team with cross-functional authority. Dynamics licence decisions should not be made by individual departments in silos. |
| Quarterly usage reviews | Run reports showing active vs. assigned licences, inactive users, and users with multiple licences. Review in a governance committee meeting. |
| Request approval workflow | Implement an internal approval step for new licence requests. A licensing specialist should verify attach eligibility before any new full licence is purchased. |
| Admin training | Train Dynamics admins on attach licensing, Team Member limitations, and the consequences of misassignment. Frontline awareness prevents most pitfalls. |
| Storage and capacity monitoring | Monitor Dataverse storage consumption, API call quotas, and add-on capacity in the Power Platform Admin Center. Set alerts before you hit limits. |
| Integration compliance | Document all Power Platform and third-party integrations with Dynamics data. Verify that every user accessing Dynamics data, even indirectly, is properly licensed. |
09 CIO Checklist: 7 Actions to Take
Map Roles to Licence Types
Conduct a role-based analysis of your entire user base. Determine which users need Full licences (power users), which can use Team Member or Activity licences (light users), and which shared workstations qualify for Device licences.
Audit for Duplicate and Unused Licences
Run a report of all Dynamics 365 licence assignments. Flag any user with two or more full licences (convert to attach), any unassigned licences, and any user who has not logged in for 90+ days. Reclaim and reduce immediately.
Implement the Attach Model Organisation-Wide
Make it policy that no user receives a second full-price Dynamics licence without first evaluating the base-plus-attach model. Educate IT admins on how to assign attach licences correctly.
Establish Governance and Quarterly Reviews
Create a licensing governance committee with representatives from IT, finance, and procurement. Review usage reports quarterly, identify optimisation opportunities, and maintain a year-round licence tracker for true-up accuracy.
Prepare for Renewal 6 to 12 Months Early
Assess current usage, forecast future needs, identify expiring discounts, and coordinate with other Microsoft renewals. Build a renewal dossier documenting what you need and what you are willing to pay.
Address Compliance Gaps Proactively
Reconcile active users against licences quarterly. Ensure no Team Member users have access to restricted features. Document integration architectures and verify Power Platform licensing compliance.
Engage Independent Licensing Expertise
For large or complex environments, have an independent licensing expert perform a health check. They can spot duplicate entitlements, misclassified users, and negotiation opportunities that internal teams typically miss.
Frequently Asked Questions
The base-plus-attach model is Microsoft's standard approach for licensing users who need multiple Dynamics 365 apps. Each user must have one "base" licence (their primary app) at full price. Any additional D365 apps for that user can be purchased as "attach" licences at approximately $20/user/month, regardless of the additional app's full price. This provides identical functionality at a fraction of the cost. The most expensive app must always be assigned as the base.
Dynamics 365 pricing varies by application and licence type. CRM Enterprise apps (Sales, Customer Service, Field Service) cost approximately $105/user/month. ERP Enterprise apps (Finance, Supply Chain Management) cost approximately $210/user/month. Team Member licences cost approximately $8/user/month. Operations Activity licences cost approximately $50/user/month. Attach licences for additional apps cost approximately $20/user/month. Microsoft increased CRM prices by 11% and ERP prices by 17% in October 2024.
A Team Member licence (~$8/user/month) provides basic read and limited write access across Dynamics 365 apps. Users can view data, update contacts, enter timesheets, create notes, and access dashboards, but cannot execute core business processes like closing sales opportunities, posting financial transactions, or accessing advanced features. Ideal for executives who only need reporting access, administrative staff with minimal data-entry needs, and employees who primarily consume rather than create data.
No. You generally cannot mix Professional and Enterprise editions of the same app in the same environment. For example, you cannot have some users on Sales Professional and others on Sales Enterprise within a single CRM instance. Your organisation must choose one edition per app. Additionally, attach licences typically apply to Enterprise editions. If you choose a Professional licence as the base, you usually cannot attach an Enterprise app. Most large enterprises opt for Enterprise editions to access full features and use the attach model for cost control.
Under an Enterprise Agreement (EA), you commit to a licence count for a 3-year term. At each annual anniversary, you report any additional licences added beyond your initial commitment. This is the true-up. You pay a prorated amount for those additions, and they are added to your baseline going forward. EAs do not allow reducing licence counts mid-term: even if usage drops, you pay for the original quantity until renewal. This makes accurate forecasting and proactive licence management essential.
Each Dynamics 365 subscription includes a base allocation of Dataverse database storage, file storage, and log storage, plus incremental capacity per user licence. If your data grows beyond these limits, you must purchase additional capacity, typically around $40/GB/month for database storage. Monitor consumption in the Power Platform Admin Center and set alerts before you approach limits. It is generally cheaper to pre-purchase additional storage capacity or negotiate it into your EA than to pay overage fees.
Multiplexing, using middleware, service accounts, or custom portals to let multiple internal users access Dynamics 365 through fewer licences than actual users, is explicitly prohibited by Microsoft's licensing terms. If ten employees feed data into Dynamics via a single service account, all ten must be individually licensed. Microsoft's compliance teams specifically look for multiplexing scenarios during audits. The remedy is typically forced purchase of back-dated licences at list price with no discounts.
The most effective levers are: competitive benchmarking (obtain quotes from Salesforce or SAP to create pricing pressure), timing your negotiation to Microsoft's quarter-end (March, June, September, or December), bundling Dynamics with your broader Microsoft spend (M365, Azure) for cross-product concessions, committing to multi-year terms in exchange for deeper discounts, and escalating to Microsoft leadership if your account team's discount authority is exhausted.
📚 Related Reading
CIO Playbook: Microsoft Dynamics 365 Licensing → Dynamics 365 Licensing and Renewals: A CIO's Playbook → CIO Playbook: Dynamics 365 Licensing Strategy → Dynamics 365 Licensing Metrics and Models → Licensing Dynamics 365 CRM & ERP Applications → Microsoft Licensing Trends 2025-2026 → Key Changes in Microsoft Licensing → Managing Microsoft Cloud Agreements & Subscriptions →Microsoft Contract Negotiation
Service
Microsoft EA Optimisation
Service
Microsoft Audit Defence
Service
Microsoft Optimisation Services
Service
SPLA Audit Defence
Service
Microsoft Knowledge Hub
Knowledge Hub
Optimise Your Dynamics 365 Licensing
Approaching a Dynamics 365 renewal, licence review, or compliance assessment? Redress Compliance provides independent advisory with current benchmark data, pricing intelligence, and negotiation expertise. Also managing Oracle, SAP, Salesforce, or Broadcom contracts? We cover all major vendors.