Integrations architecture

Connecting Dynamics 365 to the rest of the world — patterns, Azure services, resilience, and observability for real production integrations.

For: Integration architects and developers building production integrations.

12 guides in this path

  1. 1
    Integration 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. 2
    Event-driven architecture for Dynamics 365How to design event-driven integrations around Dynamics 365 — event sources, brokers, consumers, and the patterns that produce loosely coupled, scalable architectures.
  3. 3
    Polling vs push patterns for Dynamics 365 integrationsHow to choose between polling and push integration patterns for Dynamics 365 — trade-offs, performance, freshness, and when each fits.
  4. 4
    Anti-corruption layers for Dynamics 365 integrationsHow anti-corruption layers protect Dynamics 365 from external system model leakage — translation patterns, when to apply ACL, and the maintenance discipline.
  5. 5
    Azure Service Bus integration with DataverseHow Dataverse publishes change events to Azure Service Bus — registration, message format, queues vs topics, and resilient consumer patterns.
  6. 6
    Webhooks vs events in DataverseHow Dataverse exposes change notifications — webhooks, service endpoints to Azure Service Bus / Event Hub / Event Grid, and the trade-offs in reliability and scale.
  7. 7
    Idempotency in Dynamics 365 integrationsWhy integrations must be idempotent — patterns for safe retries, deduplication, correlation IDs, and the design principles that prevent duplicates and inconsistencies.
  8. 8
    Retry policies with Azure services for Dynamics 365 integrationsHow to implement retry policies in Azure-based Dynamics 365 integrations — exponential backoff, idempotency, circuit-breaker integration, and the patterns that handle transient failures gracefully.
  9. 9
    Circuit breakers in Dynamics 365 integrationsHow the circuit-breaker pattern protects Dynamics 365 integrations from cascading failures — implementation in Azure Functions, Logic Apps, and Dataverse plug-ins, with operational tuning.
  10. 10
    Message replay and poison queue handling for Dynamics 365 integrationsHow to design Dynamics 365 integrations that survive transient failures and handle poison messages — dead-letter queues, replay tooling, idempotency, and the operational rhythms.
  11. 11
    Observability for Dynamics 365 integrationsHow to build observability into Dynamics 365 integrations — logs, metrics, traces, correlation IDs, and the patterns that make production integration health visible.
  12. 12
    OpenTelemetry with Dynamics 365 integrationsHow OpenTelemetry standardises observability in Dynamics 365 architectures — instrumentation, exporters, distributed tracing, and the path to vendor-neutral observability.
← All pathsBrowse all guides →