The Dynamics 365 product family

Dynamics 365 is not one product. It is a portfolio of business applications sold under one brand, grouped loosely into two halves: ERP for running the back office (money, inventory, operations) and CRM for running customer-facing work (sales, service, marketing). Microsoft calls the CRM half "Customer Engagement" and the ERP half "Finance and Operations apps", and neither label appears consistently even in Microsoft's own material — which is why a map helps.

If you're deciding what to buy, the product chooser is the decision-focused companion to this guide. This one is the tour.

The ERP side: money and operations

Dynamics 365 Finance is the enterprise financial system, descended from Dynamics AX. General ledger, accounts payable and receivable, fixed assets, budgeting, revenue recognition, and consolidations across many legal entities, currencies, and tax regimes. If you have subsidiaries in twelve countries, this is the tier built for you.

Dynamics 365 Supply Chain Management is Finance's operational twin — same codebase, same database, usually implemented together (the pair is what people mean by "F&O"). It covers procurement, inventory, warehouse and transportation management, master planning, and discrete, process, and lean manufacturing.

Business Central is the SMB ERP, descended from Dynamics NAV. It delivers financials, sales, purchasing, inventory, projects, and light manufacturing in one tightly integrated app with a far simpler operating model than F&O. It is not a cut-down F&O — it is a different product with a different lineage, and for most companies under a few hundred users it is the right ERP. The BC vs F&O comparison draws the line in detail.

Project Operations runs professional services firms — project sales, resourcing, time and expense, project accounting, and billing. It deliberately straddles the ERP/CRM line: the sales and resourcing side runs on Dataverse, the invoicing side runs on the F&O financial engine.

The CRM side: customers

Sales handles leads, opportunities, pipeline, and forecasting — the core CRM most people picture. It is Microsoft's head-to-head competitor with Salesforce, and that comparison is its own guide.

Customer Service runs case management and omnichannel support — voice, chat, email, social — with SLAs, entitlements, and knowledge management. Its contact-centre sibling, Dynamics 365 Contact Center, packages the channel and Copilot layer as a standalone CCaaS product that can sit on top of other CRMs.

Field Service schedules and dispatches mobile technicians: work orders, route optimisation, a technician mobile app, and IoT-triggered service. If your business sends people in vans to fix things, this is the app.

Customer Insights is one licence covering two distinct products. Customer Insights – Journeys is the marketing automation app — customer journeys, email campaigns, events, lead scoring. Customer Insights – Data is a customer data platform that unifies profiles from many systems. They install and work independently; the shared name causes endless confusion, and the naming history explains how it got this way.

The operational extensions

Human Resources covers HR core: the employee record, org structure, leave and absence, benefits, and compensation. It is not a payroll engine — payroll comes from ISV partners — and in most deployments it feeds a broader HCM landscape rather than replacing one.

Commerce is the unified retail platform: head-office merchandising, store point-of-sale, e-commerce, and call centre, running on the same data model as Finance and Supply Chain Management. It is the deepest vertical product in the family and effectively assumes the F&O backbone underneath it.

The platform underneath

Every app above stands on shared plumbing, and that plumbing is the real reason the family exists as a family.

The Power Platform — Power Apps, Power Automate, Power BI, Copilot Studio, and Power Pages — extends every Dynamics 365 app with low-code customisation, automation, analytics, AI agents, and external portals. In practice you cannot run a serious Dynamics 365 implementation without touching it; a Dynamics licence includes rights to use it against your Dynamics data.

Microsoft Dataverse is the shared data layer the CRM-side apps run on natively. The ERP apps keep their own databases and connect to it — a distinction with real architectural consequences, unpacked in how the apps connect.

Identity comes from Microsoft Entra ID, so one login covers CRM, ERP, Power Platform, and Microsoft 365. Infrastructure, compliance, and data residency are inherited from Azure. And Copilot now threads through the whole family — the orientation guide covers what is real versus roadmap.

How to read the family

Three practical rules keep the portfolio legible:

The apps are sold separately. "We're getting Dynamics 365" means nothing until someone names the apps. Each is licensed per user per month at its own price, with attach pricing when one user needs several — the edition comparison covers the licensing shape.

The halves have different DNA. The CRM apps share one database and feel like one product. The ERP apps are separate systems that integrate with the CRM side rather than merging with it. Expect integration work whenever a project spans the line.

Names change; products mostly don't. Marketing became Customer Insights – Journeys, Retail became Commerce, AX became Finance and Supply Chain, NAV became Business Central. When you meet an unfamiliar Dynamics name in older material, it is usually a current product wearing a previous badge.

Next step in the path: how the apps actually connect — which links between them are tight, which are loose, and what that means for your architecture.