فا
MSLicenseHub
cloud · reference
💼

Microsoft Dynamics 365

Dynamics 365 — modular cloud ERP and CRM, licensed per user per app with base + attach pricing.

Before licensing Microsoft Dynamics 365

01Business app02User role03Access rights
Microsoft Dynamics 365 · licensing decision diagram, not a product screenshot

Select the exact Dynamics 365 application and role. Full-user, Team Members, device and attach licensing have different eligibility and use rights; a Team Members licence is not unrestricted access to every app. Check indirect access, capacity and regional availability in the current licensing guide.

Confirm against official Microsoft sources

Licensing terms and guides · Product lifecycle directory

Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.

Editions covered
6
Edition matrix with feature differences and the right audience.
In-depth sections
7
Channels, activation, audit, modern management & more.
FAQs answered
5
Common questions buyers and IT admins ask before purchase.
Words of reference
0.7k
Edition and deployment guidance; verify current rights against official sources.
Edition matrix

Pick the right edition

Each edition targets a specific scale and feature set. Match the workload, not the price tag.

Edition 1
Sales Enterprise / Premium

CRM core. Premium adds conversation intelligence and Sales Copilot.

Edition 2
Customer Service Enterprise

Case management, omnichannel, knowledge base, unified service desk.

Edition 3
Field Service

Work orders, scheduling, mobile, IoT-triggered service.

Edition 4
Finance / Supply Chain / Commerce / HR / Project Operations

Enterprise ERP modules. Per user per app, base + attach.

Edition 5
Business Central Essentials / Premium

SMB ERP. Essentials covers finance and inventory; Premium adds manufacturing and service management.

Edition 6
Team Members

Light user. Read + limited write. Cannot do transactional work.

Side-by-side

Edition comparison

Compare the stated edition details. An omitted capability is not evidence that a feature is unavailable; verify the exact release in Microsoft's documentation.

CapabilitySales Enterprise / PremiumCustomer Service EnterpriseField ServiceFinance / Supply Chain / Commerce / HR / Project Operations
Edition and licensing notesCRM core. Premium adds conversation intelligence and Sales Copilot.Case management, omnichannel, knowledge base, unified service desk.Work orders, scheduling, mobile, IoT-triggered service.Enterprise ERP modules. Per user per app, base + attach.
Deep dive

Microsoft Dynamics 365 — what to actually know

Dynamics 365 is Microsoft's modular business application suite — Sales, Customer Service, Field Service, Customer Insights (formerly Marketing), Finance, Supply Chain Management, Commerce, Human Resources, Project Operations and Business Central. Each app is licensed per user per month and shares the underlying Microsoft Dataverse platform, which means data flows between apps natively and the same security model applies across the suite. The licensing model is intentionally modular: pay only for the apps each user actually uses, with steep discounts on additional apps for the same user.

01

First app vs subsequent apps — the base + attach model

Microsoft prices the first qualifying app at the higher 'base' rate. Additional apps for the same user are sold as 'attach' licences at a steep discount — often 60–70% off the base price. The catch: only some apps qualify as a base (the major ones — Sales Enterprise, Customer Service Enterprise, Field Service, Finance, Supply Chain, Commerce, Human Resources, Project Operations), and the attach pricing only applies to that same user. If a user needs Sales as their base and Customer Service as an attach, the maths works out; if you want to license two different teams on two different bases, neither team gets the attach discount unless individual users happen to need both apps.

02

Business Central vs Finance + Supply Chain Management

Business Central is the SMB ERP — designed for companies up to roughly 300 employees and a few hundred million in revenue, with a unified accounting, inventory, sales and purchasing platform. Finance + Supply Chain Management (often sold together as 'Finance & Operations') is the enterprise ERP, built for multi-entity, multi-currency, multi-country deployments with complex manufacturing, advanced financial consolidation, dual-write integration to the rest of Dynamics 365, and large finance teams. The two products are not interoperable migration paths — moving from Business Central to Finance + Supply Chain is effectively a re-implementation. Pick correctly the first time based on five-year growth expectations rather than current size.

03

Sales, Customer Service and Field Service

