Real-time
Two-way sync
Changes in Box or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Business productivity
Box to Microsoft Dynamics 365 integration — real-time, two-way sync
Keep Box 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 Box and Microsoft Dynamics 365
Land the records and documents that build up in Microsoft Dynamics 365 into Box as they are created, and surface Box's file details on the Microsoft Dynamics 365 records that point to them, without an export job to maintain.
Microsoft Dynamics 365 and Box 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. Box 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 Box stores are the very documents Microsoft Dynamics 365's records point to.
Stacksync syncs Quotes, Orders & Invoices, Products, Activities, Custom Tables in Microsoft Dynamics 365 with Files, Folders, Metadata, Collaborations in Box in real time. Records and attachments created in Microsoft Dynamics 365 are written into Box as objects or files within seconds of being created. In the other direction, the metadata Box 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 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
- 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
Common sync patterns
Where Microsoft Dynamics 365 generates attachments: keep the files in Box
Documents attached to records in Microsoft Dynamics 365 land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.
Where Box holds the source documents: file details on the record
A file's name, location, owner, and modified date from Box sync onto the matching record in Microsoft Dynamics 365, so whoever is working there sees the current version without switching tools.
A copy that outlives the tool
A continuously synced copy in Box preserves records and documents even as they age out of Microsoft Dynamics 365 or get changed inside it, so history stays intact and reachable.
What you can sync between Box 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.
| Box objects | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Cases (Incidents) Support records shared with ticketing tools and product databases. | Metadata is specific to Box and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Collaborations is specific to Box and Quotes, Orders & Invoices to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Products Catalog records aligned with ERP item masters. | Users is specific to Box and Products to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Activities Emails, calls, and tasks captured for engagement analytics. | Groups is specific to Box and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Tasks is specific to Box and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Events is specific to Box and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
How changes propagate between Box 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.
Box Microsoft Dynamics 365 Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Box 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 Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Box ⇄ Microsoft Dynamics 365
Connect Box and Microsoft Dynamics 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Microsoft Dynamics 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box 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 Box or Microsoft Dynamics 365 record.
Observability
Monitoring
Track your Box ⇄ 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 Box and Microsoft Dynamics 365.
How the Box and Microsoft Dynamics 365 connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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
How it works
How to connect Box 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.
- 01
Connect your apps
Authenticate Box 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.
Box
connected
Microsoft Dynamics 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box 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.
objects · Box ⇄ Microsoft Dynamics 365Customers 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.
Box Microsoft Dynamics 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Microsoft Dynamics 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Box's Metadata and Collaborations), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Box: REST API (api.box.com/2.0), plus the Events API and V2 Webhooks. Authentication: OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing. Microsoft Dynamics 365: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft Dynamics 365: CDC on custom entities does not work until Change Tracking is manually enabled per table in Power Apps/Dataverse. Box: Webhooks are capped per application and per file/folder target, must be verified with Box's signature keys, and their payloads carry the object reference rather than the full changed content. Stacksync's field mapping accounts for these differences between Box and Microsoft Dynamics 365 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 Box and Microsoft Dynamics 365 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Microsoft Dynamics 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Microsoft Dynamics 365 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Box and Microsoft Dynamics 365. 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 504 integrations available for Box and Microsoft Dynamics 365.
Popular · 7 of 504
-
Box ⇄ Lusha -
Box ⇄ Microsoft 365 -
Box ⇄ Microsoft Teams -
Box ⇄ NextGen Healthcare -
Microsoft Dynamics 365 ⇄ Sharepoint -
Microsoft Dynamics 365 ⇄ Egnyte -
Microsoft Dynamics 365 ⇄ Amazon S3
No integrations match .
