Real-time
Two-way sync
Changes in Datadog or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Business productivity
Datadog to Microsoft Dynamics 365 integration — real-time, two-way sync
Keep Datadog and Microsoft Dynamics 365 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Datadog and Microsoft Dynamics 365
Connect the tickets, records, and events in Microsoft Dynamics 365 to the systems engineering runs in Datadog, kept current in real time and in both directions.
Microsoft Dynamics 365 is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Datadog is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.
Stacksync syncs Products, Activities, Custom Tables, Accounts in Microsoft Dynamics 365 with Incidents, Service Level Objectives, Hosts, Monitors in Datadog field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.
Common use cases
- 01 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Pull the Hosts inventory into a CMDB or database for asset tracking, tag hygiene, and cost allocation across teams.
- 04 Sync Monitors and their alert state into Postgres so reliability teams query alert history and noisy-monitor trends in SQL.
Common sync patterns
One shared record across both systems
Where both systems keep records for the same contacts, items, or users, a correction in either updates the other, ending dual maintenance and keeping IDs aligned for every other flow.
Where Datadog tracks engineering work: requests become issues
A ticket or request raised in Microsoft Dynamics 365 opens or updates a matching issue in Datadog, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.
Where Datadog moves messages between services: activity lands on the stream
Records created or changed in Microsoft Dynamics 365 publish to the queue or topic in Datadog as they happen, so downstream services react to real events rather than polling for them.
What you can sync between Datadog and Microsoft Dynamics 365
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Datadog objects | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| Hosts Infrastructure host inventory with tags and metadata from the v1 host list API; loaded into a CMDB or warehouse for asset tracking, and hosts can be muted or unmuted via the API. | Activities Emails, calls, and tasks captured for engagement analytics. | Hosts is specific to Datadog and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Monitors Alert definitions with query, thresholds, and current state via the v1 Monitors API, which supports full create, update, and delete; Stacksync reads alert state into a warehouse or provisions and updates monitors from a config source. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Monitors is specific to Datadog and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Logs Log events searched via the v2 Logs search endpoint by time window and submittable through the log intake API; commonly streamed to a warehouse for retention beyond Datadog's storage period. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Logs is specific to Datadog and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Events The event stream (deploys, alerts, comments) searched via the v2 Events endpoint and posted via POST /api/v1/events; used to correlate deploy and incident timelines or to publish deploy and pipeline events into Datadog. | Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Events is specific to Datadog and Contacts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Dashboards Dashboard definitions and widgets via the v1 Dashboards API with full CRUD; exported for backup and audit, or created and updated programmatically from a source of truth. | Leads Inbound records enriched and routed from external sources into sales queues. | Dashboards is specific to Datadog and Leads to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Metrics Time-series metrics queried in aggregate windows through the query API and submitted via POST /api/v1/series; individual raw points cannot be extracted beyond retention. | Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Metrics is specific to Datadog and Opportunities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
How changes propagate between Datadog and Microsoft Dynamics 365
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Datadog Microsoft Dynamics 365 Sub-second propagation
DetectionDatadog notifies Stacksync of record changes through webhook events. Polling with time-windowed search queries on Logs and Events (timestamp cursor).
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Datadog Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to Datadog through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Datadog: Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
What ships with Datadog ⇄ Microsoft Dynamics 365
Connect Datadog and Microsoft Dynamics 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Datadog–Microsoft Dynamics 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Datadog or Microsoft Dynamics 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Datadog or Microsoft Dynamics 365 record.
Observability
Monitoring
Track your Datadog ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Datadog and Microsoft Dynamics 365.
How the Datadog and Microsoft Dynamics 365 connectors work
Datadog
- Integration surface
- REST API (v1 and v2)
- Authentication
- API key (DD-API-KEY) plus an Application key (DD-APPLICATION-KEY) sent as request headers; application keys are tied to the creating user and inherit that user's permissions and authorization scopes.
- Change detection
- Polling with time-windowed search queries on Logs and Events (timestamp cursor); monitor alerts can also push via the Webhooks notification integration. No modified-date CDC on mutable objects.
- Capabilities
- read · write · webhooks
- Rate limits
- Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
How it works
How to connect Datadog to Microsoft Dynamics 365 — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Datadog and Microsoft Dynamics 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Datadog
connected
Microsoft Dynamics 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Datadog and Microsoft Dynamics 365 objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Datadog ⇄ Microsoft Dynamics 365Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Datadog Microsoft Dynamics 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Datadog and Microsoft Dynamics 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Datadog and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Datadog's Hosts and Monitors), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Datadog and Microsoft Dynamics 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Datadog–Microsoft Dynamics 365 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Datadog and Microsoft Dynamics 365. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Datadog: Polling with time-windowed search queries on Logs and Events (timestamp cursor); monitor alerts can also push via the Webhooks notification integration. No modified-date CDC on mutable objects. On Microsoft Dynamics 365: Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft Dynamics 365 side: Products, Activities, Custom Tables, Accounts, plus custom fields where Microsoft Dynamics 365 exposes them. On the Datadog side: Incidents, Service Level Objectives, Hosts, Monitors. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 392 integrations available for Datadog and Microsoft Dynamics 365.
Popular · 8 of 392
-
Datadog ⇄ Quip -
Datadog ⇄ Smartsheet -
Datadog ⇄ Sysaid -
Datadog ⇄ Wrike -
Microsoft Dynamics 365 ⇄ PagerDuty -
Microsoft Dynamics 365 ⇄ Jira -
Microsoft Dynamics 365 ⇄ Rabbitmq -
Microsoft Dynamics 365 ⇄ Azure Service Bus
No integrations match .
