Real-time
Two-way sync
Changes in Dynamics 365 F&O or GitHub instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Business productivity
Dynamics 365 F&O to GitHub integration — real-time, two-way sync
Keep Dynamics 365 F&O and GitHub 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 GitHub
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between GitHub and Dynamics 365 F&O.
Dynamics 365 F&O and GitHub connect ERP operations to the engineering workflow around them. Teams that build customizations and integrations on F&O sync entities like Sales Orders and Customer Invoices into issue and release tracking, tying GitHub Issues and Workflow runs to the ERP records they affect.
Stacksync syncs Organizations and Teams, Users, Labels and Milestones, Repositories in GitHub with Customer Invoices, Vendor Invoices, General Journal Entries, On-hand Inventory in Dynamics 365 F&O bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Common use cases
- 01 Trace an invoice discrepancy back to the Pull Request that changed the mapping.
- 02 Audit which Repositories and Releases interact with F&O Customer Invoices.
- 03 Turn recurring Purchase Order sync failures into tracked GitHub Issues.
- 04 Mirror repository, PR, and workflow-run data into a Postgres database for engineering-metrics reporting.
Common sync patterns
ERP incident tracking
data problems on F&O Sales Orders or Purchase Orders open GitHub Issues in the integration repository.
Release-gated deployments
GitHub Releases and Workflow runs (Actions) record which integration version is live against F&O entities.
Change traceability
GitHub Commits and Pull Requests are linked to the F&O objects (Customers, Released Products) their code touches.
What you can sync between Dynamics 365 F&O and GitHub
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 | GitHub objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Supplier master records; synced with procurement and AP tools. | Workflow runs (Actions) CI results synced into incident and reporting systems. | Vendors is specific to Dynamics 365 F&O and Workflow runs (Actions) to GitHub — 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. | Organizations and Teams Membership data synced with identity systems and HR directories for access reviews. | Released Products is specific to Dynamics 365 F&O and Organizations and Teams to GitHub — 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 Author and assignee identities matched to internal directories. | Sales Orders is specific to Dynamics 365 F&O and Users to GitHub — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. | Labels and Milestones Classification fields mapped to statuses and sprints in external trackers. | Purchase Orders is specific to Dynamics 365 F&O and Labels and Milestones to GitHub — 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. | Repositories Top-level containers whose metadata and settings syncs read to scope other objects. | Customer Invoices is specific to Dynamics 365 F&O and Repositories to GitHub — each maps to any object or custom field on the other side. | |
| Vendor Invoices AP documents; synced with invoice automation systems. | Issues Synced two-way with project trackers and support tools, including labels and assignees. | Vendor Invoices is specific to Dynamics 365 F&O and Issues to GitHub — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 F&O and GitHub
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 GitHub 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 GitHub through its API, with automatic retries and rate-limit backoff.
GitHub Dynamics 365 F&O Sub-second propagation
DetectionGitHub notifies Stacksync of record changes through webhook events. Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases.
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.
- GitHub: Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.
What ships with Dynamics 365 F&O ⇄ GitHub
Connect Dynamics 365 F&O and GitHub for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–GitHub connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 F&O or GitHub 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 GitHub record.
Observability
Monitoring
Track your Dynamics 365 F&O ⇄ GitHub 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 GitHub.
How the Dynamics 365 F&O and GitHub 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.
GitHub
- Integration surface
- REST API and GraphQL API
- Authentication
- OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens
- Change detection
- Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases; polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.
How it works
How to connect Dynamics 365 F&O to GitHub — 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 GitHub 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
GitHub
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 F&O and GitHub 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 ⇄ GitHubCustomers 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 GitHubCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 F&O and GitHub integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 F&O and GitHub: 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.
-
Dynamics 365 F&O: 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"). GitHub: REST API and GraphQL API. Authentication: OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
GitHub: GitHub Apps authenticate with short-lived installation tokens scoped to specific repositories and permissions, which suits least-privilege sync setups. Dynamics 365 F&O: Some complex entities cannot have change tracking turned on ('Track changes' disabled or fails validation). Stacksync's field mapping accounts for these differences between Dynamics 365 F&O and GitHub 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 Dynamics 365 F&O and GitHub 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 GitHub connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamics 365 F&O–GitHub integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamics 365 F&O and GitHub. 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 367 integrations available for Dynamics 365 F&O and GitHub.
Popular · 5 of 367
-
Dynamics 365 F&O ⇄ Front -
Dynamics 365 F&O ⇄ Amazon Seller Central -
Dynamics 365 F&O ⇄ SendGrid -
Dynamics 365 F&O ⇄ Twilio -
GitHub ⇄ Manhattan Associates WMS
No integrations match .
