Skip to content
AI ⇄ Data warehouse

Azure OpenAI to MotherDuck integration — real-time data sync

Keep Azure OpenAI and MotherDuck 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 OpenAI and MotherDuck

Flow Azure OpenAI data into MotherDuck in real time — no exports, no schedulers, no custom scripts.

Azure OpenAI is a read-only source: Stacksync reads its data in real time and delivers it into MotherDuck, so MotherDuck always reflects the current state of Azure OpenAI — without exports, scripts, or schedulers.

MotherDuck holds the raw records the business runs on; Azure OpenAI turns those records into embeddings, scores, labels, and summaries. The two meet wherever a warehouse row needs to be enriched by a model and the result needs somewhere durable to live. Most teams stitch that meeting together with export scripts and a queue, then spend their time keeping the glue alive.

The payoff is that model output stops living in a separate place from the data it describes. Once results sit in MotherDuck, they join against billing, product, and usage tables already there, so you can report on quality, cost, and coverage without moving anything by hand.

Common use cases

  • 01 Land Fine-tuning jobs with their status, base model, and result Files in a warehouse to power MLOps dashboards without per-viewer API calls.
  • 02 Poll Batch jobs into an operational database and fire the next pipeline step when a job's status turns to completed.
  • 03 Sync modeled MotherDuck tables outward to operational tools for activation
  • 04 Share curated, synced datasets with other teams through read-only database shares

Common sync patterns

History that outlives a run

A continuously synced copy in MotherDuck preserves every generated result, so outputs stay auditable even as they are overwritten or expire inside Azure OpenAI.

Feed live warehouse records to Azure OpenAI

Rows added or changed in MotherDuck flow into Azure OpenAI within seconds, so embeddings, classifications, and enrichments are computed on current data rather than a nightly extract.

Model output back in the warehouse

Scores, labels, embeddings, or summaries produced in Azure OpenAI land in MotherDuck as columns or tables, queryable and joinable with the rest of the business data.

What you can sync between Azure OpenAI and MotherDuck

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 OpenAI objects MotherDuck objects How this pairing syncs
Files Uploaded training, validation, and batch-input files plus generated output files; listed and read by ID, not written back in sync. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Files is specific to Azure OpenAI and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side.
Batch jobs Asynchronous bulk-inference jobs; status and output-file IDs are polled to completion to drive downstream pipeline triggers. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Batch jobs is specific to Azure OpenAI and Databases to MotherDuck — each maps to any object or custom field on the other side.
Usage and quota Per-deployment TPM/RPM consumption and remaining quota, read from usage endpoints and Azure Monitor for cost and throttling reporting. Schemas Namespaces within a database used to organize synced tables. Usage and quota is specific to Azure OpenAI and Schemas to MotherDuck — each maps to any object or custom field on the other side.
Assistants Persistent assistants (preview) with instructions, tools, and linked files; read as configuration inventory, not authored via sync. Tables The main landing target for synced records and source for analysis. Assistants is specific to Azure OpenAI and Tables to MotherDuck — each maps to any object or custom field on the other side.
Vector stores File collections (preview) backing file-search retrieval; read as metadata such as name, file counts, and status. Views Modeled projections used as outbound sync sources. Vector stores is specific to Azure OpenAI and Views to MotherDuck — each maps to any object or custom field on the other side.
Deployments Named model deployments (model, version, SKU, assigned TPM capacity) read as a control-plane inventory via Azure Resource Manager; read-only in sync. Database Shares Read-only copies of a database shared with other users or teams. Deployments is specific to Azure OpenAI and Database Shares to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between Azure OpenAI and MotherDuck

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 OpenAI MotherDuck Interval-based propagation

DetectionStacksync polls Azure OpenAI for changes on an incremental schedule, reading only records changed since the previous pass. Polling: list endpoints plus GET on job IDs for status.

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

MotherDuck Azure OpenAI Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

DeliveryAzure OpenAI does not accept inbound record writes, so this direction carries requests rather than records: Azure OpenAI's output flows back as field updates on the originating MotherDuck records.

Rate-limit considerations

  • Azure OpenAI: Per-deployment TPM and RPM limits (about 6 RPM per 1000 TPM), scoped by region and subscription; control-plane ARM calls throttle separately.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Azure OpenAI ⇄ MotherDuck

Connect Azure OpenAI and MotherDuck for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure OpenAI–MotherDuck connection.

Real-time

Real-time sync

Changes in Azure OpenAI or MotherDuck instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure OpenAI or MotherDuck 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 OpenAI or MotherDuck record.

Observability

Monitoring

Track your Azure OpenAI ⇄ MotherDuck sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure OpenAI and MotherDuck.

How the Azure OpenAI and MotherDuck connectors work

Azure OpenAI

Integration surface
REST data-plane (inference + authoring) and Azure Resource Manager control-plane
Authentication
API key in the api-key header, or a Microsoft Entra ID bearer token / managed identity
Change detection
Polling: list endpoints plus GET on job IDs for status; no webhooks or change feed. Fine-tuning and batch jobs expose queued/running/succeeded states.
Capabilities
read
Rate limits
Per-deployment TPM and RPM limits (about 6 RPM per 1000 TPM), scoped by region and subscription; control-plane ARM calls throttle separately.

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

How to connect Azure OpenAI to MotherDuck — 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 OpenAI and MotherDuck 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 OpenAI connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure OpenAI and MotherDuck 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 OpenAI ⇄ MotherDuck
    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 OpenAI MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure OpenAI and MotherDuck 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 422 integrations available for Azure OpenAI and MotherDuck.

Popular · 7 of 422
All Azure OpenAI integrations All MotherDuck integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own