Real-time
Two-way sync
Changes in Azure Active Directory or MySQL instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Azure Active Directory to MySQL integration — real-time, two-way sync
Keep Azure 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 Azure Active Directory and MySQL
Close the gap between your application data and your directory: MySQL and Azure Active Directory share users, groups, and access in real time, in both directions.
Azure 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 Views, Columns, Primary and Unique Keys, JSON Columns in MySQL with Devices, Users, Groups, Group memberships in Azure 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 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts
- 02 Feed a warehouse from MySQL continuously using binlog-based capture instead of nightly dumps
- 03 Sync manager, department, and jobTitle from an HRIS back onto Entra ID User attributes to keep dynamic groups and Conditional Access accurate.
- 04 Replicate Groups and their Members into a Postgres warehouse for access reviews and entitlement reporting.
Common sync patterns
Deprovision the moment the record changes
When someone is marked inactive or removed in MySQL, the matching account in Azure 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 Azure 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.
What you can sync between Azure 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.
| Azure Active Directory objects | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Devices is specific to Azure Active Directory and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side. | |
| Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. | Tables The primary sync target; rows map to records in connected systems. | Users is specific to Azure Active Directory and Tables to MySQL — each maps to any object or custom field on the other side. | |
| Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Views Read-side projections used as outbound sync sources. | Groups is specific to Azure Active Directory and Views to MySQL — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Columns Field-level mapping targets with engine-typed values. | Group memberships is specific to Azure Active Directory and Columns to MySQL — each maps to any object or custom field on the other side. | |
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Applications is specific to Azure Active Directory and Primary and Unique Keys to MySQL — each maps to any object or custom field on the other side. | |
| Service principals /servicePrincipals (enterprise apps) plus appRoleAssignments; read for app inventory and access-posture reporting. | JSON Columns Validated semi-structured payloads for nested SaaS data. | Service principals is specific to Azure Active Directory and JSON Columns to MySQL — each maps to any object or custom field on the other side. |
How changes propagate between Azure 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.
Azure Active Directory MySQL Sub-second propagation
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.
MySQL Azure 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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Azure Active Directory: Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header.
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Azure Active Directory ⇄ MySQL
Connect Azure Active Directory and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure 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 Azure Active Directory or MySQL record.
Observability
Monitoring
Track your Azure 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 Azure Active Directory and MySQL.
How the Azure Active Directory and MySQL connectors work
Azure Active Directory
- Integration surface
- Microsoft Graph REST API (v1.0)
- Authentication
- OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent
- Change detection
- Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification webhook subscriptions for near-real-time push
- Capabilities
- read · write · webhooks
- Rate limits
- Resource-unit throttling: roughly 8,000 ResourceUnits per 10 seconds per app for reads on tenants over 500 users, writes near 3,000 requests per 2.5 minutes; 429 responses include a Retry-After header
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 Azure 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 Azure 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.
Azure Active Directory
connected
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure 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 · Azure 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.
Azure Active Directory MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Active Directory and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Active Directory and MySQL: authenticate both systems, choose the objects to sync (such as Azure Active Directory's Devices and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Azure Active Directory: Microsoft Graph REST API (v1.0). Authentication: OAuth 2.0 via the Microsoft identity platform using an Entra ID app registration; app-only (client credentials) or delegated flows, with directory scopes such as User.ReadWrite.All and Group.ReadWrite.All requiring tenant admin consent. 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: Composite primary keys are not supported — primary key must be a single column. Azure Active Directory: Hybrid identities synchronized from on-premises Active Directory via Entra Connect are mastered on-prem; many of their attributes are read-only in Entra ID and must be edited in AD DS. Stacksync's field mapping accounts for these differences between Azure Active Directory and MySQL 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 Azure Active Directory and MySQL records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Active Directory and MySQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Active Directory–MySQL integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Active Directory and MySQL. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Azure Active Directory and MySQL.
Popular · 8 of 544
-
Azure Active Directory ⇄ Couchbase -
Azure Active Directory ⇄ DuckDB -
Azure Active Directory ⇄ Elasticsearch -
Azure Active Directory ⇄ Google Cloud Spanner -
MySQL ⇄ Okta -
MySQL ⇄ Onelogin -
MySQL ⇄ Auth0 -
MySQL ⇄ Jumpcloud
No integrations match .
