What is Dynamics 365?

Microsoft Dynamics 365 is a family of cloud-based business applications that combines enterprise resource planning (ERP) and customer relationship management (CRM) into a single, modular platform. Rather than buying one large monolithic system, organisations license the specific apps they need — Sales, Customer Service, Finance, Supply Chain Management, Business Central, Field Service, Project Operations, Human Resources, Commerce, and others — and run them on a shared data foundation called Dataverse (for the CRM-lineage apps) or on the F&O data model (for the AX-lineage apps).

Where Dynamics 365 came from

Dynamics 365 launched in 2016 as the successor to Microsoft's earlier business-apps portfolio — Dynamics AX, NAV, GP, SL, and CRM. Several of those legacy lines still live on inside Dynamics 365 in evolved form. Finance and Supply Chain Management grew out of Dynamics AX. Business Central grew out of Dynamics NAV. The CRM apps (Sales, Customer Service, Field Service) grew out of Dynamics CRM. GP and SL are still supported but did not get modern cloud successors under the Dynamics 365 name.

The benefit of consolidating everything under one brand is not just cosmetic. All the apps now share identity (Microsoft Entra ID), reporting (Power BI), automation (Power Automate), extensibility (Power Apps, Copilot Studio, and Azure), and increasingly a single Copilot layer. That means a Sales record can trigger a Business Central invoice with a low-code flow, a Power BI dashboard can pull from both an F&O warehouse and Dataverse without ETL, and the same Entra ID user can be granted access to the whole stack from one place.

The app families

Dynamics 365 splits into two lineages that share a brand but not a codebase.

The customer engagement apps — Sales, Customer Service, Field Service, Project Operations, Marketing (now Customer Insights – Journeys), and Contact Center — run on Dataverse and are the modern CRM stack. They share a data model, a security model, and the Power Platform build tools. Extensions are written in low-code Power Apps or in plugins and JavaScript.

The finance and operations apps — Finance, Supply Chain Management, Commerce, Human Resources, and Project Operations (F&O SKU) — evolved from Dynamics AX and run on a separate, X++-based platform. They are the enterprise ERP layer, aimed at organisations with complex financial consolidation, multi-legal-entity structures, or large warehouse and manufacturing operations. Development is in X++, deployed through Lifecycle Services (LCS).

Business Central is the third lineage — the SMB ERP evolved from NAV. It runs on its own platform, is extended in AL, and covers finance, sales, purchasing, inventory, and light manufacturing for mid-market companies.

The three lineages talk to each other via connectors, Dataverse virtual tables, and increasingly common Copilot surfaces — but under the hood they are still three products.

Who it is for

Dynamics 365 is sold per user, per app, and is most commonly deployed by mid-market and enterprise organisations that have outgrown entry-level accounting or spreadsheets but want to avoid the cost and multi-year risk of a custom-built or SAP-scale ERP.

Typical buyers include:

• SMB / mid-market ERP buyers — usually landing on Business Central, sometimes coming from QuickBooks, Xero, Visma, Fortnox, or a home-grown NAV.
• Enterprise ERP buyers — landing on Finance and Supply Chain Management, often replacing on-premise AX, JD Edwards, IFS, or an ageing custom system.
• Sales and service teams — landing on Sales, Customer Service, Field Service, or Project Operations, often replacing Salesforce, HubSpot, ServiceNow, or Zendesk in a Microsoft-heavy organisation.
• Marketing teams — landing on Customer Insights to unify customer data across the CRM and ERP apps.

The single strongest reason to choose Dynamics 365 over a specialised competitor is almost always the existing investment in Microsoft: Entra ID, Microsoft 365, Teams, Power BI, and Azure are already there, and Dynamics 365 slots into them without any of the integration tax you would pay for a foreign stack.

What it actually costs

Pricing is published on Microsoft's site — a per-user, per-month figure for each app, with base + attached-app discounts and volume discounts through enterprise agreements — but the sticker price is only ever a fraction of the real cost of Dynamics 365.

Real-world cost is dominated by:

• Data migration from the incumbent system, which is almost always more work than the customer expects.
• Configuration — chart of accounts, dimensions, security roles, workflows, price lists.
• Customisations and integrations — Power Automate flows, plugins, ISV apps, and connections to bank feeds, e-commerce platforms, warehouse hardware, or industry systems.
• Training and change management — Dynamics 365 replaces the tool people spend their day in, so adoption is a real project.
• Partner fees for all of the above.

A rough industry rule is that the first-year all-in cost is somewhere between 3× and 8× the annual licence cost, depending on the apps in scope and how much customisation the customer takes on. In steady state, ongoing partner spend usually runs 15–30 % of licence spend per year.

The partner ecosystem

Dynamics 365 is almost always implemented with help from a Microsoft partner. Microsoft itself does not deliver implementations except for the largest customers. Instead, a global network of certified partners — from boutique specialists to global systems integrators (SIs) — does the work.

The partner ecosystem breaks down roughly like this:

• Business Central partners — often specialise by country or by vertical (retail, manufacturing, distribution). Many have their own ISV extensions on top of BC.
• F&O partners — larger firms, often global SIs (Avanade, KPMG, EY, PwC, HSO, Cognizant, Wipro), because F&O programmes tend to be multi-year and multi-region.
• Customer engagement partners — a wider mix, from Power Platform-first specialists to CRM boutiques to the big SIs.
• Independent software vendors (ISVs) — publishing add-ons on AppSource for country-specific tax, industry verticals, or extra features Microsoft doesn't cover.

Choosing the right partner and apps is usually a bigger decision than choosing Dynamics 365 itself. A great platform with the wrong partner still fails; a mediocre platform with the right partner often quietly succeeds.

Where to go next

If you're figuring out which app to license, the plain-English decision guide is how to choose the right Dynamics 365 product. If you want the whole product family on one page, see the Dynamics 365 product family. For the Power Platform connection, read Dynamics 365 and the Power Platform. And if you're weighing Business Central vs Finance & Supply Chain, start with what is Business Central and what is Dynamics 365 Finance.