Real-time
Two-way sync
Changes in Microsoft Dynamics 365 or PagerDuty instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Developer tools
Microsoft Dynamics 365 to PagerDuty integration — real-time, two-way sync
Keep Microsoft Dynamics 365 and PagerDuty 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 Dynamics 365 and PagerDuty
Connect the tickets, records, and events in Microsoft Dynamics 365 to the systems engineering runs in PagerDuty, kept current in real time and in both directions.
Microsoft Dynamics 365 is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. PagerDuty 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 Accounts, Contacts, Leads, Opportunities in Microsoft Dynamics 365 with Escalation Policies, On-Calls, Notes and Log Entries, Incidents in PagerDuty 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 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Mirror Services and their integration keys with a CMDB or service catalog so ownership and tier metadata stay aligned in both directions.
- 04 Provision and deactivate Users and Team memberships two-way from an HRIS or identity provider so the on-call roster matches the current org.
Common sync patterns
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.
Where PagerDuty tracks engineering work: requests become issues
A ticket or request raised in Microsoft Dynamics 365 opens or updates a matching issue in PagerDuty, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.
Where PagerDuty moves messages between services: activity lands on the stream
Records created or changed in Microsoft Dynamics 365 publish to the queue or topic in PagerDuty as they happen, so downstream services react to real events rather than polling for them.
What you can sync between Microsoft Dynamics 365 and PagerDuty
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 Dynamics 365 objects | PagerDuty objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Users Responders with contact methods and notification rules; provisioned and updated two-way to keep the on-call roster aligned with an HRIS or identity provider. | Contacts is specific to Microsoft Dynamics 365 and Users to PagerDuty — each maps to any object or custom field on the other side. | |
| Leads Inbound records enriched and routed from external sources into sales queues. | Teams Groupings of users, services, and escalation policies; synced two-way so membership mirrors org structure from an IdP or HRIS. | Leads is specific to Microsoft Dynamics 365 and Teams to PagerDuty — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Schedules On-call rotations built from layers and overrides; read and written so calendar or workforce tools can drive who is on call. | Opportunities is specific to Microsoft Dynamics 365 and Schedules to PagerDuty — each maps to any object or custom field on the other side. | |
| Cases (Incidents) Support records shared with ticketing tools and product databases. | Escalation Policies Ordered rules routing incidents to users and schedules; read and written two-way to codify paging logic from a source of truth. | Cases (Incidents) is specific to Microsoft Dynamics 365 and Escalation Policies to PagerDuty — each maps to any object or custom field on the other side. | |
| Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | On-Calls Computed view of who is on call now, derived from schedules and escalation policies; read-only, ideal for pushing current responders into other systems. | Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and On-Calls to PagerDuty — each maps to any object or custom field on the other side. | |
| Products Catalog records aligned with ERP item masters. | Notes and Log Entries Notes are writable to append context to an incident; log entries are a read-only record of every action taken on that incident. | Products is specific to Microsoft Dynamics 365 and Notes and Log Entries to PagerDuty — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics 365 and PagerDuty
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 Dynamics 365 PagerDuty Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to PagerDuty through its API, with automatic retries and rate-limit backoff.
PagerDuty Microsoft Dynamics 365 Sub-second propagation
DetectionPagerDuty notifies Stacksync of record changes through webhook events. V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated).
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- PagerDuty: REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
What ships with Microsoft Dynamics 365 ⇄ PagerDuty
Connect Microsoft Dynamics 365 and PagerDuty for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–PagerDuty connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics 365 or PagerDuty 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 Dynamics 365 or PagerDuty record.
Observability
Monitoring
Track your Microsoft Dynamics 365 ⇄ PagerDuty sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 and PagerDuty.
How the Microsoft Dynamics 365 and PagerDuty connectors work
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
PagerDuty
- Integration surface
- REST API v2 (plus Events API v2 for inbound alerts)
- Authentication
- REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key
- Change detection
- V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows
- Capabilities
- read · write · webhooks
- Rate limits
- REST API allows 960 requests per minute per token and returns HTTP 429 when exceeded; the Events API is rate-limited separately per integration key.
How it works
How to connect Microsoft Dynamics 365 to PagerDuty — 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 Dynamics 365 and PagerDuty with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Microsoft Dynamics 365
connected
PagerDuty
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics 365 and PagerDuty 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 Dynamics 365 ⇄ PagerDutyCustomers 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 Dynamics 365 PagerDutyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics 365 and PagerDuty integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 and PagerDuty: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Contacts and Leads), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Microsoft Dynamics 365: Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties. On PagerDuty: V3 webhook subscriptions push incident.* and service.* events (triggered, acknowledged, escalated, resolved, created, updated); list endpoints also support polling with updated_at and since/until windows. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft Dynamics 365 side: Accounts, Contacts, Leads, Opportunities, plus custom fields where Microsoft Dynamics 365 exposes them. On the PagerDuty side: Escalation Policies, On-Calls, Notes and Log Entries, Incidents. 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 Microsoft Dynamics 365 and PagerDuty: One shared record across both systems; Where PagerDuty tracks engineering work: requests become issues; Where PagerDuty moves messages between services: activity lands on the stream. 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.
-
Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). PagerDuty: REST API v2 (plus Events API v2 for inbound alerts). Authentication: REST API token via the Authorization: Token header (account-level for full access or user-level scoped to the user's permissions), or OAuth 2.0 (Authorization Code / PKCE); the Events API v2 uses a per-service routing (integration) key. Stacksync manages authentication, retries, and rate limits on both sides.
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 392 integrations available for Microsoft Dynamics 365 and PagerDuty.
Popular · 8 of 392
-
Microsoft Dynamics 365 ⇄ Jms -
Microsoft Dynamics 365 ⇄ Newrelic -
Microsoft Dynamics 365 ⇄ Opsgenie -
Microsoft Dynamics 365 ⇄ Jira -
PagerDuty ⇄ Microsoft Teams -
PagerDuty ⇄ NextGen Healthcare -
PagerDuty ⇄ Orderful -
PagerDuty ⇄ Resend
No integrations match .
