Skip to content
Security and identity ⇄ Data warehouse

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

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

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

Stacksync syncs Devices, Directory roles, Service principals & applications, Organizational units from Active Directory into tables in Snowflake in real time, and the connection works in both directions: values computed in Snowflake, 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 Keep a customer 360 table aligned with its source systems in both directions instead of one-way reverse ETL
  • 02 Push product usage aggregates from Snowflake into sales and success tools for account prioritization
  • 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

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Snowflake 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 Snowflake 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 Snowflake, 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 Snowflake

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 Snowflake objects How this pairing syncs
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Tasks Scheduled SQL used to transform synced data after it lands. Group memberships is specific to Active Directory and Tasks to Snowflake — 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. VARIANT Columns Semi-structured JSON payloads stored alongside relational columns. Devices is specific to Active Directory and VARIANT Columns to Snowflake — 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 Warehouses The compute a sync's queries run on, sized independently of storage. Directory roles is specific to Active Directory and Virtual Warehouses to Snowflake — 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 Top-level containers that scope which data a sync can touch. Service principals & applications is specific to Active Directory and Databases to Snowflake — 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 Snowflake — 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. Tables The main landing and activation target for synced records. Organizational contacts is specific to Active Directory and Tables to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Snowflake

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

Snowflake Active Directory Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

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.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Active Directory ⇄ Snowflake

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

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

    Choose tables

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

Active Directory and Snowflake 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 545 integrations available for Active Directory and Snowflake.

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