Real-time
Two-way sync
Changes in Datadog or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Business productivity
Datadog to Microsoft 365 integration — real-time, two-way sync
Keep Datadog 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 Datadog and Microsoft 365
Connect the tickets, records, and events in Microsoft 365 to the systems engineering runs in Datadog, kept current in real time and in both directions.
Microsoft 365 is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Datadog is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.
Stacksync syncs Groups, Mail Messages, Calendar Events, Contacts in Microsoft 365 with Metrics, Incidents, Service Level Objectives, Hosts in Datadog field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.
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 Pull the Hosts inventory into a CMDB or database for asset tracking, tag hygiene, and cost allocation across teams.
- 04 Sync Monitors and their alert state into Postgres so reliability teams query alert history and noisy-monitor trends in SQL.
Common sync patterns
Where Datadog is the directory or identity source: one set of users
People and accounts in Microsoft 365 stay matched to the users in Datadog, so access, provisioning, and org changes propagate instead of being keyed in twice.
Where Datadog watches operations: live volumes for visibility
Open items, throughput, and error counts from Microsoft 365 replicate into Datadog, so the operational view reflects what is actually happening in the business.
One shared record across both systems
Where both systems keep records for the same contacts, items, or users, a correction in either updates the other, ending dual maintenance and keeping IDs aligned for every other flow.
What you can sync between Datadog 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.
| Datadog objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Dashboards Dashboard definitions and widgets via the v1 Dashboards API with full CRUD; exported for backup and audit, or created and updated programmatically from a source of truth. | Teams Team and membership data provisioned from upstream systems. | Dashboards is specific to Datadog and Teams to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Metrics Time-series metrics queried in aggregate windows through the query API and submitted via POST /api/v1/series; individual raw points cannot be extracted beyond retention. | Planner & To Do Tasks Task items synced with project and work-management tools. | Metrics is specific to Datadog and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Incidents Incident records from the v2 Incidents API with full CRUD, including status and timeline fields; landed in a database for MTTR reporting or created and updated from an external incident workflow. | Users Entra ID user accounts synced with HR and identity systems. | Incidents is specific to Datadog and Users to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Service Level Objectives SLO definitions and status history via the v1 SLO API with full CRUD; read out for reliability and error-budget reporting, or provisioned and updated from a reliability config. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Service Level Objectives is specific to Datadog and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Hosts Infrastructure host inventory with tags and metadata from the v1 host list API; loaded into a CMDB or warehouse for asset tracking, and hosts can be muted or unmuted via the API. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Hosts is specific to Datadog and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Monitors Alert definitions with query, thresholds, and current state via the v1 Monitors API, which supports full create, update, and delete; Stacksync reads alert state into a warehouse or provisions and updates monitors from a config source. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Monitors is specific to Datadog and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Datadog 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.
Datadog Microsoft 365 Sub-second propagation
DetectionDatadog notifies Stacksync of record changes through webhook events. Polling with time-windowed search queries on Logs and Events (timestamp cursor).
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Datadog 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 Datadog through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Datadog: Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
What ships with Datadog ⇄ Microsoft 365
Connect Datadog and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Datadog–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Datadog 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 Datadog or Microsoft 365 record.
Observability
Monitoring
Track your Datadog ⇄ 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 Datadog and Microsoft 365.
How the Datadog and Microsoft 365 connectors work
Datadog
- Integration surface
- REST API (v1 and v2)
- Authentication
- API key (DD-API-KEY) plus an Application key (DD-APPLICATION-KEY) sent as request headers; application keys are tied to the creating user and inherit that user's permissions and authorization scopes.
- Change detection
- Polling with time-windowed search queries on Logs and Events (timestamp cursor); monitor alerts can also push via the Webhooks notification integration. No modified-date CDC on mutable objects.
- Capabilities
- read · write · webhooks
- Rate limits
- Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
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 Datadog 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.
- 01
Connect your apps
Authenticate Datadog 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.
Datadog
connected
Microsoft 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Datadog 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.
objects · Datadog ⇄ Microsoft 365Customers 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.
Datadog Microsoft 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Datadog and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Datadog and Microsoft 365: authenticate both systems, choose the objects to sync (such as Datadog's Dashboards and Metrics), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Microsoft 365 side: Groups, Mail Messages, Calendar Events, Contacts, plus custom fields where Microsoft 365 exposes them. On the Datadog side: Metrics, Incidents, Service Level Objectives, Hosts. 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 Datadog and Microsoft 365: Where Datadog is the directory or identity source: one set of users; Where Datadog watches operations: live volumes for visibility; One shared record across both systems. People and accounts in Microsoft 365 stay matched to the users in Datadog, so access, provisioning, and org changes propagate instead of being keyed in twice.
-
Datadog: REST API (v1 and v2). Authentication: API key (DD-API-KEY) plus an Application key (DD-APPLICATION-KEY) sent as request headers; application keys are tied to the creating user and inherit that user's permissions and authorization scopes. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Nearly all Microsoft 365 workloads (Exchange, SharePoint, OneDrive, Teams, Entra ID) are exposed through the single Microsoft Graph endpoint rather than per-product APIs. Datadog: Datadog is multi-region (US1, US3, US5, EU1, AP1, US1-FED); the API host differs per site (api.datadoghq.com vs api.datadoghq.eu) and API and application keys are scoped to a single site. Stacksync's field mapping accounts for these differences between Datadog and Microsoft 365 without custom code.
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 334 integrations available for Datadog and Microsoft 365.
Popular · 8 of 334
-
Datadog ⇄ Wrike -
Datadog ⇄ Zendesk -
Datadog ⇄ Campfire -
Datadog ⇄ Front -
Microsoft 365 ⇄ PagerDuty -
Microsoft 365 ⇄ Jira -
Microsoft 365 ⇄ Rabbitmq -
Microsoft 365 ⇄ Azure Service Bus
No integrations match .