Sales is the CRM core — accounts, contacts, opportunities, leads, forecasting, and the relationship-intelligence features that surface activity history and next-best-actions. Sales Premium adds AI-driven conversation intelligence (transcription of sales calls, sentiment analysis) and Microsoft Sales Copilot. Customer Service handles case management, knowledge base, omnichannel routing (email, chat, voice, SMS, WhatsApp), and the unified service desk. Field Service adds work-order management, scheduling and dispatch, mobile technician apps, IoT-triggered service requests and inventory tracking on vehicles. Customer Insights (Journeys + Data) is the rebuilt marketing automation product, with real-time customer journey orchestration replacing the previous outbound-marketing module.

04

Team Members licence — and what it can and cannot do

A reduced-cost SKU for light users — read-only access to most data plus a few approval scenarios (timesheet entry, expense approval, knowledge consumption, project task updates). Team Members cannot replace full-app users for transactional work; Microsoft enforces this in the platform with hard-coded restrictions on creating accounts, opportunities, work orders, journal entries and other transactional records. The Team Members licence is genuinely useful — every employee in an organisation can have one for self-service tasks like timesheets and expense submission — but do not over-rely on it for case management or sales scenarios where full licences are required.

05

Power Platform integration and Dataverse

Every Dynamics 365 app stores its data in Microsoft Dataverse — the same database that backs Power Apps, Power Automate and Power BI Pro reports. That means a Dynamics 365 deployment includes a meaningful Power Platform footprint by default: you can build custom Power Apps on top of the Dynamics data model, automate workflows with Power Automate, and produce dashboards with Power BI without needing a separate database. Power Apps Per App and Per User licences extend the platform for custom applications that are not part of Dynamics 365 itself.

06

Copilot for Dynamics 365

Microsoft has added Copilot capabilities across Dynamics 365 — Sales Copilot, Customer Service Copilot, Finance Copilot, Field Service Copilot. Some are included in the base app licences (sales email summarisation, case-resolution suggestions); others are sold as add-ons (Microsoft Sales Copilot stand-alone for organisations whose CRM is not Dynamics, advanced financial planning Copilots). Read the SKU licensing guide carefully — the Copilot inclusion story varies by app and by base / attach status.

07

Implementation partners and the buying journey

Dynamics 365 is almost always sold and implemented through a Microsoft partner rather than directly — the product is configurable enough that a partner-led implementation (data migration, process configuration, custom development on the Power Platform, training) is the norm. Microsoft FastTrack provides architectural guidance for larger deployments but is not a substitute for implementation services. Plan implementation budgets at one to three times the annual licence cost for the first year for SMB deployments, and significantly more for enterprise Finance + Supply Chain projects.

By channel

Where to buy this product

Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.

Evidence to request

  • Exact product, edition, version and licence quantity.
  • Order, invoice and applicable agreement or subscription record.
  • Ownership in your organisation's account, where applicable.
  • Written reassignment, renewal and support conditions.

OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.

Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline

Lifecycle phases to plan against

Cloud SKUs change pricing, naming and bundling more often than any other Microsoft product line. Buy through a CSP partner who tracks the changes, and re-baseline your plan at every renewal — the right SKU last year is rarely the right SKU today.

Phase 1
Public preview
Variable

New SKUs and features land in preview first. Production use is at your own risk; SLAs do not apply.

Phase 2
General availability
Launch

Full SLA, full support, included in the relevant bundles. Pricing announced and stable for the contract term.

Phase 3
Continuous innovation
Ongoing

Quarterly to monthly feature drops. Read the Message Center and roadmap — opt-out windows are short.

Phase 4
Deprecation
Check service notice

Review product-specific retirement and service-change notices. Notice periods depend on the service, policy and agreement; a universal one-year period is not assumed.

Purchase preparation

What to include in a Microsoft Dynamics 365 quote request

Service
Exact application and subscription plan.
Users
Named users, roles and any device-based requirements.
Account
Tenant ownership, region and existing subscriptions.
Contract
Commitment duration, renewal and cancellation conditions.

These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.

Compare like-for-like quotations
  • Match product, edition, version, quantity and perpetual or subscription terms.
  • Confirm total cost, renewal conditions and the evidence of ownership supplied.
  • Obtain written delivery, refund and support conditions before payment.
