ERP in the Microsoft Ecosystem — what Business Central, Dynamics 365 and the Power Platform deliver together.

Microsoft has consistently built an integrated business application ecosystem in recent years: Microsoft 365 as productivity backbone, Dynamics 365 as a family of ERP and CRM apps, Power Platform as the development and automation layer in between. For mid-market selection projects this raises a different question than pure ERP comparisons: how deep do I commit? This profile shows what Business Central delivers as the core, which modules dock on usefully, what the Power Platform really contributes – and where the stack hits its limits. Related strategic topics: Suite vs. Best-of-Breed and ERP selection in multi-entity structures.

1. What "Microsoft ecosystem" really means for ERP selection

The Microsoft stack is not a single product but a constellation. Four layers belong together:

• Microsoft 365. Office, Outlook, Teams, SharePoint, OneDrive – the productivity layer where employees already work daily.
• Dynamics 365. Family of business apps. In ERP: Business Central (mid-market) and Finance & Operations (enterprise). In CRM: Sales, Customer Service, Field Service, Marketing.
• Power Platform. Power Automate (workflow automation), Power BI (reporting), Power Apps (low-code development) and Copilot Studio. Connects the apps and extends them without classical programming.
• Azure. The cloud platform underneath. For pure SaaS users mostly not directly relevant, for hybrid setups and data integration decisive.

The promise: a single integrated data model (Microsoft Dataverse), a single identity system (Entra ID, formerly Azure AD), a single compliance layer. What works in detail and what doesn't depends heavily on which apps are actually deployed and how cleanly the connections are designed.

2. Business Central as the ERP core

Business Central (BC) is Microsoft's mid-market ERP – successor to Dynamics NAV (Navision). The solution is offered as SaaS in the Microsoft cloud, optionally as on-premise installation. In the German mid-market, by far the most frequently considered system after SAP.

What Business Central delivers as standard

• Financial accounting with German localisation and DATEV connection
• Order processing, sales, purchasing, inventory
• Light manufacturing (BOMs, routings, variant logic)
• Projects and service orders
• Multi-tenant capability for multiple legal entities
• Native integration with Excel, Outlook, Teams

What BC explicitly is not

Business Central is not designed for upper enterprise logic. Multi-entity with consolidated reporting, parallel books under IFRS and HGB, heavy manufacturing with MES integration – these are fields where D365 Finance & Operations or classical enterprise ERPs (NetSuite OneWorld, SAP S/4HANA) are closer to the requirement. Anyone who wants to consolidate from the second or third country onwards should clarify this early in the architecture question (see Group consolidation in the mid-market).

3. Dynamics 365 Sales, Service, Marketing as edge apps

Here the Microsoft stack becomes interesting: anyone using Business Central as ERP can optionally add Dynamics 365 Sales (CRM for sales), Customer Service (tickets, service cases) and Marketing (customer insights, journey orchestration). The apps share the data model (Dataverse) and are technically tightly integrated – having created a customer in BC means seeing that customer in the Sales module too.

This is effectively a suite-in-the-stack model: Microsoft positions the components as an integrated family, but each component is technically its own app with its own licence. In the classical sense (see Suite vs. Best-of-Breed) it is a hybrid with ERP core and edge apps, except all edge apps come from the same vendor.

When this makes sense

If the sales requirements are classical (lead management, pipeline, field force steering), if the service business should be run in a structured way, or if marketing automation suffices for DACH mid-market needs – then Dynamics 365 Sales/Service is often the most resource-efficient choice, because implementation and operations can be planned together with BC.

When it doesn't fit

If marketing requirements are highly specialised (performance marketing, marketing attribution, B2C CDPs), a dedicated tool – HubSpot, Salesforce Marketing Cloud, Adobe – almost always beats the Microsoft Marketing module. In B2B sales with complex configurators, Salesforce is typically deeper.

4. Power Platform: Automate, BI, Apps

The Power Platform is what distinguishes Microsoft setups from competitors in practice. In short: what a suite cannot do as standard can often be supplemented with Power Automate as a workflow or Power Apps as a low-code application, without classical development effort.

