Skip to content
Database ⇄ Business productivity

Azure Cosmos DB to Microsoft 365 integration — real-time, two-way sync

Keep Azure Cosmos DB and Microsoft 365 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 Cosmos DB and Microsoft 365

Mirror Microsoft 365's data into Azure Cosmos DB so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Microsoft 365 through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Azure Cosmos DB.

Stacksync mirrors Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists, Teams from Microsoft 365 into Stored procedures and triggers, Databases, Containers, Items (JSON documents) in Azure Cosmos DB and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Microsoft 365, so the tool and the database never disagree.

Common use cases

  • 01 Sync SharePoint lists with operational databases so business users edit in SharePoint while systems read SQL.
  • 02 Archive mail and file metadata into a warehouse for compliance and activity analytics.
  • 03 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 04 Consolidate documents from multiple containers into a single reporting store.

Common sync patterns

Read Microsoft 365 with a query

Records from Microsoft 365 are ordinary rows in Azure Cosmos DB; join them, index them, and use them in application logic without touching the vendor API.

Automate Microsoft 365 from your codebase

Write to the synced tables in Azure Cosmos DB and Stacksync propagates the change into Microsoft 365, replacing custom integration code.

React to changes as they happen

Updates in Microsoft 365 arrive as row changes in Azure Cosmos DB, so triggers, jobs, and services can respond in near real time.

What you can sync between Azure Cosmos DB and Microsoft 365

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 Cosmos DB objects Microsoft 365 objects How this pairing syncs
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Planner & To Do Tasks Task items synced with project and work-management tools. Change feed entries is specific to Azure Cosmos DB and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Users Entra ID user accounts synced with HR and identity systems. Stored procedures and triggers is specific to Azure Cosmos DB and Users to Microsoft 365 — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Groups Microsoft 365 and security groups kept aligned with org structure and access rules. Databases is specific to Azure Cosmos DB and Groups to Microsoft 365 — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Mail Messages Exchange Online messages read for logging, archiving, or activity capture. Containers is specific to Azure Cosmos DB and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. Items (JSON documents) is specific to Azure Cosmos DB and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Contacts Personal and org contacts kept consistent with CRM contact records. Partition keys is specific to Azure Cosmos DB and Contacts to Microsoft 365 — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Microsoft 365

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 Cosmos DB Microsoft 365 Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.

Microsoft 365 Azure Cosmos DB Sub-second propagation

DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.

DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.

What ships with Azure Cosmos DB ⇄ Microsoft 365

Connect Azure Cosmos DB and Microsoft 365 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Microsoft 365 connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Cosmos DB or Microsoft 365 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 Cosmos DB or Microsoft 365 record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Microsoft 365.

How the Azure Cosmos DB and Microsoft 365 connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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
How it works

How to connect Azure Cosmos DB to Microsoft 365 — 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.

  1. 01

    Connect your apps

    Authenticate Azure Cosmos DB and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Cosmos DB connected
    Microsoft 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Cosmos DB and Microsoft 365 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Cosmos DB ⇄ Microsoft 365
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Cosmos DB Microsoft 365
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Cosmos DB and Microsoft 365 integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 387 integrations available for Azure Cosmos DB and Microsoft 365.

Popular · 4 of 387
All Azure Cosmos DB integrations All Microsoft 365 integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own