Real-time
Two-way sync
Changes in Active Directory or MarkLogic instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to MarkLogic integration — real-time, two-way sync
Keep Active Directory and MarkLogic 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 MarkLogic
Close the gap between your application data and your directory: MarkLogic 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. MarkLogic 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 Collections, Semantic Triples, TDE Views, Document Metadata & Properties in MarkLogic with Groups, Group memberships, Devices, Directory roles 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 Feed harmonized entities into search and analytics applications as documents change.
- 02 Sync curated master data from a MarkLogic data hub into operational CRMs and ERPs.
- 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
Provision accounts from the source of truth
When a person is added to the employee, member, or customer table in MarkLogic, Stacksync creates the matching user in Active Directory with the right attributes, so access starts from live data instead of a manual ticket.
Deprovision the moment the record changes
When someone is marked inactive or removed in MarkLogic, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
Read users and groups as ordinary tables
Users, groups, and their memberships from Active Directory land in MarkLogic as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
What you can sync between Active Directory and MarkLogic
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 | MarkLogic objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Users & Roles Security principals that govern what an integration credential can read or write. | Users is specific to Active Directory and Users & Roles to MarkLogic — 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. | Documents JSON and XML documents, the primary records read from and written to the database. | Groups is specific to Active Directory and Documents to MarkLogic — 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. | Collections Named groupings used to scope which documents a sync reads or updates. | Group memberships is specific to Active Directory and Collections to MarkLogic — 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. | Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. | Devices is specific to Active Directory and Semantic Triples to MarkLogic — 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. | TDE Views Relational projections of documents that let syncs read document data as SQL rows. | Directory roles is specific to Active Directory and TDE Views to MarkLogic — 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. | Document Metadata & Properties Permissions, quality, and property fragments carried with each document. | Service principals & applications is specific to Active Directory and Document Metadata & Properties to MarkLogic — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and MarkLogic
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 MarkLogic 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 MarkLogic as a row-level write, with types converted between the two schemas.
MarkLogic Active Directory Interval-based propagation
DetectionStacksync polls MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.
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.
What ships with Active Directory ⇄ MarkLogic
Connect Active Directory and MarkLogic for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–MarkLogic connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or MarkLogic 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 MarkLogic record.
Observability
Monitoring
Track your Active Directory ⇄ MarkLogic 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 MarkLogic.
How the Active Directory and MarkLogic 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.
MarkLogic
- Integration surface
- REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries
- Authentication
- Username/password (digest or basic), with certificate-based options
- Change detection
- No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup
- Capabilities
- read · write
How it works
How to connect Active Directory to MarkLogic — 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 Active Directory and MarkLogic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
MarkLogic
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and MarkLogic 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 · Active Directory ⇄ MarkLogicCustomers 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.
Active Directory MarkLogicCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and MarkLogic integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and MarkLogic: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and MarkLogic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–MarkLogic integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and MarkLogic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: 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. On MarkLogic: No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MarkLogic side: Collections, Semantic Triples, TDE Views, Document Metadata & Properties, plus custom fields where MarkLogic exposes them. On the Active Directory side: Groups, Group memberships, Devices, Directory roles. 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.
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 436 integrations available for Active Directory and MarkLogic.
Popular · 8 of 436
-
Active Directory ⇄ AWS Aurora MySQL - Active Directory ⇄ AWS Aurora PostgreSQL
-
Active Directory ⇄ MongoDB -
Active Directory ⇄ CockroachDB -
MarkLogic ⇄ Onelogin -
MarkLogic ⇄ Auth0 -
MarkLogic ⇄ Jumpcloud - MarkLogic ⇄ Azure Active Directory
No integrations match .
