Real-time
Two-way sync
Changes in Active Directory or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Data warehouse
Active Directory to MotherDuck integration — real-time, two-way sync
Keep Active Directory 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 Active Directory and MotherDuck
Land the users, groups, and access events from Active Directory in MotherDuck continuously for security analytics, and write computed results back — without building or maintaining a pipeline.
Active Directory is the record of who exists and what they can reach; MotherDuck is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Active Directory governs are what security, compliance, and analytics teams want to query in MotherDuck. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.
Stacksync syncs Directory roles, Service principals & applications, Organizational units, Organizational contacts from Active Directory into tables in MotherDuck in real time, and the connection works in both directions: values computed in MotherDuck, such as risk scores or access-review decisions, can be written back to attributes in Active Directory where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.
Common use cases
- 01 Share curated, synced datasets with other teams through read-only database shares
- 02 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
- 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
- 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
Common sync patterns
Directory data in the warehouse, minus the pipeline
Users, groups, and roles from Active Directory arrive in MotherDuck as queryable tables, current within seconds instead of a nightly directory export.
Access and sign-in analytics
Sign-in and access events from Active Directory land in MotherDuck, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.
Access governance on joined data
Join Active Directory's users and group memberships with HR, product, and usage data already in MotherDuck to surface who holds access they no longer need.
What you can sync between Active Directory 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.
| Active Directory objects | MotherDuck objects | How this pairing syncs | |
|---|---|---|---|
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Tables The main landing target for synced records and source for analysis. | Groups is specific to Active Directory and Tables to MotherDuck — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Views Modeled projections used as outbound sync sources. | Group memberships is specific to Active Directory and Views to MotherDuck — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Database Shares Read-only copies of a database shared with other users or teams. | Devices is specific to Active Directory and Database Shares to MotherDuck — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Directory roles is specific to Active Directory and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Service principals & applications is specific to Active Directory and Databases to MotherDuck — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Schemas Namespaces within a database used to organize synced tables. | Organizational units is specific to Active Directory and Schemas to MotherDuck — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory 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.
Active Directory MotherDuck Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.
MotherDuck Active Directory Interval-based propagation
DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Active Directory ⇄ MotherDuck
Connect Active Directory and MotherDuck for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–MotherDuck connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory 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 Active Directory or MotherDuck record.
Observability
Monitoring
Track your Active Directory ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and MotherDuck.
How the Active Directory and MotherDuck connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
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
How it works
How to connect Active Directory 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.
- 01
Connect your apps
Authenticate Active Directory 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.
Active Directory
connected
MotherDuck
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory 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.
objects · Active Directory ⇄ MotherDuckCustomers 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.
Active Directory MotherDuckCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and MotherDuck integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and MotherDuck: authenticate both systems, choose the objects to sync (such as Active Directory's Groups and Group memberships), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
MotherDuck: Hybrid execution can split a query between the local DuckDB process and cloud compute. Active Directory: On-premises AD DS has no Graph API and syncs over LDAP/LDAPS using the DirSync control, which needs the DS-Replication-Get-Changes right on the partition. Stacksync's field mapping accounts for these differences between Active Directory and MotherDuck without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Active Directory and MotherDuck records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and MotherDuck connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–MotherDuck integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and MotherDuck. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On MotherDuck: Polling; no log-based CDC or webhook surface is exposed. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 447 integrations available for Active Directory and MotherDuck.
Popular · 8 of 447
-
Active Directory ⇄ ClickHouse -
Active Directory ⇄ Cloudera Data Platform -
Active Directory ⇄ Dremio -
Active Directory ⇄ Exasol -
MotherDuck ⇄ Okta -
MotherDuck ⇄ Onelogin -
MotherDuck ⇄ Auth0 -
MotherDuck ⇄ Jumpcloud
No integrations match .