• Power Automate. Workflow automation between Microsoft apps and third-party systems. Classic use case: order intake in BC → notification in Teams → task in Planner → approval via Outlook.
• Power BI. Reporting and analysis – the de facto standard reporting tool in the Microsoft universe. Direct connection to BC and Dataverse, without ETL.
• Power Apps. Low-code platform for own business applications when standard apps don't suffice. Example: a simple mobile tool for warehouse inventory, built in half a day, integrated with BC.
• Copilot Studio. AI assistants for internal and customer-facing processes. Early phase, growing field.

Important: the Power Platform is not free. Licence costs come per user per month, depending on the use of premium connectors, Dataverse storage and AI features. In honest TCO calculations (see ERP cost and effort) this always belongs in the calculation.

5. Typical mid-market setups

Three setups regularly seen in German mid-market selection projects:

Setup A: BC + M365 + Power BI

Classic entry point. Business Central as ERP, Microsoft 365 already in place, Power BI for reporting. Dynamics 365 Sales/Service either doesn't come at all or only in a second phase. Most common mid-market footprint.

Setup B: BC + Sales + Power Automate

When sales is to be run in a structured way, Sales is added. Power Automate connects the two in both directions: a lead from Sales generates a customer in BC after closing, order data from BC is reflected in Sales pipelines.

Setup C: D365 F&O + Sales/Service + Power Platform

Enterprise setup for upper mid-market and enterprise. Instead of BC, Finance & Operations serves as the ERP backbone. Multiple entities, parallel books, international rollout (see international ERP rollout) – this is the field where D365 F&O competes with NetSuite and SAP S/4HANA.

6. When the Microsoft stack fits, when it doesn't

Strong with

• Classical German mid-market with 50–500 employees
• Existing Microsoft 365 infrastructure
• Standard processes without deep industry specifics
• IT strategies that consolidate on a single vendor
• Requirements that can be extended with low-code (Power Apps, Power Automate)
• Migrations from Dynamics NAV, AX or older Microsoft solutions

Weak or unsuitable with

• Group-wide consolidation with multi-GAAP (BC too narrow, F&O very involved)
• Heavy regulated industry manufacturing with MES depth
• Highly specialised e-commerce setups (see ERP for e-commerce and D2C – Xentral or NetSuite closer to the requirement)
• Pure open-source strategies with data sovereignty focus (see Open-source ERP in the mid-market)

7. Relevant Microsoft solutions

8. Frequently asked questions about the Microsoft ecosystem

Is Business Central worthwhile if we don't use Microsoft 365?

Possible, but below average attractive. Most BC advantages come from M365 integration (Outlook integration of documents, Excel connection, Teams channels for orders). Anyone without M365 should benchmark BC neutrally against NetSuite, Odoo and Weclapp.

What does a BC setup cost in the mid-market?

Typically mid-five-figure to lower-six-figure range in year one for 50–150 users, depending on modules, localisation and partner. Full TCO view: ERP cost and effort.

When does it make sense to switch from BC to D365 F&O?

When the company becomes multi-entity (several operating companies), when parallel books under IFRS and HGB are required, when heavy manufacturing with MES requirements emerges, or when international rollouts loom. The switch is substantial – not an update but a re-implementation.

How deep does the Power Platform belong in the selection process?

As deep as the customisation depth requires. Anyone using standard BC with standard Sales gets by with Power Automate for a few workflows. Anyone planning own business apps (mobile warehouse app, field service tool) should include Power Apps and premium connectors early in the selection – including licence considerations.

What about Copilot in Dynamics 365?

Copilot is being integrated into all Dynamics 365 apps (Outlook integration, Sales insights, Field Service helper). In the 2026 mid-market still under evaluation, not a prerequisite. Useful as an optional differentiator, not a selection criterion.

---

Note: This profile does not replace an individual project assessment. The patterns and recommendations described are experience values from selection projects in the German-speaking mid-market.

Author: Joerg H. Paul Schaefer · As of: May 2026 · erp-check.info is a vendor-neutral information platform.