Real-time
Two-way sync
Changes in Azure Active Directory or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Data warehouse
Azure Active Directory to Starburst Enterprise integration — real-time, two-way sync
Keep Azure 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
Live sync
stacksync.com - <1s
- latency
- 2-way
- sync
- 100M+
- records
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 Active Directory and Starburst Enterprise
Land the users, groups, and access events from Azure Active Directory in Starburst Enterprise continuously for security analytics, and write computed results back — without building or maintaining a pipeline.
Azure 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 Azure 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 Applications, Service principals, Directory roles, Devices from Azure 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 Azure 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 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
- 02 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
- 03 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
- 04 Mirror Applications and Service principals into a database or CMDB to track app ownership and credential expiry.
Common sync patterns
Access and sign-in analytics
Sign-in and access events from Azure 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 Azure 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.
Queryable history for audit and compliance
A continuously synced copy in Starburst Enterprise gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.
What you can sync between Azure 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.
| Azure Active Directory objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Users is specific to Azure Active Directory and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Groups is specific to Azure Active Directory and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Views Engine-level SQL views used to shape federated data before syncing it out. | Group memberships is specific to Azure Active Directory and Views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Materialized views Precomputed results that make repeated sync reads cheaper. | Applications is specific to Azure Active Directory and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | Columns Typed per the Trino type system, mapped from each source's native types. | Service principals is specific to Azure Active Directory and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Directory roles is specific to Azure Active Directory and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory Starburst Enterprise Sub-second propagation
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise Azure 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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Azure Active Directory ⇄ Starburst Enterprise
Connect Azure Active Directory and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or Starburst Enterprise record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and Starburst Enterprise.
How the Azure Active Directory and Starburst Enterprise connectors work
Azure Active Directory
- Integration surface
- Microsoft Graph REST API (v1.0)
- Authentication
- OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
- Change detection
- Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
- Capabilities
- read · write · webhooks
- Rate limits
- Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header
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 Azure 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 Azure 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.
Azure Active Directory
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Azure Active Directory: Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push. 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 Azure Active Directory side: Applications, Service principals, Directory roles, Devices. 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.
-
Common patterns for Azure Active Directory and Starburst Enterprise: Access and sign-in analytics; Access governance on joined data; Queryable history for audit and compliance. Sign-in and access events from Azure 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.
-
Azure Active Directory: Microsoft Graph REST API (v1.0). Authentication: OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
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 Azure Active Directory and Starburst Enterprise.
Popular · 8 of 434
-
Azure Active Directory ⇄ ClickHouse -
Azure Active Directory ⇄ Cloudera Data Platform -
Azure Active Directory ⇄ Dremio -
Azure Active Directory ⇄ Exasol -
Starburst Enterprise ⇄ Onelogin -
Starburst Enterprise ⇄ Auth0 -
Starburst Enterprise ⇄ Jumpcloud - Starburst Enterprise ⇄ Active Directory
No integrations match .
