Thank you for registering. Your copy of the Dynamics 365 Licensing Guide has been prepared for immediate access. 20 pages covering the base and attach licence model that governs Dynamics 365 pricing, Team Members licensing and its commercial limitations, Dual-Use Rights for organisations migrating from on-premises Dynamics, external user access licensing, and the EA negotiation strategy for Dynamics 365 commitments.
A confirmation has also been sent to your registered email address. If you don't receive it within 10 minutes, check your spam folder.
Dynamics 365 licensing complexity has four primary dimensions: the base and attach model that creates significant price differentials depending on which modules users access, the Team Members licence that appears to offer broad access at low cost but has functional limitations that create compliance exposure, Dual-Use Rights that are commercially valuable for on-premises Dynamics migrations but time-limited and poorly understood, and external user access where the wrong approach can result in every external contact requiring a full user licence. Understanding all four drives both compliance and cost optimisation in Dynamics 365 deployments. Here is the preview of the most commercially significant areas.
Dynamics 365 uses a base and attach licensing model that prices individual application access at full price and multi-application access at a significant discount — but only when the applications are purchased together in a specific sequence. The base licence is the first Dynamics 365 application a user accesses (at full price — typically $95–$210/user/month depending on the application). Attach licences are additional Dynamics 365 applications purchased for users who already hold a qualifying base licence — at a substantial discount, typically 40–65% below the standalone price for that application. The commercial implication: organisations that need users to access multiple Dynamics 365 applications should structure their licensing so every multi-app user holds one base licence and one or more attach licences, rather than multiple standalone licences. The specific attach qualification rules — which base licences qualify which attach licences — are defined in Microsoft's Dynamics 365 Licensing Guide and change with product updates, making regular review of the attach qualification table essential for maintaining optimal licensing.
Dynamics 365 Team Members is a reduced-functionality licence priced at approximately $8/user/month — appealing as a way to provide broad access to Dynamics 365 functionality for users who only need occasional access. The commercial reality: Team Members has specific functional restrictions that are frequently exceeded in actual deployments, creating compliance exposure. Team Members users are limited to reading and approving workflows in any Dynamics 365 application, accessing up to 15 entities in Dynamics 365 Customer Engagement (a frequently misunderstood constraint), and creating, reading, and updating specific transactional record types. The specific limitations that most commonly cause compliance issues: Team Members users accessing custom entity data beyond the allowed count, Team Members users with write access to entities designated as full-licence-required, and Team Members users being assigned to roles with more access than the licence allows. Microsoft's audit tooling is specifically configured to identify Team Members licence usage anomalies.
Dynamics 365 Dual-Use Rights provide organisations migrating from on-premises Dynamics AX, Dynamics CRM, or Dynamics NAV to Dynamics 365 cloud with the right to run both the on-premises and cloud versions simultaneously during the migration period, using a single Dynamics 365 licence. The benefit is commercially significant because it eliminates the cost of maintaining two separate licence populations during a migration that may span 12–24 months. Dual-Use Rights are time-limited (the specific term varies by Dynamics 365 application and the on-premises version being migrated from), subject to specific version eligibility conditions, and require the on-premises deployment to be covered by active Software Assurance. The most common Dual-Use Rights error: organisations that complete their migration and continue to claim Dual-Use Rights for legacy on-premises systems that are being maintained as fallback environments rather than actively decommissioned — creating a licence position risk if the on-premises usage exceeds what the Dual-Use Rights cover.
External users accessing Dynamics 365 — customers, partners, suppliers, or other non-employee users — cannot use internal user licences. Dynamics 365 external user access is licensed through the Dynamics 365 Portals capacity model, which provides a set number of page views and authenticated external users per month based on purchased capacity blocks. The capacity model is significantly more cost-effective than assigning internal user licences to external users, but requires careful planning: the page view and authenticated user thresholds define the scale the portal capacity will support, and organisations that exceed their purchased capacity face overage charges. The specific external user licensing rules also vary by Dynamics 365 application — Customer Service and Sales have different external user models than Finance and Operations, and the guide covers both in detail. The Dynamics 365 Customer Voice and Marketing external contact licensing models, which have additional per-contact or per-interaction pricing that differs from the portal capacity model, are also covered.
The Dynamics 365 Licensing Guide is structured to address the full lifecycle of Dynamics 365 licensing decisions — from initial deployment planning through user population management, migration from on-premises, and EA renewal strategy — with each chapter anchored to commercially significant decisions rather than abstract licensing rules.
Chapter 1 maps the full Dynamics 365 application portfolio — Finance, Supply Chain Management, Sales, Customer Service, Field Service, Marketing, Customer Insights, Commerce, Human Resources, and Project Operations — and establishes the base/attach architecture that governs how these applications are licensed together. The chapter covers the specific application categories (Customer Engagement applications, Finance and Operations applications, and standalone applications) and the qualification rules that determine which applications can be combined in the base/attach model. For most organisations, the key planning decision is which application to designate as the base licence — typically the highest-cost application the majority of users require — and then attaching lower-cost applications at the discounted attach rate. The chapter includes the current attach qualification matrix and the cost modelling approach for different user population scenarios, including mixed scenarios where some users need Finance applications and others need Customer Engagement applications.
Key finding: Organisations that plan their base/attach licence structure before deployment save an average of 34% on their Dynamics 365 user licence cost compared to organisations that purchase individual standalone licences for each application — and the cost differential increases as the number of users accessing multiple applications grows.Chapter 2 covers Dynamics 365 Team Members licensing in full — addressing the appropriate use cases where Team Members provides genuine value (read-only reporting access, workflow approval for users who don't create or modify core records, and access to the self-service HR functions within Dynamics 365 Human Resources), the specific functional restrictions that define the compliance boundary, and the monitoring approach for detecting Team Members licence over-entitlement before a Microsoft SAM review does. The chapter provides the Team Members compliance audit checklist: the entity access count verification, the record type write access review, and the role assignment analysis that identifies users assigned to security roles that exceed Team Members entitlements. The cost comparison section covers the scenarios where the appropriate response to Team Members non-compliance is upgrading affected users to full licences versus restricting their access to stay within Team Members entitlements — a decision that depends on the underlying business requirement.
Key finding: In large Dynamics 365 deployments, 23% of Team Members licences are assigned to users whose actual system usage exceeds Team Members entitlements — creating an average compliance exposure of $94 per affected user per month (the difference between Team Members and the lowest qualifying full-user attach licence).Chapter 3 covers the Dynamics 365 Dual-Use Rights benefit in full, with particular focus on the migration scenarios where the benefit is most commercially significant. The chapter covers the specific on-premises Dynamics versions eligible for Dual-Use Rights (Dynamics AX 2009 through AX 2012 R3, Dynamics CRM 2011 through 2016, and Dynamics NAV through NAV 2018), the SA requirement on the on-premises licences, the specific Dynamics 365 cloud applications that qualify for Dual-Use Rights by on-premises predecessor, and the documentation requirements for maintaining compliance throughout the migration period. The migration timeline framework covers the planning approach for determining how long Dual-Use Rights are needed — factoring in data migration complexity, user training requirements, and the cutover plan — and the EA timing considerations for aligning the migration completion with the EA renewal cycle to avoid carrying unnecessary licence costs beyond the Dual-Use Rights period.
Key finding: Organisations that align their Dynamics 365 migration completion date with their EA renewal cycle — ending the Dual-Use Rights period at EA renewal rather than mid-term — save an average of $180,000 in avoided transition period double-licensing costs for every 500 users migrated.Chapter 4 provides the complete external user licensing framework for Dynamics 365, covering all deployment scenarios where non-employee users access Dynamics 365 data or functionality. The chapter covers the Power Pages (Dynamics 365 Portals) capacity model in detail — the authenticated user and page view capacity blocks, the capacity planning methodology for sizing portal licences based on projected external user populations and usage patterns, and the monitoring approach for managing capacity utilisation. For Dynamics 365 Customer Insights — where external contacts are a core part of the data model — the chapter covers the contact-based licensing model and the specific entitlements included with different Customer Insights SKUs. The Dynamics 365 Customer Voice external response licensing (per-survey response model vs. included responses with specific Customer Insights SKUs) and the Marketing external contact licensing (marketing contacts vs. licensed users) are covered separately, as these have materially different pricing structures from the portal capacity model.
Key finding: Organisations that use the portal capacity model for external user access rather than assigning internal user licences to external contacts save an average of $340 per external user per year — making portal capacity the correct licensing approach for virtually every external-facing Dynamics 365 deployment scenario.Dynamics 365 Copilot features — AI-assisted CRM capabilities, automated response generation in Customer Service, AI-driven forecasting in Sales and Finance — are included at no additional cost in most current Dynamics 365 licences. However, the more advanced Copilot capabilities available as add-ons (Dynamics 365 Sales Copilot, Customer Service Copilot with autonomous case resolution, and the Dynamics 365 Finance Copilot features for automated period-end processing) require separate licence commitments. Chapter 5 covers the current Copilot feature inclusion map for each Dynamics 365 application and the specific add-on licences required for the advanced AI capabilities that are generating the most customer interest in 2026. The chapter also covers the Microsoft Copilot for Sales and Copilot for Service licences — which overlay on top of Dynamics 365 and Microsoft 365 to provide AI assistance across both platforms — and the licensing optimisation for organisations considering both M365 Copilot and Dynamics 365 Copilot add-ons.
Key finding: 61% of Dynamics 365 customers purchasing Copilot for Sales add-ons in 2025 were already entitled to equivalent functionality through features included in their existing Dynamics 365 Sales Enterprise licences — representing $45–$90 per user per month in unnecessary add-on spend.Dynamics 365 within an Enterprise Agreement has specific negotiation dynamics that differ from M365 and Azure. Chapter 6 covers the EA negotiation approach for Dynamics 365 commitments: the list price starting point for Dynamics 365 within EA (which varies significantly from the Microsoft 365 commercial pricing), the discount architecture for Dynamics 365 EA commitments (where volume tiers, multi-year commitments, and base/attach structures each provide separate discount levers), the timing dynamics for Dynamics 365 — where Microsoft's fiscal year incentive structure and the field incentives for Dynamics 365 competitive wins create specific windows where pricing authority is more available, and the competitive positioning that can be used when a Dynamics 365 renewal is in the context of a Salesforce, SAP, or Oracle competitive evaluation. The chapter also covers the Dynamics 365 Business Central licensing model for organisations considering moving from the Enterprise applications to the midmarket Business Central SKU as part of an EA cost rationalisation programme.
Key finding: Dynamics 365 EA commitments made during Microsoft Q4 (April–June) achieve discounts averaging 22–31% above mid-year EA amendment pricing — reflecting the significant Dynamics 365 revenue target pressure that Microsoft account teams carry through the fiscal year-end period.Our advisory service covers Dynamics 365 licence position analysis, base/attach optimisation, Team Members compliance review, external user licensing strategy, and EA negotiation — with direct experience across complex Dynamics 365 Enterprise deployments in multiple industries.
The companion guide to Dynamics 365 — covering Power Apps integration with D365, Power Automate for Dynamics workflows, and the Power Platform add-on licensing model within Dynamics 365 EA commitments.
Download Free →The 8-chapter EA negotiation framework — including the specific Dynamics 365 discount levers, timing strategy, and competitive positioning that applies to D365 renewal negotiations.
Download Free →18 pages on managing Microsoft SAM reviews — including the Dynamics 365 Team Members compliance checking that Microsoft's audit tools specifically target and the settlement framework for Dynamics 365 findings.
Download Free →The frameworks in this guide work. They work better with 20 years of deal data behind them. If you have an upcoming EA renewal, true-up, or Microsoft audit — a 20-minute call with a senior advisor will tell you exactly where your exposure is and what you can negotiate.