Skip to content
Data warehouse ⇄ Developer tools

Azure Synapse Analytics to Datadog integration — real-time, two-way sync

Keep Azure Synapse Analytics and Datadog 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 Azure Synapse Analytics and Datadog

Close the gap between analytics and operations: Azure Synapse Analytics holds the record while Datadog runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Azure Synapse Analytics is the central store where teams keep Views, Schemas, Materialized views, SQL pools for reporting and analysis; Datadog runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Service Level Objectives, Hosts, Monitors, Logs produced in Datadog are exactly what analysts want to measure in Azure Synapse Analytics, and the curated rows in Azure Synapse Analytics are what should drive the next action in Datadog. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Views, Schemas, Materialized views, SQL pools in Azure Synapse Analytics with Service Level Objectives, Hosts, Monitors, Logs in Datadog field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Publish warehouse aggregates (account health scores, LTV) from Synapse back into operational tools like a CRM.
  • 02 Sync curated Synapse views into an operational Postgres or Azure SQL database that applications can query cheaply.
  • 03 Provision and update Datadog Monitors from a config database or Git so alert definitions stay consistent across teams and environments.
  • 04 Publish deploy and pipeline Events, and submit custom Metrics, into Datadog from CI/CD or a data pipeline to enrich dashboards and correlation.

Common sync patterns

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where Datadog manages users, directory, or access data, those records stay current in Azure Synapse Analytics — and can be provisioned back from it — so ownership and permissions match across both.

What you can sync between Azure Synapse Analytics and Datadog

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.

Azure Synapse Analytics objects Datadog objects How this pairing syncs
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. 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. External tables is specific to Azure Synapse Analytics and Dashboards to Datadog — each maps to any object or custom field on the other side.
Views Curated projections used when downstream tools should not read base tables directly. 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. Views is specific to Azure Synapse Analytics and Metrics to Datadog — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. Incidents Incident records from the v2 Incidents API with full CRUD, including status and timeline fields; landed in a database for MTTR reporting or created and updated from an external incident workflow. Schemas is specific to Azure Synapse Analytics and Incidents to Datadog — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. Service Level Objectives SLO definitions and status history via the v1 SLO API with full CRUD; read out for reliability and error-budget reporting, or provisioned and updated from a reliability config. Materialized views is specific to Azure Synapse Analytics and Service Level Objectives to Datadog — each maps to any object or custom field on the other side.
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. 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. SQL pools is specific to Azure Synapse Analytics and Hosts to Datadog — each maps to any object or custom field on the other side.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. 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. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Monitors to Datadog — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics and Datadog

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.

Azure Synapse Analytics Datadog Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

DeliveryEach detected change is written to Datadog through its API, with automatic retries and rate-limit backoff.

Datadog Azure Synapse Analytics 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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

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 Azure Synapse Analytics ⇄ Datadog

Connect Azure Synapse Analytics and Datadog for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Datadog connection.

Real-time

Two-way sync

Changes in Azure Synapse Analytics or Datadog instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Synapse Analytics or Datadog 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 Azure Synapse Analytics or Datadog record.

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ Datadog sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Datadog.

How the Azure Synapse Analytics and Datadog connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

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.
How it works

How to connect Azure Synapse Analytics to Datadog — 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.

  1. 01

    Connect your apps

    Authenticate Azure Synapse Analytics and Datadog with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Synapse Analytics connected
    Datadog connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics and Datadog 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Synapse Analytics ⇄ Datadog
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Synapse Analytics Datadog
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Synapse Analytics and Datadog integration FAQ

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 420 integrations available for Azure Synapse Analytics and Datadog.

Popular · 8 of 420
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.