The Dynamics 365 App Map

What "Dynamics 365 business applications" actually means

When Microsoft says "business applications," it means a specific thing: the cloud apps it sells under the Dynamics 365 brand, plus the Power Platform (Power Apps, Power Automate, Power BI, and Copilot Studio) that connects and extends them. Microsoft Learn describes Dynamics 365 as a set of intelligent cloud applications that help organisations run sales, service, operations, finance, and commerce from connected data. Each Dynamics 365 app is a standalone SaaS product you license per user per month — you do not buy "Dynamics 365" as a single suite. In 2026 Microsoft also positions the portfolio as agentic business applications: first-party agents and custom agents (via Copilot Studio and Model Context Protocol servers) that act inside the apps under the same security and audit rules as people.

The architecture that makes these separate apps behave like a portfolio is the shared data layer underneath them. The customer-engagement apps (Sales, Customer Service, Field Service, Customer Insights) store their data natively in Microsoft Dataverse, the managed relational data service that is also the foundation of Power Apps. Because they share the same tables for accounts, contacts, and cases, one app can read and write the records another app owns without an integration project. That single-source-of-truth model is what the phrase "business applications" is really pointing at.

The finance-and-operations side of the portfolio works differently. Dynamics 365 Finance, Supply Chain Management, Commerce, and Project Operations run on their own purpose-built database and reach Dataverse through Microsoft's dual-write synchronisation framework rather than storing data in it natively. Business Central, the SME all-in-one ERP, has its own database again. So the honest mental model is three data tiers under one brand: Dataverse-native (CRM), dual-write-bridged (enterprise ERP), and self-contained (Business Central). Every decision about which apps to buy, how many to buy, and how they connect flows from understanding those three tiers.

• →Dynamics 365 is a portfolio of eleven modular per-user cloud apps, not a single suite you buy as one product
• →"Business applications" = the Dynamics 365 apps plus the Power Platform (Power Apps, Power Automate, Power BI, Copilot Studio) that extends them
• →The customer-engagement apps share data natively through Microsoft Dataverse; finance-and-operations apps bridge to Dataverse via dual-write
• →Three data tiers: Dataverse-native CRM, dual-write-bridged enterprise ERP, and self-contained Business Central
• →Every licensing and integration decision starts with knowing which tier each app sits in
• →In 2026 the portfolio is explicitly agent-ready: prebuilt agents plus custom agents need app licenses and, for many scenarios, Copilot Credits

The full Dynamics 365 app map (all eleven apps)

Microsoft's official pricing overview lists eleven Dynamics 365 applications. They cluster into four functional groups: CRM (customer engagement), enterprise ERP (finance and operations), the SME all-in-one ERP, and the marketing/customer-data platform. The table below is the single reference you should keep — it names every app, the group it belongs to, what it does in one line, and verified per-user list prices for 2026. All prices are USD annual list prices from Microsoft's product pricing pages and 2026 partner summaries of the licensing guide; monthly billing is typically higher.

Two reading notes before the table. First, CRM prices are tiered (Professional / Enterprise / Premium) and the table shows the Enterprise anchor where one exists; each app's dedicated pricing page carries the full tier breakdown. Second, Business Central is priced by Essentials or Premium edition rather than by app because it bundles finance, sales, purchasing, and operations. Customer Insights is per tenant with metered consumption, not per user. Several apps also expose Premium or device SKUs and agent features that consume Copilot Credits on top of the seat price — treat seat list prices as the base layer of TCO, not the whole bill.

• →Eleven apps across four groups: CRM, enterprise ERP, SME all-in-one ERP, and marketing/customer data
• →CRM apps are tiered (Professional/Enterprise/Premium); Finance and SCM list at $210 with Premium at $300
• →Customer Insights is per-tenant + metered, not per-user — budget it separately
• →Business Central is sold by edition (Essentials $80 / Premium $110), not by app
• →Seat list prices exclude Copilot Credits for many agents and exclude implementation — model both
• →Every price above is a USD annual list price from Microsoft and 2026 partner licensing summaries

The data split: why CRM and ERP apps do not share the same database

