Dynamics 365 Enterprise Integration: The Complete Guide
Enterprise integration patterns for Dynamics 365. Dataverse, dual write, Power Platform, Azure middleware, multi-ERP consolidation, M&A playbooks, and third-party connectors for Salesforce, SAP, Shopify, and more.
- Shared Data Layer
- Microsoft Dataverse (formerly Common Data Service) — relational cloud database underlying all CRM apps and Power Platform
- F&O Integration
- Dual write (near-real-time bidirectional), virtual entities (read on demand), business events (event-driven), OData APIs (custom)
- BC Integration
- Dataverse sync, Power Automate connectors, REST APIs, AL-based web services, Shopify native connector
- Low-Code
- Power Automate (1,000+ connectors), Power Apps, Power BI — all native Dataverse integration
- Enterprise Middleware
- Azure Logic Apps, Azure Service Bus, Azure API Management, Azure Functions
- Analytics Pipeline
- Azure Synapse Link exports Dataverse data continuously to Synapse/Fabric in Delta Lake format
- Pre-Built Connectors
- 1,000+ in Power Platform; native connectors for Salesforce, SAP, Shopify, ServiceNow, Workday, and more
- MCP Support
- Dynamics 365 ERP MCP Server (2025) exposes ERP operations as agent-accessible capabilities
- Last Updated
- March 2026
The Dynamics 365 Integration Landscape
Integration is the single largest source of complexity — and budget overruns — in enterprise Dynamics 365 deployments. Organizations rarely run Dynamics 365 in isolation. They connect it to e-commerce platforms, HR systems, banking APIs, shipping providers, CRM data, warehouse systems, and often other ERP instances acquired through M&A activity. Getting integration right requires understanding which pattern fits each use case, because Microsoft provides at least five distinct integration mechanisms, each with different trade-offs.
This hub covers every major integration pattern in the Dynamics 365 ecosystem: from the foundational Dataverse platform that unifies data across CRM and Power Platform, to dual write for bridging Finance & Operations with customer engagement apps, to Azure-based middleware for enterprise-scale event-driven architectures, to practical patterns for connecting non-Microsoft systems like Salesforce, SAP, and Shopify.
The Five Core Integration Patterns
Every Dynamics 365 integration falls into one of five patterns. Choosing correctly avoids over-engineering simple scenarios and under-engineering complex ones:
| Pattern | Best For | Latency | Direction | Complexity |
|---|---|---|---|---|
| Dataverse Native | CRM apps, Power Platform, model-driven apps | Real-time | Bidirectional | Low |
| Dual Write | F&O ↔ Dataverse/CRM bidirectional sync | Near-real-time (~seconds) | Bidirectional | Medium-High |
| Virtual Entities | Read F&O data from Dataverse without copying | On-demand | Read (CRUD via OData) | Low-Medium |
| Power Automate / Logic Apps | Event-driven workflows, scheduled syncs, low-code | Seconds to minutes | Configurable | Low-Medium |
| Custom API / Azure Middleware | High-volume, complex transformations, enterprise bus | Configurable | Configurable | High |
For detailed guidance on each pattern, see the individual spoke pages linked throughout this guide.
Dataverse: The Shared Data Foundation
Microsoft Dataverse (formerly Common Data Service / CDS, rebranded in late 2020) is the relational cloud database that underpins every Dynamics 365 CRM application (Sales, Customer Service, Field Service, Customer Insights) and the entire Power Platform. Understanding Dataverse is prerequisite to understanding any Dynamics 365 integration, because it’s the data layer that everything connects through.
What Dataverse Provides
- Unified schema: Standardized tables (Accounts, Contacts, Leads, Opportunities, Cases) shared across all CRM apps
- Security model: Role-based access control, field-level security, business unit hierarchy — inherited by all apps and integrations
- API surface: REST/OData Web API and SOAP-based Organization Service for programmatic access
- Event system: Webhooks, plug-ins, and business events for real-time integration triggers
- Connector ecosystem: 1,000+ Power Automate/Logic Apps connectors for SaaS integration
For the complete Dataverse deep dive — architecture, tables, security, APIs, and when to extend vs. customize — see our What Is Microsoft Dataverse? guide.
Finance & Operations Integration
Finance & Operations apps (Finance, Supply Chain Management, Commerce, HR) run on a separate technical infrastructure from Dataverse-based CRM apps. Bridging these two platforms is one of the most important — and most complex — integration challenges in the Dynamics 365 ecosystem.
Dual Write
Dual write provides near-real-time, bidirectional synchronization between F&O and Dataverse. When a record changes in F&O, it’s automatically written to Dataverse (and vice versa). This is the recommended pattern when CRM and ERP users need to work with the same data in real time — for example, creating a customer in Sales and having it instantly available in Finance for invoicing.
The 2025 Release Wave 2 introduced asynchronous dual write, which decouples the write operations for better performance and resilience. This means integrations must now account for eventual consistency rather than assuming immediate sync.
Virtual Entities
Virtual entities let Dataverse-based apps query F&O data on demand without copying it. The data stays in F&O and is accessed through the standard OData interface. This pattern is ideal when you need to display F&O data in a Power App or model-driven app but don’t need it permanently stored in Dataverse.
Business Events & Data Events
F&O can publish events when business processes complete (e.g., purchase order confirmed, invoice posted). These events can trigger Power Automate flows, Azure Service Bus messages, or Azure Event Grid subscriptions for downstream processing.
For the complete dual write and virtual entities guide, see our Dual Write & Virtual Entities deep dive.
Power Platform Integration
The Power Platform (Power Automate, Power Apps, Power BI, Power Pages) is Microsoft’s low-code layer that extends Dynamics 365 without custom development. For integration specifically, Power Automate and Power Apps are the primary tools:
- Power Automate: Workflow automation with 1,000+ pre-built connectors. Trigger flows from Dynamics 365 events (record created, field changed, approval needed) and push data to external systems — or pull data in on a schedule. Supports business process flows, approval chains, and AI Builder actions.
- Power Apps: Build custom apps that read/write Dynamics 365 data through Dataverse connectors. Model-driven apps use Dataverse natively; canvas apps can connect to any data source including F&O OData endpoints.
- Power BI: Embedded analytics with DirectQuery to Dataverse or Azure Synapse Link for large datasets. Pre-built D365 content packs provide out-of-box dashboards.
For the complete Power Platform integration guide, see our Power Platform & Dynamics 365 Integration deep dive.
Azure Integration Services (Enterprise Middleware)
For high-volume, complex, or mission-critical integrations, Azure Integration Services provides enterprise-grade middleware:
| Azure Service | Use Case | D365 Integration Pattern |
|---|---|---|
| Logic Apps | Workflow orchestration, B2B (EDI/AS2), scheduled data sync | D365 connector triggers and actions, HTTP/REST calls |
| Service Bus | Message queuing, pub/sub, decoupled event processing | F&O business events to Service Bus topics; reliable async messaging |
| API Management | API gateway, rate limiting, security, developer portal | Facade over D365 OData endpoints; unified API surface for external consumers |
| Azure Functions | Serverless compute for transformation, validation, enrichment | Event-driven processing triggered by Service Bus, webhooks, or timers |
| Azure Data Factory | ETL/ELT, bulk data movement, data warehouse loading | Batch extract from D365 via OData or Data Management Framework (DMF) |
| Synapse Link | Continuous data export for analytics | Near-real-time replication of Dataverse data to Synapse/Fabric in Delta Lake format |
The key principle: use Azure Service Bus to decouple Dynamics 365 from downstream systems. This avoids API rate limit issues, provides retry/dead-letter handling, and lets you scale consumers independently. For the complete middleware guide, see our API & Middleware Integration Patterns deep dive.
Multi-ERP & M&A Consolidation
Private equity-backed companies and serial acquirers frequently face the challenge of integrating acquired entities running different ERP systems — sometimes multiple Dynamics instances, sometimes a mix of Dynamics, SAP, NetSuite, and legacy systems. Two common patterns emerge:
Pattern 1: Consolidate onto One Platform
Migrate all acquired entities to a single Dynamics 365 instance (Business Central for SMB, Finance for enterprise). This provides unified reporting, standardized processes, and lower ongoing maintenance — but takes 6–18 months per entity and disrupts operations during migration.
Pattern 2: Integrate at the Data Layer
Keep each entity on its current ERP and build integration middleware (Azure Integration Services or iPaaS) to synchronize master data, financial consolidation, and cross-entity workflows. Faster to implement, lower disruption, but higher ongoing maintenance and data quality challenges.
Most organizations use a phased approach: immediate data-layer integration for financial consolidation (Pattern 2), followed by rolling platform consolidation (Pattern 1) over 2–5 years. For detailed M&A playbooks and multi-ERP patterns, see our Multi-ERP Integration Patterns and M&A ERP Consolidation guides.
Third-Party & Non-Dynamics Integration
The most common third-party integrations in the Dynamics 365 ecosystem include:
- Shopify: Native Business Central connector for orders, inventory, customers, and fulfillment sync. The most popular e-commerce integration in the BC ecosystem.
- Salesforce: Power Automate and custom middleware for CRM data sync. Common in organizations migrating from Salesforce CRM while keeping D365 for ERP.
- SAP: Azure Integration Services with SAP connector for master data and transaction sync. Critical for organizations running SAP alongside Dynamics 365.
- ServiceNow: Power Automate connectors for ITSM ticket sync with D365 Customer Service.
- Workday: HR data integration with D365 HR or custom employee master sync to Finance.
- Banking APIs: Direct bank feed integration for automated reconciliation in Business Central and Finance.
- EDI: Azure Logic Apps B2B module for X12/EDIFACT electronic data interchange with trading partners.
For the complete third-party integration guide with architecture patterns and connector comparisons, see our Third-Party & Non-Dynamics Integration deep dive.
MCP & Agentic Integration (2025–2026)
The newest integration paradigm is the Model Context Protocol (MCP), which Microsoft has adopted for Dynamics 365. The Dynamics 365 ERP MCP Server (announced November 2025) exposes core ERP operations — financial queries, inventory checks, order creation, customer lookups — as capabilities that AI agents can discover and execute. This enables autonomous agents to interact with Dynamics 365 data without human intervention, opening new patterns for intelligent automation across the enterprise.
Similarly, the Commerce MCP Server (preview 2026) exposes catalog, pricing, promotions, cart, and fulfillment operations for conversational commerce agents. This represents a fundamental shift from API-centric integration to agent-centric integration, where AI systems negotiate capabilities and execute workflows across enterprise applications.
Choosing the Right Integration Pattern
Use this decision framework to select the appropriate integration pattern:
| Scenario | Recommended Pattern | Why |
|---|---|---|
| CRM + Power Platform apps sharing data | Dataverse native | Already the shared data layer; no integration needed |
| F&O + CRM real-time bidirectional sync | Dual write | Purpose-built for this exact scenario |
| Display F&O data in Power Apps without copying | Virtual entities | No data duplication, read on demand |
| Simple event-driven workflows (under 50K records/day) | Power Automate | Low-code, fast to build, 1,000+ connectors |
| Complex orchestration or B2B (EDI) | Logic Apps | Enterprise workflow engine with B2B capabilities |
| High-volume async messaging (>50K events/day) | Service Bus + Azure Functions | Decoupled, scalable, dead-letter handling |
| Bulk data movement or ETL | Data Factory + Synapse Link | Batch processing, data warehouse loading |
| Multi-ERP financial consolidation | Azure middleware + reporting layer | Cross-platform data normalization |
| AI agent access to ERP data | MCP Server | Agent-native capability discovery and execution |
All Articles in Enterprise Integration
What Is Microsoft Dataverse? The Complete Guide for Dynamics 365 Users (2026)
Complete guide to Microsoft Dataverse for Dynamics 365. Learn what is Dataverse, architecture, security, APIs, and how it connects Dynamics 365 CRM, F&O, & Business Central.
Power Platform & Dynamics 365 Integration: The Complete Guide (2026)
Master Power Platform integration with Dynamics 365 in 2026. Learn Power Automate, Power Apps, Power BI, Power Pages, & Copilot Studio with real-world examples.
Dynamics 365 API & Middleware Integration Patterns: Azure Logic Apps, Service Bus & Beyond (2026)
Master D365 API integration patterns with Azure Logic Apps, Service Bus, API Management, and Functions. Complete 2026 guide to middleware, security, and iPaaS alternatives.
Dual Write & Virtual Entities in Dynamics 365: The Complete Guide (2026)
Learn dual write setup, virtual entities, and bidirectional sync between F&O & Dataverse. Covers 2025 Release Wave 2 async updates, best practices, & performance tuning.
Multi-ERP Integration Patterns: Connecting Dynamics 365 Across the Enterprise (2026)
Learn multi-ERP integration patterns for Dynamics 365: multi-company strategies, cross-platform connectivity, master data sync, financial consolidation, and modern iPaaS solutions.
M&A ERP Consolidation: The Dynamics 365 Playbook for Mergers & Acquisitions (2026)
Strategic playbook for post-merger ERP consolidation using Dynamics 365. Day 1 requirements, phased integration, PE portfolio standardization, cost benchmarks, and partner selection.
Third-Party & Non-Dynamics Integration: Connecting Salesforce, SAP, Shopify & More to D365
Complete guide to integrating third-party systems with Dynamics 365: Shopify, Salesforce, SAP, ServiceNow, Workday, EDI, and iPaaS platforms.
Frequently Asked Questions
Microsoft Dataverse (formerly Common Data Service / CDS) is the cloud-based relational database that underpins all Dynamics 365 CRM applications and the Power Platform. It provides a unified data schema, role-based security, REST/OData APIs, and an event system (webhooks, plug-ins) that all CRM apps and Power Platform tools share. Think of it as the data foundation layer — when Sales, Customer Service, and Power Apps all read from "Accounts," they're reading from the same Dataverse table.
Dual write is a near-real-time, bidirectional synchronization framework that bridges Finance & Operations apps with Dataverse (and therefore CRM apps). When you create or update a record in F&O, dual write automatically writes that change to Dataverse — and vice versa. The 2025 Release Wave 2 introduced asynchronous dual write for better performance, meaning integrations should now account for eventual consistency rather than immediate sync.
Yes. The most common pattern uses Power Automate with the Salesforce connector for CRM data synchronization, or Azure Logic Apps for higher-volume scenarios. Typical integration points include syncing accounts/contacts, opportunities, and cases between Salesforce CRM and Dynamics 365. For organizations migrating from Salesforce, a phased approach is common — integrate first, migrate later.
Azure Synapse Link continuously replicates Dataverse data to Azure Synapse Analytics or Microsoft Fabric using change tracking. Data arrives in Delta Lake format within minutes of changes in Dataverse, with zero performance impact on Dynamics 365 operations. This is the recommended pattern for analytics, data warehousing, and AI/ML workloads that need access to Dynamics 365 data without impacting transactional performance.
Business Central and Finance & Operations are separate platforms and don't use dual write for integration. The recommended approach is Power Automate or Azure Logic Apps for workflow-based integration, custom APIs for programmatic access, or Azure Data Factory for bulk data movement. Many organizations running both products use an Azure Service Bus as a message broker to decouple the systems and handle data transformation between BC's AL-based web services and F&O's OData endpoints.
The Dynamics 365 ERP MCP Server (announced November 2025) uses the Model Context Protocol to expose core ERP operations — financial queries, inventory checks, order creation, customer lookups — as agent-accessible capabilities. This allows AI agents (including Copilot and third-party agents) to discover and execute ERP operations autonomously, without requiring custom API integration for each use case. It represents a shift from traditional API integration to agent-native integration.
Integration costs vary enormously. Simple Power Automate flows connecting two cloud systems might cost $5,000-$15,000 to implement. Enterprise middleware architectures using Azure Service Bus, Logic Apps, and custom APIs typically range from $50,000-$250,000+ depending on the number of integration points, data volumes, transformation complexity, and error handling requirements. Integration commonly represents 20-40% of total implementation budget for complex multi-system deployments.