Real-time
Two-way sync
Changes in Microsoft 365 or Reltio instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Database
Microsoft 365 to Reltio integration — real-time, two-way sync
Keep Microsoft 365 and Reltio 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 Reltio
Mirror Microsoft 365's data into Reltio 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 Reltio.
Stacksync mirrors Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists from Microsoft 365 into Entities, Relations, Crosswalks, Interactions in Reltio 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 Keep CRM contacts and Microsoft 365 contacts aligned in both directions.
- 02 Sync employee records from an HR system into Entra ID users and group memberships.
- 03 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
- 04 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
Common sync patterns
Read Microsoft 365 with a query
Records from Microsoft 365 are ordinary rows in Reltio; 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 Reltio 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 Reltio, so triggers, jobs, and services can respond in near real time.
What you can sync between Microsoft 365 and Reltio
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 | Reltio objects | How this pairing syncs | |
|---|---|---|---|
| Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | Mail Messages is specific to Microsoft 365 and Entities to Reltio — each maps to any object or custom field on the other side. | |
| Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Calendar Events is specific to Microsoft 365 and Relations to Reltio — each maps to any object or custom field on the other side. | |
| Contacts Personal and org contacts kept consistent with CRM contact records. | Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | Contacts is specific to Microsoft 365 and Crosswalks to Reltio — each maps to any object or custom field on the other side. | |
| OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. | OneDrive Files (driveItems) is specific to Microsoft 365 and Interactions to Reltio — each maps to any object or custom field on the other side. | |
| SharePoint Sites & Lists List items read and written like lightweight database tables. | Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. | SharePoint Sites & Lists is specific to Microsoft 365 and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side. | |
| Teams Team and membership data provisioned from upstream systems. | Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | Teams is specific to Microsoft 365 and Activity Log to Reltio — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft 365 and Reltio
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 365 Reltio 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 written to Reltio through its API, with automatic retries and rate-limit backoff.
Reltio Microsoft 365 Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Microsoft 365 ⇄ Reltio
Connect Microsoft 365 and Reltio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Reltio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft 365 or Reltio 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 Reltio record.
Observability
Monitoring
Track your Microsoft 365 ⇄ Reltio 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 Reltio.
How the Microsoft 365 and Reltio 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
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works
How to connect Microsoft 365 to Reltio — 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 Reltio 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
Reltio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft 365 and Reltio 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 ⇄ ReltioCustomers 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 ReltioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft 365 and Reltio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft 365 and Reltio: authenticate both systems, choose the objects to sync (such as Microsoft 365's Mail Messages and Calendar Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Reltio 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 Reltio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft 365–Reltio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft 365 and Reltio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. On Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft 365 side: Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists, plus custom fields where Microsoft 365 exposes them. On the Reltio side: Entities, Relations, Crosswalks, Interactions. Stacksync auto-detects both schemas and converts types between the two systems.
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
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 380 integrations available for Microsoft 365 and Reltio.
Popular · 3 of 380
No integrations match .