The single most important architectural fact about Dynamics 365 — and the one most buyers miss — is that the CRM apps and the enterprise ERP apps do not share one database. Microsoft's Power Apps documentation is explicit: the customer-engagement apps (Sales, Customer Service, Field Service, Human Resources) store and secure their data natively in Dataverse, while "Finance and Operations apps currently require the configuration of the Data Integrator to make your business data from Finance and Operations apps available in Dataverse." Treat the marketing line "Dynamics 365 runs on one data layer" as true for CRM and only conditionally true for enterprise ERP.

The customer-engagement apps live natively in Dataverse. When you license Dynamics 365 Sales, you are licensing a pre-built application that runs on Dataverse tables — accounts, contacts, leads, opportunities. A Power App or a Power Automate flow can read and write those same records with no integration layer, and the business rules, security roles, and relationships defined in Dataverse apply regardless of which app touches the data. This is why the CRM apps compose so easily: they genuinely share one governed data store.

The enterprise ERP apps — Finance, Supply Chain Management, Commerce, and Project Operations — run on their own high-throughput database designed for transactional financial and operational load. That database does not live inside Dataverse. To make enterprise ERP data visible to the CRM apps, Power Apps, and Copilot, Microsoft provides dual-write, a near-real-time bidirectional synchronisation framework that mirrors selected tables between the F&O database and Dataverse. Dual-write is powerful but needs deliberate setup: table maps must be enabled and validated, initial synchronisation bootstrapped, and live sync monitored. Business Central sits in a third place: it has its own database entirely and connects to Dataverse through the Business Central connector and virtual tables rather than dual-write.

• →CRM apps (Sales, Service, Field Service, HR, Customer Insights) store data natively in Dataverse
• →Enterprise ERP apps (Finance, SCM, Commerce, Project Operations) use their own database, bridged via dual-write
• →Dual-write mirrors selected tables between the F&O database and Dataverse in near-real-time — it must be set up and tuned
• →Business Central has its own database and reaches Dataverse through connectors and virtual tables
• →"Dynamics 365 runs on one data layer" is true for CRM and conditionally true for enterprise ERP

The CRM apps: Sales, Customer Insights, Customer Service, Contact Center, Field Service

The five customer-engagement apps cover the front office — finding, winning, serving, and retaining customers. Because they all live natively in Dataverse, a single account record created in Sales is immediately visible to Customer Service, Field Service, and Customer Insights without any integration. That shared account/contact/case backbone is the core reason buyers pick the Dynamics 365 CRM stack over stitching together separate tools.

Dynamics 365 Sales ($105/user/month Enterprise) manages the pipeline end to end: accounts, contacts, leads, opportunities, quotes, and AI-assisted forecasting through the Sales Accelerator. Dynamics 365 Customer Service ($105/user/month Enterprise) is the case-management core — a unified agent workspace, knowledge management, and entitlements — and is distinct from Dynamics 365 Contact Center ($110/user/month), the contact-centre-as-a-service app that adds routing, IVR, voice, and supervisor analytics on top. Many teams license Customer Service for ticketing and Contact Center for live channels as a pair.

Dynamics 365 Field Service ($105/user/month Enterprise) extends the service model to the physical world: work orders, resource scheduling, a mobile app for technicians, asset service, and IoT-triggered maintenance. Dynamics 365 Customer Insights is the different one — it is the customer data platform and journey-orchestration engine (the successor to Dynamics 365 Marketing), priced per tenant at $1,700 base with metered consumption rather than per user. Customer Insights unifies customer data from across the apps and orchestrates marketing journeys, so it sits above the operational CRM apps as the personalisation layer. Together these five apps form a connected front office that shares one account and contact graph in Dataverse.

Security for the CRM stack is role-based in Dataverse: security roles grant privileges on tables (account, contact, opportunity, case, work order) and business units scope who sees which records. Because roles live in Dataverse, the same role definition applies whether a user is in Sales, Customer Service, a model-driven Power App, or an agent acting on their behalf. When you design the estate, plan roles once and package them in solutions so they promote cleanly from development to test to production.

• →Five CRM apps share one Dataverse account/contact/case graph — no integration between them
• →Sales ($105) for pipeline; Customer Service ($105) for cases; Contact Center ($110) for live channels and routing
• →Field Service ($105) extends service to physical work orders, scheduling, and a mobile dispatch app
• →Customer Insights ($1,700/tenant, metered) is the customer data platform and marketing journey engine, not a per-user app
• →Customer Service and Contact Center are commonly licensed together — ticketing plus live omnichannel
• →Dataverse security roles govern CRM table access once and apply across apps, Power Apps, and agents

