Skip to content
ERP ⇄ Storage

Dynamics 365 F&O to Sharepoint integration — real-time, two-way sync

Keep Dynamics 365 F&O and Sharepoint 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 Sharepoint

Move the documents and data that Dynamics 365 F&O produces into Sharepoint as files, and let files stored in Sharepoint update the records they belong to in Dynamics 365 F&O, continuously and without exports or manual filing.

Dynamics 365 F&O runs the business on structured records: Vendors, Released Products, Sales Orders, Purchase Orders. Sharepoint holds files and the metadata that describes them: List items, Drive items (document libraries), Columns and content types, Permissions and sharing. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Dynamics 365 F&O touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Sharepoint, from signed contracts to vendor bills to receipts, describe a transaction Dynamics 365 F&O needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.

Stacksync keeps Vendors, Released Products, Sales Orders, Purchase Orders in Dynamics 365 F&O and List items, Drive items (document libraries), Columns and content types, Permissions and sharing in Sharepoint in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Sharepoint already labeled and filed, and metadata captured against a stored file can create or update the matching record in Dynamics 365 F&O. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.

The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Dynamics 365 F&O and the file in Sharepoint never describe two different versions of the same document.

Common use cases

  • 01 Mirror GL journals and invoice lines into a warehouse for finance reporting without recurring DMF exports.
  • 02 Distribute product and price master data from F&O to downstream channels through a synced database.
  • 03 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.
  • 04 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.

Common sync patterns

Audit-ready retention

Every transaction's supporting file lives in Sharepoint beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Dynamics 365 F&O.

Documents filed with their context

Files that Dynamics 365 F&O produces land in Sharepoint labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.

Metadata that files itself

Record fields from Dynamics 365 F&O, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Sharepoint, so storage stays organized without anyone tagging by hand.

What you can sync between Dynamics 365 F&O and Sharepoint

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 Sharepoint objects How this pairing syncs
Sales Orders Order transactions; written in from storefronts or CRM and tracked through fulfillment. List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. Sales Orders is specific to Dynamics 365 F&O and List items to Sharepoint — each maps to any object or custom field on the other side.
Purchase Orders Procurement transactions; extracted for spend and supply chain reporting. Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. Purchase Orders is specific to Dynamics 365 F&O and Drive items (document libraries) to Sharepoint — 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. Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. Customer Invoices is specific to Dynamics 365 F&O and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Vendor Invoices AP documents; synced with invoice automation systems. Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. Vendor Invoices is specific to Dynamics 365 F&O and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
General Journal Entries GL postings; read-only extracts for consolidated finance reporting. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. General Journal Entries is specific to Dynamics 365 F&O and Site pages to Sharepoint — each maps to any object or custom field on the other side.
On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. On-hand Inventory is specific to Dynamics 365 F&O and Sites to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 F&O and Sharepoint

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

Sharepoint Dynamics 365 F&O Sub-second propagation

DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.

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.
  • Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with Dynamics 365 F&O ⇄ Sharepoint

Connect Dynamics 365 F&O and Sharepoint for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Sharepoint connection.

Real-time

Two-way sync

Changes in Dynamics 365 F&O or Sharepoint instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 F&O or Sharepoint 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 Sharepoint record.

Observability

Monitoring

Track your Dynamics 365 F&O ⇄ Sharepoint 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 Sharepoint.

How the Dynamics 365 F&O and Sharepoint 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.
Dynamics 365 F&O setup guide

Sharepoint

Integration surface
Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
Change detection
Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
Capabilities
read · write · webhooks
Rate limits
SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works

How to connect Dynamics 365 F&O to Sharepoint — 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 Dynamics 365 F&O and Sharepoint 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
    Dynamics 365 F&O connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Dynamics 365 F&O and Sharepoint 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 405 integrations available for Dynamics 365 F&O and Sharepoint.

Popular · 6 of 405
All Dynamics 365 F&O integrations All Sharepoint 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