Real-time
Two-way sync
Changes in Microsoft 365 or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Data warehouse
Microsoft 365 to MotherDuck integration — real-time, two-way sync
Keep Microsoft 365 and MotherDuck 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 365 and MotherDuck
Get the data locked inside Microsoft 365 into MotherDuck as live tables, and send results back where Microsoft 365 can use them, without writing a pipeline.
Whatever Microsoft 365 is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists, Teams from Microsoft 365 into tables in MotherDuck continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in MotherDuck can also be written back into fields in Microsoft 365 where the tool can use them.
Common use cases
- Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- Sync employee records from an HR system into Entra ID users and group memberships.
- Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
- Sync modeled MotherDuck tables outward to operational tools for activation
Where Microsoft 365 accepts updates: operational write-back
Segments, scores, or reference values computed in MotherDuck sync back onto records in Microsoft 365, putting analysis where the work happens.
History that outlives the tool
A continuously synced copy in MotherDuck preserves a queryable record even as data ages out of Microsoft 365 or gets changed inside it.
Analytics on Microsoft 365's data
Records and events from Microsoft 365 land in MotherDuck as queryable tables, current within seconds and ready to join with the rest of the warehouse.
What you can sync between Microsoft 365 and MotherDuck
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 365 objects | MotherDuck objects | |
|---|---|---|
| Planner & To Do Tasks Task items synced with project and work-management tools. | Tables The main landing target for synced records and source for analysis. | |
| Users Entra ID user accounts synced with HR and identity systems. | Views Modeled projections used as outbound sync sources. | |
| Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Contacts Personal and org contacts kept consistent with CRM contact records. | Schemas Namespaces within a database used to organize synced tables. |
What ships with Microsoft 365 ⇄ MotherDuck
Connect Microsoft 365 and MotherDuck for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–MotherDuck connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft 365 or MotherDuck 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 365 or MotherDuck record.
Observability
Monitoring
Track your Microsoft 365 ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft 365 and MotherDuck.
How the Microsoft 365 and MotherDuck connectors work
Microsoft 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
MotherDuck
- Integration surface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- Change detection
- Polling; no log-based CDC or webhook surface is exposed
- Capabilities
- read · write
- Rate limits
- Subject to the platform's compute and concurrency limits rather than per-request API rate limits
How it works
How to connect Microsoft 365 to MotherDuck — 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 365 and MotherDuck with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Microsoft 365
connected
MotherDuck
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft 365 and MotherDuck 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 365 ⇄ MotherDuckCustomers 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 365 MotherDuckCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft 365 and MotherDuck integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft 365 and MotherDuck: authenticate both systems, choose the objects to sync (such as Microsoft 365's Planner & To Do Tasks and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Microsoft 365 and MotherDuck: Where Microsoft 365 accepts updates: operational write-back; History that outlives the tool; Analytics on Microsoft 365's data. Segments, scores, or reference values computed in MotherDuck sync back onto records in Microsoft 365, putting analysis where the work happens.
-
Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Change notifications can push events for resources such as messages, events, and driveItems, with subscriptions that must be periodically renewed. MotherDuck: Databases can be shared with other users as read-only shares, separating producers from consumers. Stacksync's field mapping accounts for these differences between Microsoft 365 and MotherDuck 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 Microsoft 365 and MotherDuck records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Microsoft 365 and MotherDuck connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft 365–MotherDuck integration in-house.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Microsoft 365 and MotherDuck.
Popular · 8 of 386
-
Microsoft 365 ⇄ Tinybird -
Microsoft 365 ⇄ Vertica -
Microsoft 365 ⇄ Yellowbrick -
Microsoft 365 ⇄ Snowflake -
MotherDuck ⇄ eClinicalWorks -
MotherDuck ⇄ Full Enrich -
MotherDuck ⇄ Google Sheets -
MotherDuck ⇄ Klaviyo
No integrations match .