The enterprise ERP apps: Finance, Supply Chain Management, Commerce, Project Operations

The finance-and-operations (F&O) apps cover the back office for larger or operationally complex organisations. They share a single codebase and database, which means a typical enterprise buyer runs Finance plus Supply Chain Management (SCM) together as one ERP instance — Finance handles the ledgers and SCM handles the operational transactions that post into them. Microsoft lists both at $210/user/month (Finance Premium at $300 adds advanced business-performance management). The four apps are modular in licensing but unified in data once connected.

Dynamics 365 Finance is the financial core: general ledger, accounts receivable and payable, fixed assets, budgeting, multi-currency and multi-company consolidation, and AI-assisted cash-flow forecasting. Dynamics 365 Supply Chain Management adds the operational engine — inventory and warehouse management, procurement, production and master planning, and shop-floor control. Because Finance and SCM sit in the same database, a purchase order raised in SCM posts its accounting entries to Finance automatically. This is the same module set covered in depth in our finance-ops and SCM modules guides, which break down what is inside each module.

Dynamics 365 Commerce ($210/user/month standalone, or roughly $20/user/month as an attach to an F&O base, plus a $4,000/tenant e-commerce add-on) extends the ERP into omnichannel retail — an e-commerce storefront, point of sale, and distributed order management across channels. Dynamics 365 Project Operations ($135/user/month, with a $30 attach and $8 Team Member tier) serves project-based and services businesses, covering project sales, resourcing, time and expense, and project accounting that posts into Finance. All four F&O apps reach Dataverse (and therefore the CRM apps and Copilot) through dual-write, which is why an integrated F&O + CRM estate is a real, deliberate project rather than a checkbox.

Licensing enforcement tightened for finance-and-operations apps: from November 1, 2025 Microsoft requires assigned licenses for F&O access, with validation rolling out from January 15, 2026 on customer renewal timelines. Mixed CRM + F&O estates should verify that every operational user has a proper base or attach assignment — not just Entra group membership — before renewal. Attach pricing for Finance, Supply Chain Management, Human Resources, and Project Operations is typically $30/user/month when the user already holds a qualifying higher-priced base license; CE attaches (Sales, Customer Service, Field Service) are typically $20.

• →Finance and Supply Chain Management share one codebase and database and run together as one enterprise ERP ($210/user/month each)
• →Finance is the ledger core; SCM is inventory, procurement, production, warehouse, and master planning
• →Commerce ($210 standalone, ~$20 attach) adds omnichannel retail, POS, and distributed order management
• →Project Operations ($135) serves project and services firms with project sales, resourcing, and project accounting
• →All four reach the CRM stack and Dataverse through dual-write synchronisation, not native storage
• →F&O license validation (from late 2025 into 2026 renewals) requires assigned base/attach licenses for Finance, SCM, Commerce, and related ops apps

Business Central: the all-in-one ERP for small and mid-sized businesses

Dynamics 365 Business Central is architecturally and commercially separate from the enterprise F&O apps, and that distinction matters enormously for SMEs. It is a single all-in-one application — finance, sales, purchasing, inventory, manufacturing, projects, and service management in one product — priced by edition rather than by app: $80/user/month for Essentials and $110/user/month for Premium (with Team Members at $8). Where the F&O apps are licensed and bolted together, Business Central ships with most functions already inside it.

Business Central has its own database, distinct from both Dataverse and the F&O database. It does not store its data natively in Dataverse, so if an SME wants to extend BC with model-driven Power Apps, Copilot experiences, or a connection to Dynamics 365 Sales, it does so through the Business Central connector, Power Automate flows, or virtual tables that surface BC data into Dataverse. This is an extension scenario, not a default — many SMEs run Business Central effectively with no Dataverse footprint at all.

The relationship between Business Central and the enterprise F&O apps is best understood as a scale ceiling, not a competitor debate. Business Central is built for small and mid-sized businesses; Finance and SCM are built for larger or more operationally complex organisations. The realistic trigger to move from Business Central up to Finance + SCM is usually manufacturing depth, multi-entity financial complexity, or transaction volume that BC is not designed to carry. Microsoft positions the two tiers as a continuum, and most SMEs evaluating "Dynamics 365" are actually looking at Business Central first.

