Real-time
Two-way sync
Changes in Active Directory or MySQL instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to MySQL integration — real-time, two-way sync
Keep Active Directory and MySQL 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 MySQL
Close the gap between your application data and your directory: MySQL 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. MySQL 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 Stored Procedures, Triggers, Databases (Schemas), Tables in MySQL with Users, Groups, Group memberships, Devices 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 a warehouse from MySQL continuously using binlog-based capture instead of nightly dumps
- 02 Two-way sync between a MySQL application database and a CRM so operational records and sales records stay identical
- 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
Read users and groups as ordinary tables
Users, groups, and their memberships from Active Directory land in MySQL as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
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.
What you can sync between Active Directory and MySQL
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 | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Views Read-side projections used as outbound sync sources. | Directory roles is specific to Active Directory and Views to MySQL — 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. | Columns Field-level mapping targets with engine-typed values. | Service principals & applications is specific to Active Directory and Columns to MySQL — 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. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Organizational units is specific to Active Directory and Primary and Unique Keys to MySQL — 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. | JSON Columns Validated semi-structured payloads for nested SaaS data. | Organizational contacts is specific to Active Directory and JSON Columns to MySQL — 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. | Stored Procedures Server-side logic that can post-process synced rows. | Users is specific to Active Directory and Stored Procedures to MySQL — 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. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | Groups is specific to Active Directory and Triggers to MySQL — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and MySQL
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 MySQL 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 MySQL as a row-level write, with types converted between the two schemas.
MySQL Active Directory Sub-second propagation
DetectionChanges in MySQL 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 (requires log_bin_trust_function_creators=ON when.
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.
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Active Directory ⇄ MySQL
Connect Active Directory and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or MySQL 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 MySQL record.
Observability
Monitoring
Track your Active Directory ⇄ MySQL 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 MySQL.
How the Active Directory and MySQL 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.
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- 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 MySQL — 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 MySQL 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
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and MySQL 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 ⇄ MySQLCustomers 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 MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and MySQL: authenticate both systems, choose the objects to sync (such as Active Directory's Directory roles and Service principals & applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the MySQL side: Stored Procedures, Triggers, Databases (Schemas), Tables, plus custom fields where MySQL exposes them. On the Active Directory side: Users, Groups, Group memberships, Devices. 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.
-
Common patterns for Active Directory and MySQL: Read users and groups as ordinary tables; Keep group and role membership aligned; One profile, kept current. Users, groups, and their memberships from Active Directory land in MySQL as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
-
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. MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Stacksync manages authentication, retries, and rate limits on both sides.
-
MySQL: Primary keys must be auto-generated (e.g. AUTO_INCREMENT). 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 MySQL without custom code.
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 544 integrations available for Active Directory and MySQL.
Popular · 8 of 544
-
Active Directory ⇄ Azure Cosmos DB -
Active Directory ⇄ Azure SQL Database -
Active Directory ⇄ Citus -
Active Directory ⇄ Couchbase -
MySQL ⇄ Jumpcloud - MySQL ⇄ Azure Active Directory
-
MySQL ⇄ Okta -
MySQL ⇄ Onelogin
No integrations match .
