Skip to content
Business productivity ⇄ Storage

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

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

Land the records and documents that build up in Microsoft Dynamics 365 into Sharepoint as they are created, and surface Sharepoint's file details on the Microsoft Dynamics 365 records that point to them, without an export job to maintain.

Microsoft Dynamics 365 and Sharepoint hold different kinds of data. Microsoft Dynamics 365 carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Sharepoint holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Microsoft Dynamics 365 produces has to be kept somewhere durable, and many of the files Sharepoint stores are the very documents Microsoft Dynamics 365's records point to.

Stacksync syncs Products, Activities, Custom Tables, Accounts in Microsoft Dynamics 365 with Permissions and sharing, Site pages, Sites, Lists in Sharepoint in real time. Records and attachments created in Microsoft Dynamics 365 are written into Sharepoint as objects or files within seconds of being created. In the other direction, the metadata Sharepoint keeps about those files — name, location, owner, modified date — flows back onto the matching record in Microsoft Dynamics 365, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.

Common use cases

  • 01 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
  • 02 Sync cases with external ticketing or product systems so support works one queue.
  • 03 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.
  • 04 Stream list and library changes through delta query and change-notification webhooks into a warehouse for audit, access-review, and reporting.

Common sync patterns

A copy that outlives the tool

A continuously synced copy in Sharepoint preserves records and documents even as they age out of Microsoft Dynamics 365 or get changed inside it, so history stays intact and reachable.

Feed a data lake or downstream pipeline

Structured records from Microsoft Dynamics 365 land in Sharepoint as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.

Archive what Microsoft Dynamics 365 produces into Sharepoint

Records and events from Microsoft Dynamics 365 — tickets, messages, orders, or issues — are written into Sharepoint as objects or files as they change, giving you a durable, addressable copy for retention and audit.

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

Microsoft Dynamics 365 objects Sharepoint objects How this pairing syncs
Products Catalog records aligned with ERP item masters. 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. Products is specific to Microsoft Dynamics 365 and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Activities Emails, calls, and tasks captured for engagement analytics. 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. Activities is specific to Microsoft Dynamics 365 and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Custom Tables Dataverse tables that carry business-specific entities through the same API surface. 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. Custom Tables is specific to Microsoft Dynamics 365 and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Accounts is specific to Microsoft Dynamics 365 and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Contacts Person records kept consistent with marketing, support, and data-warehouse copies. 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. Contacts is specific to Microsoft Dynamics 365 and Sites to Sharepoint — each maps to any object or custom field on the other side.
Leads Inbound records enriched and routed from external sources into sales queues. Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. Leads is specific to Microsoft Dynamics 365 and Lists to Sharepoint — each maps to any object or custom field on the other side.

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

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

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

Rate-limit considerations

  • 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 Microsoft Dynamics 365 ⇄ Sharepoint

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Microsoft Dynamics 365 ⇄ Sharepoint 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 Sharepoint.

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

    Choose tables

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

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

Popular · 7 of 504
All Microsoft Dynamics 365 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