“Microsoft Dynamics 365 ERP” sounds like one product. It is actually a set of applications that share a platform, a licensing model, and a release cadence — and the boundaries between them matter when you are mapping users to licenses. A warehouse supervisor, a project manager, and a controller may all be “Dynamics 365 users,” but they do not need the same apps.
The suite is Microsoft’s enterprise and mid-market ERP offering. It includes Finance, Supply Chain Management, Commerce, Project Operations, Human Resources, and Business Central. Around those apps sits the platform layer: Dataverse, Power Platform, Azure, and Copilot. That layer is a large part of the value proposition, and a large part of the implementation complexity.
This guide maps the apps, explains what each one actually covers, and covers the licensing and implementation details that determine what a Dynamics 365 ERP program costs.
The App Map
| App | Core scope | Typical users |
|---|---|---|
| Dynamics 365 Finance | General ledger, AP/AR, fixed assets, budgeting, cost accounting, consolidation, tax, audit | Controllers, accountants, finance analysts, CFO |
| Dynamics 365 Supply Chain Management | Procurement, inventory, warehouse, transportation, master planning, production control, quality | Buyers, planners, warehouse staff, production managers |
| Dynamics 365 Commerce | E-commerce, retail POS, call center, omnichannel fulfillment | Retail operations, e-commerce teams, customer service |
| Dynamics 365 Project Operations | Project sales, resourcing, time and expense, billing, revenue recognition | Project managers, consultants, professional services leaders |
| Dynamics 365 Human Resources | Employee records, leave and absence, benefits, compensation | HR teams, payroll administrators |
| Dynamics 365 Business Central | Full ERP for SMBs: financials, sales, purchasing, inventory, projects, light manufacturing | Small and mid-market companies |
The first five apps are part of the F&O platform, which descends from Dynamics AX. Business Central is a separate product with its own codebase, licensing, and partner ecosystem. It is grouped under the Dynamics 365 brand, but it is not an app inside F&O. That distinction matters when a partner proposes “Dynamics 365” without naming the product.
Finance and Supply Chain Management are the core. Most F&O deployments start with one or both, then add Commerce, Project Operations, or Human Resources as the scope expands. The apps share a legal entity structure, a chart of accounts, and a security model, which is the main reason to buy them together rather than stitching together best-of-breed systems.
What Each App Actually Covers
Finance is the accounting core: general ledger, accounts payable, accounts receivable, fixed assets, budgeting, cost accounting, consolidation, tax, and audit trails. It supports multiple legal entities and currencies, intercompany accounting, and a formal close process. For a US company, the key questions are the chart of accounts design, the consolidation structure, and how the system handles ASC 606 and sales tax. Finance is usually the first app implemented because nothing else works without it.
Supply Chain Management is the operations core: procurement and sourcing, inventory, warehouse management, transportation, master planning, production control, and quality. It is deep, and it assumes a real supply chain organization. The warehouse management module alone can run a multi-site distribution operation; the master planning engine can generate replenishment plans across facilities. Companies with simple inventory needs often find this more than they need and choose Business Central instead.
Commerce covers e-commerce, retail point of sale, call center, and omnichannel fulfillment. It is relevant for retailers and direct-to-consumer brands that want storefront and back office on the same data. It is not a general-purpose ERP module; it is a commerce layer that reads from Finance and Supply Chain.
Project Operations covers project sales, resourcing, time and expense, billing, and revenue recognition. It is aimed at professional services, construction, and project-based manufacturers. It connects the project plan to the financial ledger, which is the main reason to use it rather than a standalone PSA tool.
Human Resources covers employee records, leave and absence, benefits, and compensation. Microsoft has been converging HR capabilities across Dynamics 365, Viva, and the wider Microsoft cloud, so confirm the current packaging and roadmap before you plan a deployment. Many companies keep a dedicated HCM or payroll system and integrate rather than run HR inside the ERP.
Licensing by Role, Not by App
Dynamics 365 licensing is per user, per app, with base and attach pricing. The first app a user is licensed for is the base license; additional apps for the same user are often priced at a lower attach rate. That structure rewards careful role mapping. A controller who needs Finance and Project Operations may not need two full licenses; a warehouse supervisor who only needs Supply Chain may not need Finance at all.
Microsoft publishes list prices, though enterprise agreements and partner discounts change the effective rate. Recent list prices have been around $180 per user per month for Finance, Supply Chain Management, and Commerce, and around $120 for Project Operations. Business Central is priced separately, with Essentials and Premium tiers. Treat these as reference points, not quotes.
The licensing trap is over-provisioning. Companies often license everyone for everything because mapping roles takes time. That inflates the annual cost and hides the real usage pattern. Do the role mapping before you sign, and review it annually. It is also worth asking which users need full app access versus a lighter “team member” license for occasional tasks.
One Version, Power Platform, and Copilot
F&O follows Microsoft’s One Version policy: two major releases a year, with customers expected to stay current. Microsoft handles the platform upgrade, but your extensions, integrations, and reports still need regression testing. The discipline is different from on-premises ERP, where a company might skip releases for years. It requires an internal owner and a partner who knows how to test.
The Power Platform layer is a genuine differentiator. Power Apps lets teams build small applications on top of ERP data. Power Automate handles approvals and integrations. Power BI provides reporting. Dataverse provides a shared data layer, and dual-write keeps select F&O data in sync with customer engagement apps. For companies already using Microsoft 365, this reduces the cost of custom integrations and reporting.
Copilot is Microsoft’s generative AI layer across Dynamics 365. It can summarize records, draft communications, and help with tasks inside the apps. It is useful in specific workflows, and it is not a replacement for clean data or good process design. Treat it as an accelerant, not a strategy. The companies that get value from it are the ones with standardized processes and reliable master data.
Implementation Realities
Dynamics 365 ERP implementations are partner-led and structured. A typical F&O program runs nine to eighteen months for the first wave, with Finance and Supply Chain Management as the usual starting apps. The work includes process design, data migration, integration, security roles, testing, training, and organizational change. Microsoft’s FastTrack program provides guidance and some funded advisory hours, but the partner does the implementation.
The biggest risks are familiar. Data quality is the first: item masters, customer records, and opening balances. Process disagreement is the second: ERP forces standardization, and departments resist. Integration is the third: every system that touches finance or operations needs a connection. The fourth is licensing creep, as more users and apps are added without a corresponding review.
Budget for hypercare and a slower first close. Do not schedule a major acquisition or audit in the same quarter as go-live. And keep a running list of customizations, because every extension is a future testing obligation under One Version.
Who Should Choose Dynamics 365 ERP
Dynamics 365 ERP fits companies that want a Microsoft-aligned platform, a deep partner ecosystem, and an app model that can expand from finance into supply chain, commerce, projects, and HR. It is strongest in upper mid-market and enterprise organizations with multiple entities, complex operations, and an existing Microsoft footprint.
It is a weaker fit for small companies that would be better served by Business Central, for companies with highly specialized vertical needs that a Microsoft partner cannot cover, and for companies that cannot support a multi-year program. It is also a weaker fit when the licensing complexity would outweigh the integration benefits.
For the mid-market alternative, see the Dynamics ERP guide. For the broader portfolio and legacy products, see Microsoft ERP. And if you are still building a shortlist, start with the ERP software buyer’s guide or the cloud ERP guide.
Frequently Asked Questions
What apps are included in Microsoft Dynamics 365 ERP?
The main ERP apps are Dynamics 365 Finance, Supply Chain Management, Commerce, Project Operations, Human Resources, and Business Central. Business Central is a separate product for SMBs, while the other five are part of the Finance and Operations platform. Microsoft also sells customer engagement apps such as Sales and Customer Service, which are not ERP.
Is Dynamics 365 ERP cloud-only?
Finance and Supply Chain Management are cloud-first, with limited on-premises options. Business Central is available in the cloud and on-premises. Microsoft’s investment and release cadence are oriented toward the cloud, so confirm the support terms if on-premises is a hard requirement.
How is Dynamics 365 ERP licensed?
Per user, per app, with base and attach pricing. The first app a user is licensed for is the base license; additional apps are often priced lower. Business Central uses Essentials and Premium tiers instead. Microsoft publishes list prices, but enterprise agreements and partner discounts change the effective rate. Map roles to apps before you sign.
What is One Version in Dynamics 365?
One Version is Microsoft’s release policy for Finance and Operations: two major updates a year, with customers expected to stay current. Microsoft manages the platform upgrade, but your extensions, integrations, and reports need regression testing. It is a continuous-update model, not a set-and-forget deployment.
Does Copilot replace ERP customization?
No. Copilot can summarize records, draft content, and assist with tasks, but it does not change the underlying data model or process design. It works best when master data is clean and processes are standardized. Treat it as a productivity layer, not a substitute for configuration or integration work.
About the Author
Michael Grant is a senior ERP analyst and contributing editor at ERP Compass. He spent 12 years implementing and supporting finance and operations systems for US manufacturers, distributors, and professional services firms before moving into independent research. Read more about our editorial process.
Last updated: November 2026