Real-time
Two-way sync
Changes in Active Directory or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Data warehouse
Active Directory to Starburst Enterprise integration — real-time, two-way sync
Keep Active Directory and Starburst Enterprise 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 Starburst Enterprise
Land the users, groups, and access events from Active Directory in Starburst Enterprise 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; Starburst Enterprise 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 Starburst Enterprise. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.
Stacksync syncs Service principals & applications, Organizational units, Organizational contacts, Users from Active Directory into tables in Starburst Enterprise in real time, and the connection works in both directions: values computed in Starburst Enterprise, 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 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
- 02 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Directory data in the warehouse, minus the pipeline
Users, groups, and roles from Active Directory arrive in Starburst Enterprise 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 Starburst Enterprise, 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 Starburst Enterprise to surface who holds access they no longer need.
What you can sync between Active Directory and Starburst Enterprise
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 | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Materialized views Precomputed results that make repeated sync reads cheaper. | Service principals & applications is specific to Active Directory and Materialized views to Starburst Enterprise — 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. | Columns Typed per the Trino type system, mapped from each source's native types. | Organizational units is specific to Active Directory and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Organizational contacts is specific to Active Directory and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Users is specific to Active Directory and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Groups is specific to Active Directory and Tables to Starburst Enterprise — 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 Engine-level SQL views used to shape federated data before syncing it out. | Group memberships is specific to Active Directory and Views to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Starburst Enterprise
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 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise Active Directory Interval-based propagation
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based 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.
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Active Directory ⇄ Starburst Enterprise
Connect Active Directory and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Starburst Enterprise 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 Starburst Enterprise record.
Observability
Monitoring
Track your Active Directory ⇄ Starburst Enterprise 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 Starburst Enterprise.
How the Active Directory and Starburst Enterprise 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.
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect Active Directory to Starburst Enterprise — 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 Starburst Enterprise 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
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Starburst Enterprise 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 ⇄ Starburst EnterpriseCustomers 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 Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Active Directory's Service principals & applications and Organizational units), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Starburst Enterprise 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 Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Starburst Enterprise integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Starburst Enterprise. 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 Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Starburst Enterprise side: Tables, Views, Materialized views, Columns, plus custom fields where Starburst Enterprise exposes them. On the Active Directory side: Service principals & applications, Organizational units, Organizational contacts, Users. Stacksync auto-detects both schemas and converts types between the two systems.
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 434 integrations available for Active Directory and Starburst Enterprise.
Popular · 8 of 434
-
Active Directory ⇄ IBM Netezza -
Active Directory ⇄ Materialize -
Active Directory ⇄ Rockset -
Active Directory ⇄ StarRocks -
Starburst Enterprise ⇄ Onelogin -
Starburst Enterprise ⇄ Auth0 -
Starburst Enterprise ⇄ Jumpcloud - Starburst Enterprise ⇄ Azure Active Directory
No integrations match .
