Integration guides

Integrating Dynamics 365 with Azure, partner systems, and the web — patterns, messaging, APIs, identity, resilience, and the Azure services that carry the load.

71 guides · Last updated 2026-09-02

Every Dynamics 365 estate integrates with something: an ERP across the CRM line, a bank, a web shop, a data lake, SAP, Salesforce, a legacy system with no API. This section is the architecture reference for that work — the patterns (outbox, saga, idempotency, CQRS, anti-corruption layers, polling versus push), the messaging and eventing options (Service Bus, Event Grid, webhooks, business events), and the API surfaces on each product.

The Azure services sub-section covers Functions, Logic Apps, Data Factory, Synapse Link, Fabric, and the virtual network data gateway. API and identity covers Graph, APIM in front of Dataverse, batch operations, and external identity. Resilience and ops covers retries, circuit breakers, observability, OpenTelemetry, and integration testing. Third-party systems covers the named integrations — SAP S/4HANA, Salesforce, NetSuite, HubSpot, Snowflake, Databricks, Shopify, Stripe, Twilio, and more.

Start with the CRM integration patterns overview and the Azure services overview, then the pattern that matches your reliability requirement. If your integration is F&O to Dataverse, dual-write in the Finance & SCM section is the starting point.

Start here

  1. 1Integration patterns for Dynamics 365 CRMThe standard integration patterns for CRM-side Dynamics 365 — webhooks, Dataverse plug-ins, Service Bus integration, virtual tables, and pull vs push.
  2. 2Integrating Dynamics 365 with Azure servicesHow Dynamics 365 plugs into Azure — Service Bus, Logic Apps, Functions, API Management, Event Grid, and the iPaaS patterns that actually work.
  3. 3Azure Service Bus integration with DataverseHow Dataverse publishes change events to Azure Service Bus — registration, message format, queues vs topics, and resilient consumer patterns.
  4. 4Webhooks vs events in DataverseHow Dataverse exposes change notifications — webhooks, service endpoints to Azure Service Bus / Event Hub / Event Grid.
  5. 5Idempotency in Dynamics 365 integrationsWhy integrations must be idempotent — patterns for safe retries, deduplication, correlation IDs.
  6. 6The outbox pattern with Service BusA resilient integration pattern for Dynamics 365 — combining an outbox table with Service Bus to deliver guaranteed-once messaging across systems.
  7. 7The Business Central API and OData servicesHow external systems talk to Business Central — the v2.0 REST API, OData web services, bound actions, and call limits.
  8. 8Microsoft Fabric and Dynamics 365How Microsoft Fabric and OneLake change Dynamics 365 analytics — Synapse Link, lakehouses, and the migration from Export to Data Lake.
  9. 9Azure Synapse Link for DataverseHow Synapse Link replicates Dataverse data to Azure Data Lake Storage continuously — architecture, configuration, query patterns.
  10. 10Integrating Dynamics 365 with SAP S/4HANA: two-tier ERP patternsHow Dynamics 365 Finance, Supply Chain, or Business Central coexists with SAP S/4HANA at group level — what to integrate, which SAP interfaces to use.

All Integrations guides

Architecture patterns →(14)

Azure services →(8)

API & identity →(14)

Data movement →(14)

Third-party systems →(8)

Other sections