Business Central also ships first-party agents — notably a Sales Order Agent (email-to-quote/order capture) and a Payables Agent (invoice draft creation). Microsoft's Business Central pricing page states both require Copilot Credits sold separately on top of Essentials or Premium seats. That pattern is the 2026 rule of thumb: the app license gets you into the process; agent runtime is often metered. SMEs planning "AI in BC" need a seat plan plus a Copilot Credits pay-as-you-go or prepaid commit, not seats alone.

• →Business Central is one all-in-one app: finance, sales, purchasing, inventory, manufacturing, and service in one product
• →Priced by edition: Essentials $80/user/month, Premium $110/user/month, Team Members $8
• →Has its own database — does not store data natively in Dataverse; reaches it via connectors and virtual tables
• →Distinct from the enterprise F&O apps; the two are a scale continuum, not a direct competitor debate
• →Most SMEs evaluating "Dynamics 365" are actually being shown Business Central first
• →Sales Order Agent and Payables Agent need a BC license plus Copilot Credits — agent usage is consumption-priced

Human Resources: the standalone HR app and the F&O HR module

Dynamics 365 Human Resources ($135/user/month, with a $4/user/month Self Service tier and a $20–$30 attach option) is the standalone people-management app in the portfolio, covering core HR, benefits administration, leave and absence, compensation, and employee and manager self-service. Like the CRM apps, it stores its data natively in Dataverse, which means it composes cleanly with the rest of the customer-engagement stack and is reachable by Power Apps and Copilot directly.

There is a subtlety buyers often miss: the enterprise F&O apps also ship a built-in HR module (the legacy personnel-management functionality inside Finance and SCM). Organisations running Finance + SCM can use that embedded module for basic personnel records without licensing the standalone Dynamics 365 Human Resources app. The standalone app is the right choice when you need richer capability — benefits, leave workflows, self-service, and payroll integration — or when you want HR data to live in Dataverse alongside the CRM stack. For light personnel-record needs inside an existing F&O estate, the embedded module often suffices.

• →Dynamics 365 Human Resources ($135/user/month; $4 Self Service) covers core HR, benefits, leave, and self-service
• →Stores data natively in Dataverse, so it composes with the CRM stack and is reachable by Power Apps
• →The enterprise F&O apps also ship a built-in HR module for basic personnel records — no extra license needed
• →Choose the standalone app for richer HR capability or Dataverse residency; the embedded module for light records
• →An attach option ($20–$30) exists for adding Human Resources capability to an existing first-app base

How the apps share data through Dataverse

Dataverse is the reason the Dynamics 365 portfolio can be called a platform rather than eleven disconnected apps. It is Microsoft's cloud data service for business applications — a metadata-driven, relational data store on Azure that securely holds the tables, relationships, business rules, and security used by the customer-engagement apps and the Power Platform. Microsoft's documentation defines it as the service that "lets you securely store and manage data that's used by business applications" in a set of standard and custom tables. Because business rules and security are defined once in Dataverse and reused across every consuming app, a validation rule or role applies whether a record is touched by Sales, a Power App, a Power Automate flow, or Copilot.

For the CRM apps, sharing is automatic — they all read and write the same Dataverse tables. An account created in Sales is immediately visible to Customer Service and Field Service; a case can pull the same account's purchase history. There is no integration to build, no middleware to maintain, and no second copy of the customer record. This is the lowest-friction scenario in the portfolio and the one where the Dataverse-centric architecture pays off most.

For the enterprise ERP apps, sharing is engineered through dual-write. Dual-write is Microsoft's framework for near-real-time, bidirectional synchronisation between the F&O database and Dataverse: table maps define which F&O tables mirror into which Dataverse tables, and changes flow in both directions as they happen. This is what lets a sales order captured in Dynamics 365 Sales appear against an account whose financials live in Dynamics 365 Finance, with both sides staying consistent. Dual-write is powerful and is also the part of a Dynamics 365 estate that needs the most care — table maps must be enabled and validated, initial synchronisation bootstrapped, and live sync monitored for failures. For Business Central, the equivalent bridge is lighter: the Business Central connector, Power Automate flows, and virtual tables that present BC data inside Dataverse without copying it in. The practical takeaway is that "one platform" is real, but the seam between enterprise ERP and the rest of the stack is a project, not a default.

