Skip to content
Security and identity ⇄ Database

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

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

Close the gap between your application data and your directory: PostgreSQL and Active Directory share users, groups, and access in real time, in both directions.

Active Directory is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. PostgreSQL holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.

Stacksync syncs Primary and Unique Keys, JSONB Columns, Sequences, Custom Types and Enums in PostgreSQL with Directory roles, Service principals & applications, Organizational units, Organizational contacts in Active Directory field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.

Common use cases

  • 01 Consolidate data from several microservice databases into one operational Postgres store
  • 02 Feed reporting and BI from a continuously synced Postgres replica instead of scheduled ETL scripts
  • 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

Keep group and role membership aligned

A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.

One profile, kept current

A name, department, email, or manager corrected in either system updates the other, so the profile the directory shows and the data the application reads stop drifting apart.

Provision accounts from the source of truth

When a person is added to the employee, member, or customer table in PostgreSQL, Stacksync creates the matching user in Active Directory with the right attributes, so access starts from live data instead of a manual ticket.

What you can sync between Active Directory and PostgreSQL

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 PostgreSQL objects How this pairing syncs
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. Service principals & applications is specific to Active Directory and Primary and Unique Keys to PostgreSQL — 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. JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. Organizational units is specific to Active Directory and JSONB Columns to PostgreSQL — 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. Sequences Generate surrogate keys for rows created by inbound syncs. Organizational contacts is specific to Active Directory and Sequences to PostgreSQL — 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. Custom Types and Enums Constrain synced values to a fixed set, mirroring picklist fields. Users is specific to Active Directory and Custom Types and Enums to PostgreSQL — 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 The primary sync target; rows map one-to-one to records in connected SaaS systems. Groups is specific to Active Directory and Tables to PostgreSQL — 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 Read-side projections used to expose joined or filtered data to a sync. Group memberships is specific to Active Directory and Views to PostgreSQL — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and PostgreSQL

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

PostgreSQL Active Directory Sub-second propagation

DetectionChanges in PostgreSQL are captured at the source via change data capture — no polling loop against its API. Logical replication (wal_level = logical) for change data capture via the "Postgres" connector.

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.
  • PostgreSQL: No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput.
What ships with Active Directory ⇄ PostgreSQL

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

PostgreSQL

Integration surface
SQL wire protocol (PostgreSQL frontend/backend protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
Change detection
Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput
PostgreSQL setup guide
How it works

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

    Choose tables

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

Active Directory and PostgreSQL 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 543 integrations available for Active Directory and PostgreSQL.

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