Real-time
Two-way sync
Changes in Microsoft 365 or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Developer tools
Microsoft 365 to Newrelic integration — real-time, two-way sync
Keep Microsoft 365 and Newrelic 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 Newrelic
Connect the tickets, records, and events in Microsoft 365 to the systems engineering runs in Newrelic, 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. Newrelic 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 Planner & To Do Tasks, Users, Groups, Mail Messages in Microsoft 365 with Alert Policies & Conditions, NRQL Query Results, Entities, Workloads in Newrelic 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 Record deployment and change markers from CI/CD through NerdGraph change tracking to correlate releases with performance and error-rate shifts.
- 04 Sync the Entity catalog into a CMDB or warehouse for asset inventory, and add or replace entity Tags to keep ownership and environment metadata current.
Common sync patterns
Where Newrelic moves messages between services: activity lands on the stream
Records created or changed in Microsoft 365 publish to the queue or topic in Newrelic as they happen, so downstream services react to real events rather than polling for them.
Where Newrelic is the directory or identity source: one set of users
People and accounts in Microsoft 365 stay matched to the users in Newrelic, so access, provisioning, and org changes propagate instead of being keyed in twice.
Where Newrelic watches operations: live volumes for visibility
Open items, throughput, and error counts from Microsoft 365 replicate into Newrelic, so the operational view reflects what is actually happening in the business.
What you can sync between Microsoft 365 and Newrelic
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 | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | NRQL Query Results Telemetry events, metrics, logs, and spans queried through NerdGraph's nrql field (or the legacy Insights query API) over time windows; read-only and bounded by data retention, commonly streamed into a warehouse for long-term analysis. | Groups is specific to Microsoft 365 and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side. | |
| Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Entities The entity catalog of APM applications, hosts, services, and monitors searched via NerdGraph entitySearch; read for inventory, with tags added or replaced through taggingAddTagsToEntity so ownership and environment metadata stay in sync. | Mail Messages is specific to Microsoft 365 and Entities to Newrelic — each maps to any object or custom field on the other side. | |
| Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. | Calendar Events is specific to Microsoft 365 and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| Contacts Personal and org contacts kept consistent with CRM contact records. | Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. | Contacts is specific to Microsoft 365 and Synthetics Monitors to Newrelic — 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. | Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. | OneDrive Files (driveItems) is specific to Microsoft 365 and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| SharePoint Sites & Lists List items read and written like lightweight database tables. | Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. | SharePoint Sites & Lists is specific to Microsoft 365 and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft 365 and Newrelic
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 Newrelic 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 Newrelic through its API, with automatic retries and rate-limit backoff.
Newrelic Microsoft 365 Sub-second propagation
DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
What ships with Microsoft 365 ⇄ Newrelic
Connect Microsoft 365 and Newrelic for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Newrelic connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft 365 or Newrelic 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 Newrelic record.
Observability
Monitoring
Track your Microsoft 365 ⇄ Newrelic 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 Newrelic.
How the Microsoft 365 and Newrelic 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
Newrelic
- Integration surface
- NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
- Authentication
- User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
- Change detection
- NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
- Capabilities
- read · write · webhooks
- Rate limits
- NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
How it works
How to connect Microsoft 365 to Newrelic — 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 Newrelic 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
Newrelic
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft 365 and Newrelic 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 ⇄ NewrelicCustomers 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 NewrelicCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft 365 and Newrelic integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft 365 and Newrelic: authenticate both systems, choose the objects to sync (such as Microsoft 365's Groups and Mail Messages), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Newrelic: NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2. Authentication: User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP). Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft 365: Delta queries return only resources changed since the last sync token, which keeps incremental syncs cheap on large tenants. Newrelic: New Relic is region-scoped (US, EU, JP): NerdGraph is api.newrelic.com/graphql, api.eu.newrelic.com/graphql, or api.jp.newrelic.com/graphql, and keys and data belong to a single region. Stacksync's field mapping accounts for these differences between Microsoft 365 and Newrelic 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 Newrelic 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 Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft 365–Newrelic integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft 365 and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Microsoft 365 and Newrelic.
Popular · 8 of 334
-
Microsoft 365 ⇄ Opsgenie -
Microsoft 365 ⇄ PagerDuty -
Microsoft 365 ⇄ Jira -
Microsoft 365 ⇄ Rabbitmq -
Newrelic ⇄ Gainsight -
Newrelic ⇄ Ironclad -
Newrelic ⇄ Servicemax -
Newrelic ⇄ Adobe Sign
No integrations match .
