Skip to content
Security and identity ⇄ Data warehouse

Active Directory to Exasol integration — real-time, two-way sync

Keep Active Directory and Exasol 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 Exasol

Land the users, groups, and access events from Active Directory in Exasol 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; Exasol 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 Exasol. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Organizational contacts, Users, Groups, Group memberships from Active Directory into tables in Exasol in real time, and the connection works in both directions: values computed in Exasol, 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 Consolidate data from multiple operational databases into Exasol as the central analytics layer.
  • 02 Keep dimension tables such as customers and products aligned with the systems of record.
  • 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
  • 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.

Common sync patterns

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Exasol write back to attributes on the matching user in Active Directory, where the identity team can act on them.

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Active Directory arrive in Exasol 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 Exasol, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

What you can sync between Active Directory and Exasol

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 Exasol objects How this pairing syncs
Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. Schemas Namespaces that group the tables a sync reads from or writes into. Groups is specific to Active Directory and Schemas to Exasol — 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. Tables Primary sync target; columnar relational tables written with standard SQL. Group memberships is specific to Active Directory and Tables to Exasol — 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. Views Read-only query surfaces often used as curated sources for reverse ETL. Devices is specific to Active Directory and Views to Exasol — 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. Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Directory roles is specific to Active Directory and Virtual schemas to Exasol — 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. UDF scripts In-database functions that can transform synced data after load. Service principals & applications is specific to Active Directory and UDF scripts to Exasol — 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. Users and roles Grant read/write access for the dedicated integration account. Organizational units is specific to Active Directory and Users and roles to Exasol — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Exasol

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 Exasol 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 Exasol as a row-level write, with types converted between the two schemas.

Exasol Active Directory Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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.
  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
What ships with Active Directory ⇄ Exasol

Connect Active Directory and Exasol for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Exasol connection.

Real-time

Two-way sync

Changes in Active Directory or Exasol instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Exasol 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 Exasol record.

Observability

Monitoring

Track your Active Directory ⇄ Exasol 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 Exasol.

How the Active Directory and Exasol 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.

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits
How it works

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

    Choose tables

    Pick the Active Directory and Exasol 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 · Active Directory ⇄ Exasol
    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
    Active Directory Exasol
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and Exasol 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 430 integrations available for Active Directory and Exasol.

Popular · 8 of 430
All Active Directory integrations All Exasol 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