Real-time
Two-way sync
Changes in Dynamics 365 F&O or Splunk instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Analytics
Dynamics 365 F&O to Splunk integration — real-time, two-way sync
Keep Dynamics 365 F&O and Splunk 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 Dynamics 365 F&O and Splunk
Put Dynamics 365 F&O's records into Splunk as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Splunk computes back where Dynamics 365 F&O can use them.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Dynamics 365 F&O carries financials, operations, workforce data, or all three, those numbers belong in Splunk, next to the product, behavioral, and web data the team already measures.
Stacksync syncs Purchase Orders, Customer Invoices, Vendor Invoices, General Journal Entries from Dynamics 365 F&O into Splunk continuously, handling API limits and schema drift as it goes, so each record type arrives as Indexes, HTTP Event Collector, Users and Roles, Dashboards ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Splunk can be written back to fields in Dynamics 365 F&O where that is useful.
Common use cases
- 01 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 02 Provision and update Saved Searches, alerts, and Dashboards from a Git-backed config repository so detections and reports stay versioned and consistent across search heads.
- 03 Push sales orders from e-commerce into F&O and sync fulfillment and invoice status back to the storefront.
- 04 Mirror GL journals and invoice lines into a warehouse for finance reporting without recurring DMF exports.
Common sync patterns
Where Dynamics 365 F&O holds the books: revenue and finance dashboards from live data
Financial records from Dynamics 365 F&O land in Splunk as they change, so revenue, margin, and spend dashboards read current figures rather than last night's export.
Where Dynamics 365 F&O runs order-to-cash: customer and account analytics
Orders, invoices, and account records from Dynamics 365 F&O join the behavioral and usage data Splunk already tracks, so customer analysis spans activity and dollars in one view.
Where Dynamics 365 F&O runs operations: inventory and fulfillment metrics
Operational records from Dynamics 365 F&O become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.
What you can sync between Dynamics 365 F&O and Splunk
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.
| Dynamics 365 F&O objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Supplier master records; synced with procurement and AP tools. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Vendors is specific to Dynamics 365 F&O and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Released Products Sellable product master; read out to commerce channels and CRM catalogs. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Released Products is specific to Dynamics 365 F&O and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Sales Orders is specific to Dynamics 365 F&O and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Purchase Orders is specific to Dynamics 365 F&O and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Customer Invoices AR billing documents; status synced back to CRM and customer success tools. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Customer Invoices is specific to Dynamics 365 F&O and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Vendor Invoices AP documents; synced with invoice automation systems. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Vendor Invoices is specific to Dynamics 365 F&O and Saved Searches to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 F&O and Splunk
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.
Dynamics 365 F&O Splunk Sub-second propagation
DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.
DeliveryEach detected change is written to Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Dynamics 365 F&O Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
DeliveryEach detected change is written to Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Dynamics 365 F&O ⇄ Splunk
Connect Dynamics 365 F&O and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 F&O or Splunk 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 Dynamics 365 F&O or Splunk record.
Observability
Monitoring
Track your Dynamics 365 F&O ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Splunk.
How the Dynamics 365 F&O and Splunk connectors work
Dynamics 365 F&O
- Integration surface
- OData REST endpoint over data entities, plus the Data Management Framework for batch
- Authentication
- OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
- Change detection
- Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Dynamics 365 F&O to Splunk — 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 Dynamics 365 F&O and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dynamics 365 F&O
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 F&O and Splunk 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 · Dynamics 365 F&O ⇄ SplunkCustomers 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.
Dynamics 365 F&O SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 F&O and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 F&O and Splunk: authenticate both systems, choose the objects to sync (such as Dynamics 365 F&O's Vendors and Released Products), 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 Dynamics 365 F&O and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamics 365 F&O and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 F&O–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamics 365 F&O and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dynamics 365 F&O: Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable. On Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Splunk side: Indexes, HTTP Event Collector, Users and Roles, Dashboards, plus custom fields where Splunk exposes them. On the Dynamics 365 F&O side: Purchase Orders, Customer Invoices, Vendor Invoices, General Journal Entries. 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
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 386 integrations available for Dynamics 365 F&O and Splunk.
Popular · 8 of 386
-
Dynamics 365 F&O ⇄ Microsoft Power Bi -
Dynamics 365 F&O ⇄ Tableau -
Dynamics 365 F&O ⇄ Adobeanalytics -
Dynamics 365 F&O ⇄ Pendo -
Splunk ⇄ Microsoft Dynamics GP - Splunk ⇄ Microsoft Dynamics NAV
-
Splunk ⇄ Plex ERP -
Splunk ⇄ QAD ERP
No integrations match .
