Real-time
Two-way sync
Changes in Microsoft Graph or MySQL instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Database
Microsoft Graph to MySQL integration — real-time, two-way sync
Keep Microsoft Graph 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 Microsoft Graph and MySQL
Keep MySQL and Microsoft Graph in step: the rows in your database and the Calendar events, Contacts, Drive items (OneDrive & SharePoint), Teams messages and chats your engineering tools track stay consistent in real time, in both directions.
MySQL is where your application's durable data lives; Microsoft Graph is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.
Stacksync syncs JSON Columns, Stored Procedures, Triggers, Databases (Schemas) in MySQL with Calendar events, Contacts, Drive items (OneDrive & SharePoint), Teams messages and chats in Microsoft Graph field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.
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 Sync Outlook Calendar events and Contacts two-way with a CRM so reps' meetings and the people they meet stay aligned across both systems.
- 04 Send Outlook mail through the sendMail action when a database or CRM record changes, then read replies back onto the same record.
Common sync patterns
Land tool activity as queryable rows
Records and events from Microsoft Graph arrive in MySQL as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.
One integration pattern instead of per-tool API code
Read and write the synced tables in MySQL and Stacksync keeps Microsoft Graph current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.
React to changes on either side in near real time
Updates in Microsoft Graph arrive as row changes in MySQL, and writes to MySQL propagate to Microsoft Graph within seconds, so triggers, jobs, and alerts fire without polling.
What you can sync between Microsoft Graph 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.
| Microsoft Graph objects | MySQL objects | How this pairing syncs | |
|---|---|---|---|
| Users Entra ID user accounts read and written via /users; create, update profile attributes, and enable or disable accounts with User.ReadWrite.All. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | Users is specific to Microsoft Graph and Primary and Unique Keys to MySQL — each maps to any object or custom field on the other side. | |
| Groups and memberships Microsoft 365 and security groups via /groups; read and write name, owners, and add/remove members, with membership deltas surfaced by delta query. | JSON Columns Validated semi-structured payloads for nested SaaS data. | Groups and memberships is specific to Microsoft Graph and JSON Columns to MySQL — each maps to any object or custom field on the other side. | |
| Mail messages (Outlook) Messages via /users/{id}/messages; read and create drafts, update, and send with the sendMail action, so this surface is fully read-write. | Stored Procedures Server-side logic that can post-process synced rows. | Mail messages (Outlook) is specific to Microsoft Graph and Stored Procedures to MySQL — each maps to any object or custom field on the other side. | |
| Calendar events Outlook events via /users/{id}/events; read and write meetings, attendees, and recurrence, and accept or decline invitations. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | Calendar events is specific to Microsoft Graph and Triggers to MySQL — each maps to any object or custom field on the other side. | |
| Contacts Personal Outlook contacts via /users/{id}/contacts; full create, read, update, delete, synced two-way with CRM person records. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Contacts is specific to Microsoft Graph and Databases (Schemas) to MySQL — each maps to any object or custom field on the other side. | |
| Drive items (OneDrive & SharePoint) Files and folders via /drives and /me/drive; read and write items, upload and download content, and read per-item metadata. | Tables The primary sync target; rows map to records in connected systems. | Drive items (OneDrive & SharePoint) is specific to Microsoft Graph and Tables to MySQL — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Graph 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.
Microsoft Graph MySQL Sub-second propagation
DetectionMicrosoft Graph notifies Stacksync of record changes through webhook events. Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and.
DeliveryEach detected change is applied to MySQL as a row-level write, with types converted between the two schemas.
MySQL Microsoft Graph 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 Microsoft Graph through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Microsoft Graph: Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Microsoft Graph ⇄ MySQL
Connect Microsoft Graph and MySQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Graph–MySQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Graph 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 Microsoft Graph or MySQL record.
Observability
Monitoring
Track your Microsoft Graph ⇄ MySQL sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft Graph and MySQL.
How the Microsoft Graph and MySQL connectors work
Microsoft Graph
- Integration surface
- Microsoft Graph unified REST API (v1.0 and beta) at graph.microsoft.com, spanning Microsoft 365 services — Entra ID, Outlook mail and calendar, OneDrive and SharePoint, Teams, and Planner; supports JSON $batch (up to 20 requests per call).
- Authentication
- OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Mail.ReadWrite, Calendars.ReadWrite, Files.ReadWrite.All, User.ReadWrite.All, and Group.ReadWrite.All; application permissions require tenant admin consent.
- Change detection
- Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and driveItems; change-notification subscriptions (webhooks) POST near-real-time notifications to a notification URL and must be renewed before they expire.
- Capabilities
- read · write · webhooks
- Rate limits
- Throttled per app and per tenant, returning HTTP 429 with a Retry-After header; limits vary by service — the Outlook mail service allows about 10,000 requests per 10 minutes per app per mailbox with up to 4 concurrent requests, and delta and subscription tokens expire and must be renewed.
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 Microsoft Graph 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 Microsoft Graph 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.
Microsoft Graph
connected
MySQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Graph 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 · Microsoft Graph ⇄ 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.
Microsoft Graph MySQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Graph and MySQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Graph and MySQL: authenticate both systems, choose the objects to sync (such as Microsoft Graph's Users and Groups and memberships), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Graph and MySQL. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Microsoft Graph: Delta query (change tracking) returns created, updated, and deleted items since the last deltaLink for users, groups, mail, events, contacts, and driveItems; change-notification subscriptions (webhooks) POST near-real-time notifications to a notification URL and must be renewed before they expire. On MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MySQL side: JSON Columns, Stored Procedures, Triggers, Databases (Schemas), plus custom fields where MySQL exposes them. On the Microsoft Graph side: Calendar events, Contacts, Drive items (OneDrive & SharePoint), Teams messages and chats. 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 Microsoft Graph and MySQL: Land tool activity as queryable rows; One integration pattern instead of per-tool API code; React to changes on either side in near real time. Records and events from Microsoft Graph arrive in MySQL as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.
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 358 integrations available for Microsoft Graph and MySQL.
Popular · 4 of 358
No integrations match .