• →Dataverse is the shared, metadata-driven data service underneath the CRM apps and Power Platform
• →Rules and security defined in Dataverse apply across every consuming app — Sales, Power Apps, Power Automate, Copilot
• →CRM apps share data automatically — no integration, no second copy of the customer record
• →Enterprise ERP apps reach Dataverse through dual-write: near-real-time, bidirectional table-map synchronisation
• →Business Central bridges via connectors and virtual tables; the ERP-to-CRM seam is always a deliberate project

Where Power Platform and Copilot fit in

Power Platform is the layer that turns the Dynamics 365 apps from a set of products into an extensible platform. It comprises four services: Power Apps for building custom model-driven and canvas applications, Power Automate for workflow and process automation, Power BI for analytics and reporting, and Copilot Studio for building AI agents and Copilot experiences. All four read and write Dataverse natively, which means anything you build on Power Platform can reuse the same tables, rules, and security as the first-party Dynamics 365 apps.

The practical consequence is that gaps between the out-of-the-box apps are filled with low-code rather than custom integration. If Sales does not capture a field your industry needs, you add a column to the account table in Dataverse and it appears in Sales, in a custom Power App, and in Copilot alike. If a process crosses Sales and Finance, a Power Automate flow triggers on the relevant Dataverse or dual-write event and orchestrates the steps. Power BI connects directly to Dataverse to publish dashboards over the same operational data. None of this requires a separate data warehouse or middleware.

Copilot and agents are first-class across the portfolio. Microsoft positions Dynamics 365 as agentic business applications, with built-in agents (Sales qualification and research agents, finance reconciliation agents, Business Central Sales Order and Payables agents, Project Operations approvals agents, and more) plus Microsoft Copilot Studio for custom agents grounded in Dataverse or F&O data. The 2026 release wave 1 plans (April–September 2026) expand role-based agents in Microsoft 365 Copilot for Sales and Finance, Immersive Home workspaces in F&O, and Model Context Protocol (MCP) servers so agents can invoke the same transactional actions users run — Microsoft has described hundreds of thousands of MCP actions across sales, finance, supply chain, HR, field service, customer service, and project operations. Microsoft 365 Copilot can reach Dynamics 365 data when it is surfaced in Dataverse, which is why dual-write between F&O and Dataverse matters more than it used to: the more of your data that lives in or is mirrored to Dataverse, the more Copilot and custom agents can act on.

• →Power Platform = Power Apps, Power Automate, Power BI, and Copilot Studio, all reading Dataverse natively
• →Gaps between apps are filled with low-code (custom columns, model-driven apps, flows) rather than custom integration
• →A column added in Dataverse appears in Sales, custom Power Apps, and Copilot alike — one rule, many surfaces
• →2026 wave 1 deepens agentic experiences: role-based Copilot agents, Immersive Home, and MCP servers for transactional agent actions
• →Dual-write matters more in the agent era: F&O data mirrored to Dataverse becomes reachable by Copilot and custom agents

Agentic Dynamics 365: agents, MCP, and Copilot Credits

By mid-2026 Microsoft's product narrative for Dynamics 365 has shifted from "intelligent apps" to agentic business applications: systems of action where AI agents do not only summarise records but advance work under human-defined guardrails. Official Microsoft materials describe first-party agents across Sales, Customer Service, Contact Center, Field Service, Finance, Supply Chain, Project Operations, HR, and Business Central, with 2026 release wave 1 (April–September 2026) expanding role-based Sales and Finance agents in Microsoft 365 Copilot, Immersive Home workspaces in finance-and-operations apps, and broader agent supervision surfaces such as the agent feed in model-driven apps.

Model Context Protocol (MCP) is the integration surface that makes the platform agent-ready. Dynamics 365 MCP servers expose transactional actions so agents operate inside the same data models, business rules, security roles, and audit trails as interactive users — rather than bolting AI onto the side through one-off APIs. Microsoft has described over 650,000 MCP actions spanning sales, finance, supply chain, human resources, field service, customer service, and project operations. Partners use Copilot Studio, Power Apps, and MCP to ship domain agents (approvals, change orders, quality/recall tracing, forecast enrichment) without rebuilding governance for every scenario.