Official product licensing guide
Request a quote
Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

DO

Buy through a CSP and put the tenant in your own name, not the partner's.

DON'T

Let a partner host your tenant on their domain — you will not be able to move workloads or providers cleanly.

DO

Match SKU to role: F-series for frontline, Business for SMB up to 300 seats, E-series for enterprise, A-series for education.

DON'T

Buy E5 for everyone reflexively — most users do not need Defender for Endpoint P2, Purview and Entra P2 simultaneously.

DO

Use group-based licensing in Entra ID so SKUs follow the role, not the individual.

DON'T

Hand-assign licences from the admin centre — the manual drift is impossible to audit at scale.

Typical deployments

How buyers actually use Microsoft Dynamics 365

Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.

Scenario 1
SMB end-to-end

Microsoft 365 Business Premium — Office, Teams, Exchange, SharePoint, Intune, Defender for Business and Entra ID P1 in one subscription, capped at 300 seats.

Scenario 2
Mid-market and enterprise

M365 E3 baseline for most users, E5 for the security/compliance and analyst personas who actually use Purview and Defender P2.

Scenario 3
Frontline + corporate mix

F1/F3 for shop-floor and field staff, E3/E5 for HQ. Same tenant, different SKUs assigned by Entra groups.

Cost optimisation

Where the savings actually live

Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.

💰
Annual commitment vs monthly

Compare current annual and monthly quotations, commitment duration, billing frequency and cancellation windows. Do not assume a fixed discount or that monthly billing means a monthly commitment.

📊
Reserved instances for steady Azure workloads

1- or 3-year RIs cut compute and database costs by 30–60% versus pay-as-you-go for workloads that run continuously.

🎯
Decommission ghost seats quarterly

Leaver accounts that still hold a paid licence are the single biggest waste in most M365 tenants — automate the reclaim.

Counterfeit & risk

Red flags when buying second-hand

These warning signs require further verification; activation alone cannot establish licence ownership.

⚠ 01
Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is not an eligible standalone purchase; request documented rights through an appropriate channel.

⚠ 02
Lifetime key with no invoice or Microsoft 365 admin center volume licensing record

Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.

⚠ 03
Key works once, then 'not genuine' after the next cumulative update

Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.

⚠ 04
Seller refuses to put the entitlement in your tenant

For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

Microsoft 365 admin center volume licensing

Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

EA

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

SA

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →
FAQ

Frequently asked questions

Is Dynamics 365 the same as Dynamics GP, NAV or AX?+
No — those were the previous on-premises ERP lines. Business Central is the cloud successor to NAV (and is what Microsoft positions for SMB customers migrating off GP, NAV or SL). Finance + Supply Chain Management is the cloud successor to AX. GP is in its sunset phase with security updates only.
Can we deploy Dynamics 365 on-premises?+
Customer Engagement apps (Sales, Customer Service, Field Service) have an on-premises option — Dynamics 365 Customer Engagement (on-premises) — but Microsoft's investment is firmly in the cloud. Business Central can be deployed on-premises through a partner. Finance + Supply Chain Management has limited on-premises support via the Local Business Data option but the cloud SaaS is the default deployment.
How does the base + attach model work for mixed teams?+
Each user has exactly one base app (the higher-priced licence) and any number of attach apps (steeply discounted) for that same user. If your sales team needs Sales as base and Customer Service as attach, that maths is favourable. If a separate operations team only needs Field Service, those users each carry a Field Service base licence and cannot share the attach pricing from the sales team's bases.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. If someone offers you a standalone OEM key, treat it as a red flag: it almost always means either a leaked volume key, a counterfeit, or a key harvested from decommissioned hardware, none of which Microsoft will honour at audit time.
What gets checked in a Microsoft licensing audit?+
A licensing review compares deployed software and access with documented entitlements: edition, version, quantity, assignment, agreement and any qualifying subscription or Software Assurance benefits. Use applicable order and agreement records, including volume licensing records in the Microsoft 365 admin center where relevant. CALs cover licensed users or devices, not simply concurrent sessions. Audit procedures and remedies depend on the agreement; no universal penalty or outcome is assumed.