Two-way sync
Changes in Active Directory or Rockset instantly reflect in both systems. No stale data, no manual imports.
Keep Active Directory and Rockset in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Active Directory is the record of who exists and what they can reach; Rockset 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 Rockset. 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 Rockset in real time, and the connection works in both directions: values computed in Rockset, 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.
Risk scores, anomaly flags, or access-review outcomes computed in Rockset write back to attributes on the matching user in Active Directory, where the identity team can act on them.
Users, groups, and roles from Active Directory arrive in Rockset as queryable tables, current within seconds instead of a nightly directory export.
Sign-in and access events from Active Directory land in Rockset, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.
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 | Rockset objects | How this pairing syncs | |
|---|---|---|---|
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | Devices is specific to Active Directory and Query Lambdas to Rockset — 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. | Aliases Stable names that point at collections, used to swap datasets without changing queries. | Directory roles is specific to Active Directory and Aliases to Rockset — 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. | Integrations Managed source connections (databases, streams, object storage) feeding collections. | Service principals & applications is specific to Active Directory and Integrations to Rockset — 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. | Virtual Instances Isolated compute units that separate ingest from query workloads. | Organizational units is specific to Active Directory and Virtual Instances to Rockset — 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. | Collections Schemaless document containers that ingested and synced records land in. | Organizational contacts is specific to Active Directory and Collections to Rockset — 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. | Documents JSON records addressable by _id, written via the Write API in sync pipelines. | Users is specific to Active Directory and Documents to Rockset — each maps to any object or custom field on the other side. |
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.
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 Rockset as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Rockset connection.
Changes in Active Directory or Rockset instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Active Directory or Rockset data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Active Directory or Rockset record.
Track your Active Directory ⇄ Rockset sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Active Directory and Rockset.
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.
Authenticate Active Directory and Rockset with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Active Directory and Rockset 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Rockset: authenticate both systems, choose the objects to sync (such as Active Directory's Devices and Directory roles), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Active Directory and Rockset: Risk and review results back on the account; Directory data in the warehouse, minus the pipeline; Access and sign-in analytics. Risk scores, anomaly flags, or access-review outcomes computed in Rockset write back to attributes on the matching user in Active Directory, where the identity team can act on them.
Active Directory: 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. Rockset: REST API (SQL over HTTP, plus a document Write API). Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
Rockset: Its Converged Index stores every field in row, column, and inverted (search) indexes at once, which is why ad-hoc filters and aggregations stay fast without manual index tuning. Active Directory: On-premises AD DS has no Graph API and syncs over LDAP/LDAPS using the DirSync control, which needs the DS-Replication-Get-Changes right on the partition. Stacksync's field mapping accounts for these differences between Active Directory and Rockset without custom code.
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 Rockset 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 Rockset connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Rockset integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 500 integrations available for Active Directory and Rockset.