Licensing agents is not free with every seat. Many prebuilt and custom agents consume Copilot Credits. Dynamics 365 Finance Premium includes 1,000 Copilot Credits per user per month toward agent runtime; Business Central's Sales Order Agent and Payables Agent explicitly require Copilot Credits sold separately. Credits can be purchased pay-as-you-go (Azure subscription linked to the environment) or as prepaid commit units. For buyers mapping the estate, treat agents as a third cost layer after seats and tenant add-ons: confirm which agents are included with a SKU, which need credits, and which custom Copilot Studio agents will draw continuous consumption in production.

• →Agentic apps move Dynamics 365 from system-of-record to system-of-action under human guardrails
• →MCP servers let agents call transactional actions with the same permissions and audit trail as users
• →2026 wave 1 expands role-based Copilot agents, Immersive Home, and agent supervision in model-driven apps
• →Copilot Credits are the consumption meter for many prebuilt and custom agents — model them in TCO
• →Finance Premium includes 1,000 Copilot Credits/user/month; BC agents require credits sold separately

How Dynamics 365 licensing actually stacks

Dynamics 365 licensing is per app and per user, but it is not eleven independent prices added up — it follows a first-app / attach structure that rewards buying apps together. The first qualifying Dynamics 365 app a user needs is licensed at full price (the base license) and must be the highest-priced license for that named user. Additional qualifying apps for the same user are licensed as attaches at a steep discount — typically $20/user/month for customer-engagement apps (Sales, Customer Service, Field Service) and $30/user/month for heavier apps such as Finance, Supply Chain Management, Human Resources, and Project Operations. Team Member licenses at $8/user/month cover light users who only need read access, reference data, approvals, or self-service tasks. Device licenses exist for shared warehouse, retail, or kiosk terminals. This stacking is documented in Microsoft's Dynamics 365 licensing resources and the March 2026 licensing guide.

The implication for budgeting is significant. A service manager who needs Customer Service (full base), a slice of Field Service (attach at $20), and read access to Finance (Team Member at $8) does not pay three full prices. Conversely, a user who needs full CRM plus full Finance will pay the higher of the two as base plus the other as attach ($30 for Finance attach when CRM is base, or vice versa depending on which is highest). When modelling total cost, always price the first heavy app at base, additional qualifying apps as attaches, light users as Team Members, shared floors as device licenses where eligible, then layer Copilot Credits and any per-tenant items (Customer Insights base, Commerce e-commerce add-on, storage overage) on top. Exception worth knowing: users with Business Central Premium as base can often attach Sales Enterprise, Customer Service Enterprise, or Field Service at the $20 attach rate — a common SME path to "BC plus CRM" without two full CRM/ERP prices.

Two per-tenant costs and one consumption line sit outside the per-user model and catch buyers off guard. Customer Insights is priced per tenant ($1,700 base, $1,000 as an attach) with metered consumption on top. Commerce adds a $4,000/tenant e-commerce add-on regardless of seat count. Dataverse storage overage runs roughly $40/GB/month for Database capacity when you exceed included entitlements. Separately, many prebuilt and custom agents require Copilot Credits: Finance Premium includes 1,000 Copilot Credits per user per month for agent runtime; Business Central agents and many other agent scenarios bill credits via pay-as-you-go (Azure-linked) or prepaid commit units. A complete TCO model for a multi-app estate must include seats, attaches, tenant items, storage, and agent consumption — not just the marketing list price of the first app.

• →Base must be the highest-priced license for that user; attaches reuse the same app capabilities at $20 (CE) or $30 (F&O-class)
• →Business Central Premium as base often unlocks $20 attaches for Sales, Customer Service, or Field Service Enterprise
• →Team Member ($8) and device licenses cover light and shared-floor access — do not use them as cheap full-user seats
• →Customer Insights and Commerce e-commerce add-ons are tenant-level; Copilot Credits are consumption for agents
• →F&O license validation in 2025–2026 means assigned licenses matter for compliance, not just Entra group access
• →Total cost = per-user stack + tenant items + storage + agent credits; under-modelling attach and credits is the usual budgeting error

Security roles, environments, and ALM across the app map

