Real-time
Two-way sync
Changes in Active Directory or MariaDB instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to MariaDB integration — real-time, two-way sync
Keep Active Directory and MariaDB 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 MariaDB
Close the gap between your application data and your directory: MariaDB 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. MariaDB 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 Databases (Schemas), Tables, Views, Columns in MariaDB 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 Two-way sync between a MariaDB application database and a CRM so both systems hold the same customer records
- 02 Replicate ERP or billing master data into MariaDB databases that power customer-facing applications
- 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
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 MariaDB, 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 MariaDB
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 | MariaDB objects | How this pairing syncs | |
|---|---|---|---|
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Stored Procedures Server-side logic that can post-process synced rows. | Organizational contacts is specific to Active Directory and Stored Procedures to MariaDB — 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. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Users is specific to Active Directory and Databases (Schemas) to MariaDB — 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 to records in connected systems. | Groups is specific to Active Directory and Tables to MariaDB — 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 as outbound sync sources. | Group memberships is specific to Active Directory and Views to MariaDB — 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. | Columns Field-level mapping targets with engine-typed values. | Devices is specific to Active Directory and Columns to MariaDB — 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. | Primary and Unique Keys Match keys for idempotent upserts. | Directory roles is specific to Active Directory and Primary and Unique Keys to MariaDB — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and MariaDB
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 MariaDB 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 MariaDB as a row-level write, with types converted between the two schemas.
MariaDB Active Directory Sub-second propagation
DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.
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.
- MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Active Directory ⇄ MariaDB
Connect Active Directory and MariaDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–MariaDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or MariaDB 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 MariaDB record.
Observability
Monitoring
Track your Active Directory ⇄ MariaDB 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 MariaDB.
How the Active Directory and MariaDB 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.
MariaDB
- Integration surface
- SQL wire protocol (MySQL-compatible client/server protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
How it works
How to connect Active Directory to MariaDB — 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 MariaDB 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
MariaDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and MariaDB 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 ⇄ MariaDBCustomers 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 MariaDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and MariaDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and MariaDB: authenticate both systems, choose the objects to sync (such as Active Directory's Organizational contacts and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
MariaDB: System-versioned (temporal) tables can retain full row history natively, which helps audit what a sync changed and when. Active Directory: For hybrid users mastered on-premises, some attributes (e.g. userPrincipalName) cannot be changed in Entra ID because the object is sourced from AD DS. Stacksync's field mapping accounts for these differences between Active Directory and MariaDB 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 MariaDB 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 MariaDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–MariaDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and MariaDB. 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 MariaDB: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 441 integrations available for Active Directory and MariaDB.
Popular · 8 of 441
-
Active Directory ⇄ AWS Aurora MySQL - Active Directory ⇄ AWS Aurora PostgreSQL
-
Active Directory ⇄ MongoDB -
Active Directory ⇄ CockroachDB -
MariaDB ⇄ Onelogin -
MariaDB ⇄ Auth0 -
MariaDB ⇄ Jumpcloud - MariaDB ⇄ Azure Active Directory
No integrations match .
