Skip to content
Developer tools ⇄ Business productivity

Jira to Microsoft Dynamics 365 integration — real-time, two-way sync

Keep Jira and Microsoft Dynamics 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 Jira and Microsoft Dynamics 365

Connect the tickets, records, and events in Microsoft Dynamics 365 to the systems engineering runs in Jira, 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. Jira 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 Opportunities, Cases (Incidents), Quotes, Orders & Invoices, Products in Microsoft Dynamics 365 with Users, Issues, Projects, Comments in Jira 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 Two-way sync of accounts and contacts with a Postgres or SQL database so engineers query SQL while sales works in Dynamics.
  • 02 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
  • 03 Consolidate multiple Jira Projects or sites into one database, mapping Projects, Components, and Versions for cross-team reporting.
  • 04 Two-way sync Issues and their status, assignee, and story points with a Postgres database so teams query and update sprint data in SQL.

Common sync patterns

Where Jira moves messages between services: activity lands on the stream

Records created or changed in Microsoft Dynamics 365 publish to the queue or topic in Jira as they happen, so downstream services react to real events rather than polling for them.

Where Jira is the directory or identity source: one set of users

People and accounts in Microsoft Dynamics 365 stay matched to the users in Jira, so access, provisioning, and org changes propagate instead of being keyed in twice.

Where Jira watches operations: live volumes for visibility

Open items, throughput, and error counts from Microsoft Dynamics 365 replicate into Jira, so the operational view reflects what is actually happening in the business.

What you can sync between Jira and Microsoft Dynamics 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.

Jira objects Microsoft Dynamics 365 objects How this pairing syncs
Users Account records referenced as reporters, assignees, and watchers; read to resolve accountId to a person when mapping Issue ownership. Cases (Incidents) Support records shared with ticketing tools and product databases. Users is specific to Jira and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Issues Core work items (stories, bugs, tasks, epics, sub-tasks); synced two-way with databases and other trackers, keyed by issue key with an updated field for incrementals. Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. Issues is specific to Jira and Quotes, Orders & Invoices to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Projects Containers that group Issues, workflows, and permissions; usually read to segment syncs by team, or written when standing up a new project. Products Catalog records aligned with ERP item masters. Projects is specific to Jira and Products to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Comments Discussion threads on Issues; in v3 the body is Atlassian Document Format JSON, so rich text is preserved when syncing to and from other systems. Activities Emails, calls, and tasks captured for engagement analytics. Comments is specific to Jira and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Worklogs Time-tracking entries against Issues; read into warehouses for effort and capacity reporting, or written back from timesheet tools. Custom Tables Dataverse tables that carry business-specific entities through the same API surface. Worklogs is specific to Jira and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Sprints Agile iterations from the Jira Software API; synced to report scope, velocity, and burndown, and to move Issues between sprints. Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. Sprints is specific to Jira and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.

How changes propagate between Jira and Microsoft Dynamics 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.

Jira Microsoft Dynamics 365 Sub-second propagation

DetectionJira notifies Stacksync of record changes through webhook events. Jira webhooks (jira:issue_created / _updated / _deleted plus comment and worklog events) for near-real-time.

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

Microsoft Dynamics 365 Jira 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 Jira through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Jira: Cost-based (points) model; 429 responses return Retry-After and X-RateLimit-* headers. JQL search costs far more than single-issue reads.
What ships with Jira ⇄ Microsoft Dynamics 365

Connect Jira and Microsoft Dynamics 365 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jira–Microsoft Dynamics 365 connection.

Real-time

Two-way sync

Changes in Jira or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Jira or Microsoft Dynamics 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 Jira or Microsoft Dynamics 365 record.

Observability

Monitoring

Track your Jira ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Jira and Microsoft Dynamics 365.

How the Jira and Microsoft Dynamics 365 connectors work

Jira

Integration surface
REST API v2 and v3 plus the Jira Software (Agile) REST API
Authentication
OAuth 2.0 (3LO) for apps, or Basic auth with an Atlassian account email plus API token
Change detection
Jira webhooks (jira:issue_created / _updated / _deleted plus comment and worklog events) for near-real-time; incremental JQL polling on the issue updated timestamp as a best-effort reconciliation fallback.
Capabilities
read · write · webhooks
Rate limits
Cost-based (points) model; 429 responses return Retry-After and X-RateLimit-* headers. JQL search costs far more than single-issue reads.

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
Microsoft Dynamics 365 setup guide
How it works

How to connect Jira to Microsoft Dynamics 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 Jira and Microsoft Dynamics 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
    Jira connected
    Microsoft Dynamics 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Jira and Microsoft Dynamics 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 · Jira ⇄ Microsoft Dynamics 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
    Jira Microsoft Dynamics 365
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Jira and Microsoft Dynamics 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 392 integrations available for Jira and Microsoft Dynamics 365.

Popular · 8 of 392
All Jira integrations All Microsoft Dynamics 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