Dynamics 365 is a family of business apps, not a single product.
Most teams evaluating Dynamics 365 hit the same snag early. It is not one application but a set of business apps, and Microsoft's names and groupings rarely match how a company thinks about its own departments.
This guide is Microsoft Dynamics 365 modules explained from the buyer's side. It covers what each group of apps does, how they share data, and how rollouts are usually phased. If you want the platform basics first, start with our overview of what Dynamics 365 is and how it works.
A quick note on terms: Microsoft calls these apps or applications, while most people search for modules. This article uses both words for the same thing.
Why Buyers Care About the Modular Design
Modular means you start with what you need, not that every addition is free.
Dynamics 365 divides business functions into separate apps, so a company can begin with finance or sales and add other areas later. That keeps the first rollout smaller and easier to train for. For customer engagement apps, Microsoft documents installation as an administrative task at the tenant or environment level.
The trade-off is that each added app brings its own licensing, data mapping and change management. Modular design lowers the cost of starting. It does not remove the cost of connecting apps well later.
Microsoft Dynamics 365 Modules Explained by Business Function
Microsoft calls them apps, but grouping them by function is what makes the list usable.
Microsoft's Dynamics 365 documentation lists close to twenty products and product areas, but most buying decisions come down to three groups. Customer engagement apps cover sales, service and marketing. Finance and operations apps cover the back office. Business Central is a separate ERP product with its own licensing.
The table below covers the apps teams ask about most often.
Group | App | Main job |
Customer engagement | Sales | Leads, opportunities and pipeline |
Customer engagement | Customer Service | Cases, knowledge articles and service agreements |
Customer engagement | Contact Center | Voice and digital channels for service teams |
Customer engagement | Field Service | Work orders, scheduling and technician dispatch |
Customer engagement | Customer Insights | Customer data and marketing journeys |
Finance and operations | Finance | General ledger, payables, receivables and budgeting |
Finance and operations | Supply Chain Management | Procurement, inventory, warehousing and manufacturing |
Finance and operations | Commerce | Retail and omnichannel commerce |
Finance and operations | Human Resources | Core people records and processes |
Spans both | Project Operations | Project planning, resourcing and billing |
Separate ERP product | Business Central | Finance and operations in a single product |
One naming change catches many buyers out. What used to be Dynamics 365 Marketing now sits in Customer Insights - Journeys. If an older guide lists Marketing as a standalone app, it is out of date.
Key ERP and CRM Apps in More Detail
Four pairings cover most of what teams actually deploy.
Finance and Supply Chain Management
The back office lives here.
Microsoft groups these apps under the finance and operations label, and the older name Finance and Operations still appears in plenty of articles. Finance handles the general ledger, payables, receivables and budgeting. Supply Chain Management adds procurement, inventory, warehousing and manufacturing. Companies often adopt them together when finance and operations teams need the same data.
Sales and Customer Service
Revenue and service work from the same customer record.
Sales tracks leads, opportunities and pipeline. Customer Service manages cases, knowledge articles and service agreements. When both run on shared customer data, a service issue can be visible to the account team before a renewal conversation. Contact Center adds voice and digital channels for teams that need them.
Field Service and Customer Insights
On-site work and campaigns both depend on clean customer data.
Field Service covers work orders, scheduling and dispatch, plus a mobile app for technicians. Microsoft's Field Service overview also describes Connected Field Service, where connected devices can raise alerts or work orders automatically. Customer Insights covers customer data and marketing journeys.
Project Operations and Human Resources
These two are easy to overlook until a rollout needs them.
Project Operations supports project-based work such as planning, resourcing and billing, and it sits across the ERP and CRM sides. Human Resources manages core people records and is still documented as a current Dynamics 365 app. Neither is required for a first phase, but check both early if your business bills by project or runs complex HR processes.
How Dynamics 365 Apps Share Data
Shared data, not shared branding, is what makes the apps a suite.
Dataverse as the Shared Data Layer
Most customer engagement apps store their data in one place.
Microsoft Dataverse stores business data in tables and adds security, business rules and APIs on top. Microsoft's documentation names Sales, Customer Service and Human Resources as apps that store their data there. Dataverse was previously called Common Data Service, so older posts and projects still use that name.
Finance and operations apps are the exception worth remembering. They keep their own data store and reach Dataverse through integration, which is where dual-write comes in.
Dual-Write and Integration
Dual-write is the standard bridge between ERP and CRM data.
Dual-write provides near-real-time, bidirectional integration between finance and operations apps and customer engagement apps. A change on one side writes to the other. It also adds concepts such as company and party to Dataverse, so Microsoft advises planning those schema changes early. Treat it as a design decision, not a switch to flip late in the project.
Power Platform Extensions
Low-code tools reuse the same tables the apps do.
Power Apps, Power Automate and Power BI can all use Dataverse data. A custom app or automated approval can therefore work against the same records as Sales or Customer Service. That keeps extensions from turning into a second, separate system. Custom tables are also supported when the standard ones do not fit.
Adding, Extending and Phasing Apps
Plan the order of rollout before the first app goes live.
Adding Apps After Go-Live
Most additions are an administrative step, with caveats.
For customer engagement apps, Microsoft documents installation in the Power Platform admin center, either per tenant or per environment. The environment needs a database and the Dynamics 365 apps option enabled. Finance and operations apps follow a separate provisioning path, so confirm the steps and licensing with your implementation partner before promising a date.
Customizing Without Creating Debt
Configure first, then extend, then write code.
Standard configuration and low-code extensions are easier to carry through Microsoft's regular releases than heavy custom code. Custom tables and workflows suit industry-specific data the standard apps do not hold. Reserve custom development for processes that genuinely cannot run on a standard workflow.
Cloud and On-Premises Options
Check functionality and lifecycle before choosing on-premises.
Microsoft still documents on-premises deployment for finance and operations apps and notes that it differs from cloud in system requirements, hardware sizing and functionality. Customer Engagement on-premises also appears in Microsoft's documentation. Before choosing either, check the current software lifecycle policy for end dates.
Phased Rollout Strategies
Start where the pain is sharpest, then connect.
A phased plan usually starts with the app tied to the most urgent process, such as finance for a close that runs late or Sales for a pipeline nobody trusts. Later phases add apps once users are comfortable and the integration design is settled. Tie each phase to a budget cycle and a clear definition of done.
Rollouts also stall for reasons outside the software, which we cover in why ERP implementations fail without AI and automation.
FAQs
What is the difference between Dynamics 365 modules?
Each module targets a distinct business function, such as finance, sales or service. Finance and operations apps handle back-office work like accounting and supply chain. Customer engagement apps cover sales, service, field work and marketing. They can be deployed separately or connected, depending on need.
How many modules are in Microsoft Dynamics 365?
There is no single fixed number. Microsoft's documentation currently lists close to twenty products and product areas, including Business Central, Finance, Supply Chain Management, Sales, Customer Service, Field Service, Commerce, Project Operations and Human Resources. The list changes as Microsoft adds, renames or retires apps.
What modules are included in Dynamics 365 Finance and Operations?
Microsoft now uses Finance and Supply Chain Management as the product names. Finance covers the general ledger, payables, receivables and budgeting. Supply Chain Management covers procurement, inventory, warehousing and manufacturing. Commerce, Project Operations and Human Resources are separate apps that are often deployed alongside them.
Can modules be added to Dynamics 365 after deployment?
Usually yes, subject to licensing. Customer engagement apps are installed through the Power Platform admin center. Finance and operations apps follow a separate provisioning path. Plan data integration and security roles for each new app before enabling it.
How do Dynamics 365 modules work together?
Most customer engagement apps share data through Dataverse. Finance and operations apps connect to them through integration such as dual-write. Power Apps and Power Automate can then extend processes across both sides using the same data.
