Licensing updates for Dynamics 365 in 2026

Microsoft Dynamics 365 licensing has evolved continuously since the product family launched in 2016. The current shape — base licences, attach licences, Copilot bundles, premium tiers — is more complex than first-time buyers expect. This article summarises the patterns as of 2026 and the considerations for licence planning.

The base licence model. Each user gets one base licence that grants full access to one Dynamics 365 app:

• Sales Enterprise — base for sales users.
• Customer Service Enterprise — base for service.
• Field Service — base for field service.
• Finance — base for finance users.
• Supply Chain Management — base for SCM users.
• Project Operations — base for project work.
• Business Central — base for SMB ERP.
• Customer Insights — Data and Journeys, separate SKUs.

The full price applies to the first licence per user.

Attach licences. Users needing access to additional apps get discounted attach licences:

• Roughly 50% of base.
• One base + multiple attach per user.
• The base is the highest-priced app needed.

A finance manager who also uses Sales: Finance (base) + Sales (attach).

Premium tiers.

• Sales Premium — adds Conversation Intelligence, predictive features.
• Customer Service Premium — adds AI features.
• Some apps have multiple tiers (Standard, Enterprise, Premium).

Premium pricing significantly higher than Enterprise; only worth it if AI features are genuinely used.

Copilot bundles. As of 2025–2026:

• Many AI features moved from per-licence to bundled with Premium tiers.
• Microsoft 365 Copilot separately licensed.
• Some scenarios require both Dynamics Copilot bundled AND M365 Copilot.

The Copilot landscape is the area most actively evolving; consult current Microsoft guidance.

Device licences. For specific scenarios:

• Operations Device — for shared shop floor terminals.
• Activity — limited transaction-based access.

Device licences trade per-user flexibility for shared-device cost efficiency.

Team Member licences. A small, cheap licence for limited access:

• Read most data.
• Update a few specific scenarios (time entry, expenses).
• Approve workflows.
• Limited create/update rights.

The Team Member licence has tightened over the years — historically generous, increasingly restricted. Always verify current Team Member rights for your scenario.

External user licences.

• Power Pages capacity — for customer / partner portals; per-authenticated-user or per-page-view.
• Entra External ID — for B2C auth.

For high-volume customer-facing scenarios, capacity licences can be significant.

Business Central licence model (different from CE/F&O).

• Essentials — smaller SMB tier.
• Premium — adds Service Management, Manufacturing.
• Team Member — limited access.

Business Central pricing is generally lower per user than F&O; SMB-friendly.

F&O specifics.

• Activity user — limited functions.
• Self-service user — even more limited.
• Operations Device — shared.

Plus the standard full user. F&O licensing is granular; legal entity scope, server count, and other factors play in.

Storage and capacity.

• Dataverse storage — Database, File, Log.
• Per-licence allocation — base licences contribute storage entitlement.
• Overage — additional purchased capacity.
• AI Builder credits — for AI prompts and models.
• Power Automate capacity — for premium connectors and large-scale flows.

Storage is metered; large tenants outgrow base allocation and need top-up.

Power Apps and Power Automate.

• Standalone Power Apps — per-app or per-user.
• Premium connectors require premium tier.
• Power Apps included with Dynamics licences for Dynamics-related scenarios.

The "what's included" question is nuanced and shifts. Get specific licensing guidance per scenario.

Industry accelerators / templates.

• Healthcare Cloud, Retail Cloud, Sustainability — Microsoft industry clouds bundling Dynamics + adjacent products.
• Different pricing models per industry cloud.

For industry-specific deployments, evaluate industry cloud vs piecing together components.

Volume discounts.

• Enterprise Agreement (EA) — large-customer discount tiers.
• CSP (Cloud Solution Provider) — partner-resold; flexible commitment.
• Direct online — list price, simpler procurement.

For organisations with 100+ Dynamics users, EA or CSP discounts are material.

Free trials. Most apps offer 30-day trials; useful for evaluation, not for long-term cost reduction.

Common licensing pitfalls.

• Wrong base licence. Users with Sales as base but heavier Finance usage; should have Finance base.
• Premium when Enterprise suffices. Paying for AI features that aren't adopted.
• Team Member abuse. Trying to use Team Member for full-user activities; non-compliant.
• External users not licensed. Customer portal users without correct capacity licences.
• Capacity underestimated. Tenant grows; storage overruns trigger surprise costs.
• Copilot complexity. Multiple Copilots; unclear which licences cover which features.

Operational guidance.

• Annual licence true-up. Review usage; adjust quantities.
• Quarterly review for fast-growing teams. Avoid surprise non-compliance.
• License management tool. Microsoft provides admin centre views; third-party tools (NetSpring, others) help at scale.

Strategic positioning. Licence cost is significant — typically multiple percent of total cost of ownership over 5 years. Optimisation isn't about finding cheaper licences but about picking the right licence per user role:

• Full users get base + appropriate attach.
• Limited users get Team Member or activity licences.
• External users get the right Power Pages or external ID capacity.
• Premium tiers reserved for genuine AI adoption.

A licence audit every 12 months catches drift; significant savings are common from rightsizing. Microsoft's licensing publishes are extensive but moving; involve specialists for complex scenarios. Don't accept the partner's first proposal without challenging the licence assumptions — meaningful savings often available with care.