The app map is incomplete without the control plane. Customer-engagement apps inherit Dataverse security: business units, security roles, team ownership, and field-level security define who can create, read, write, append, and delete each table. Because Sales, Customer Service, Field Service, Customer Insights journeys, and custom model-driven apps share those tables, a mis-scoped role is a multi-app problem — not a single-screen problem. Finance-and-operations apps use their own security framework (duties, privileges, and roles inside F&O) and only surface selected entities to Dataverse through dual-write maps. Plan security in both places when you run CRM + F&O together.

Application lifecycle management (ALM) for the Dataverse side uses solutions and environments. Development, test, and production should be separate environments with Dataverse; custom tables, forms, plugins, Power Automate flows, Copilot Studio agents, and security role changes ship as managed solutions through pipelines rather than click-ops in production. Microsoft Learn's Power Platform ALM guidance is explicit: every environment that participates in ALM needs a Dataverse database, and makers need at least Environment Maker rights in dev — not in production. F&O customisations follow a different ALM path (models, deployable packages, and Azure DevOps pipelines), which is another reason "one Dynamics 365 project" is often two delivery tracks with a dual-write seam.

Practical estate rules that prevent pain later: (1) name a system owner for Dataverse security roles and solution publishers; (2) never grant System Administrator as a convenience role for business users; (3) package role privilege changes in solutions so managed imports do not silently regress privileges; (4) treat dual-write table maps and initial sync as release-managed configuration; (5) include agent permissions in the same role design as human users so MCP and Copilot Studio actions cannot exceed what a person in that role could do. These habits matter more as agents increase the volume of automated writes against the same tables.

• →Dataverse security roles govern CRM apps, Power Apps, and many agents — design once, apply everywhere
• →F&O has its own security model; dual-write only exposes mapped tables into Dataverse
• →ALM for CE/Power Platform uses multi-environment solutions; F&O uses packages and separate pipelines
• →Package security role changes — privilege drift after imports is a common multi-app failure mode
• →Give agents least privilege equal to the human role they act for; do not run production agents as System Administrator

How to choose which Dynamics 365 apps you actually need

Most SMEs do not need all eleven apps — they need one or two that match how the business actually operates. Start from the function you are weakest in, not from the product list. If your pain is pipeline visibility and sales process, start with Dynamics 365 Sales. If your pain is after-sales support tickets, start with Customer Service. If your pain is end-to-end financials and operations as one SME system, start with Business Central rather than assembling the enterprise ERP apps. The first app sets your base license and your data tier; everything else is a candidate attach. Use the decision table below as a first filter, then validate with process depth (manufacturing, multi-entity, omnichannel retail, project accounting).

The Business Central versus modular-apps decision is the one almost every SME hits. Business Central is the right first answer for an SME that wants finance, sales, purchasing, and inventory in one system at $80–$110/user/month, with no dual-write project and optional CE attaches when Premium is the base. The modular F&O apps (Finance, SCM, Commerce, Project Operations) become the right answer when manufacturing depth, multi-entity financial complexity, or transaction volume pushes beyond what Business Central is designed to carry — at which point you are committing to a $210/user/month base (or about $240 for Finance + SCM on one user via $210 + $30 attach), dual-write if you also want CRM in Dataverse, and stricter F&O license assignment discipline. The CRM apps can be adopted independently of either ERP tier because they sit natively in Dataverse.

For teams already committed to the Microsoft stack — Microsoft 365, Teams, Copilot — the case for keeping CRM inside Dynamics 365 (rather than a standalone CRM) is the shared Dataverse backbone and the Copilot reach. For teams whose core operational system is not Microsoft, the case weakens: a Dataverse-centric architecture pays off when multiple Microsoft apps and Power Platform components consume the same data, and delivers less when only one app does. Because Flectic implements both Dynamics 365 and Odoo, we treat this as a fit question, not a vendor-preference question — some SMEs genuinely win with a multi-app Dynamics 365 estate, and others are better served by a single all-in-one system that keeps its data in one place without the licensing overhead.

• →Start from your weakest function — it sets your base license and data tier
• →For SME finance + operations as one system, Business Central is usually the right first answer
• →Modular F&O apps are justified by manufacturing depth, multi-entity complexity, or volume beyond Business Central
• →CRM apps can be adopted independently of either ERP tier (native Dataverse)
• →Price attaches and Copilot Credits when you model multi-app or agent-heavy estates
• →A Dataverse-centric architecture pays off when multiple Microsoft apps and Power Platform components consume the same data

Frequently asked questions