Real-time
Two-way sync
Changes in Box or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Business productivity
Box to Microsoft 365 integration — real-time, two-way sync
Keep Box and Microsoft 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 365
Land the records and documents that build up in Microsoft 365 into Box as they are created, and surface Box's file details on the Microsoft 365 records that point to them, without an export job to maintain.
Microsoft 365 and Box hold different kinds of data. Microsoft 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 365 produces has to be kept somewhere durable, and many of the files Box stores are the very documents Microsoft 365's records point to.
Stacksync syncs Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists in Microsoft 365 with Collaborations, Users, Groups, Tasks in Box in real time. Records and attachments created in Microsoft 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 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 Sync employee records from an HR system into Entra ID users and group memberships.
- 02 Mirror calendar events into scheduling or CRM tools so meetings appear on customer timelines.
- 03 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.
- 04 Mirror Metadata template instances on Files into database columns so contracts and assets are searchable and reportable alongside other business data.
Common sync patterns
A copy that outlives the tool
A continuously synced copy in Box preserves records and documents even as they age out of Microsoft 365 or get changed inside it, so history stays intact and reachable.
Feed a data lake or downstream pipeline
Structured records from Microsoft 365 land in Box as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.
Archive what Microsoft 365 produces into Box
Records and events from Microsoft 365 — tickets, messages, orders, or issues — are written into Box as objects or files as they change, giving you a durable, addressable copy for retention and audit.
What you can sync between Box and Microsoft 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 365 objects | How this pairing syncs | |
|---|---|---|---|
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Users Entra ID user accounts synced with HR and identity systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Contacts Personal and org contacts kept consistent with CRM contact records. | Tasks is specific to Box and Contacts to Microsoft 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. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Events is specific to Box and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | SharePoint Sites & Lists List items read and written like lightweight database tables. | Files is specific to Box and SharePoint Sites & Lists to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Teams Team and membership data provisioned from upstream systems. | Folders is specific to Box and Teams to Microsoft 365 — each maps to any object or custom field on the other side. |
How changes propagate between Box and Microsoft 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 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 365 through its API, with automatic retries and rate-limit backoff.
Microsoft 365 Box Sub-second propagation
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
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 365
Connect Box and Microsoft 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Microsoft 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box or Microsoft 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 365 record.
Observability
Monitoring
Track your Box ⇄ Microsoft 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 365.
How the Box and Microsoft 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 365
- Integration surface
- REST API (Microsoft Graph)
- Authentication
- OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions
- Change detection
- Graph change notifications (webhooks) plus delta queries for incremental sync
- Capabilities
- read · write · webhooks
How it works
How to connect Box to Microsoft 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 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 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box and Microsoft 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 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 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Microsoft 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Microsoft 365: authenticate both systems, choose the objects to sync (such as Box's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Box: 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. On Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft 365 side: Calendar Events, Contacts, OneDrive Files (driveItems), SharePoint Sites & Lists, plus custom fields where Microsoft 365 exposes them. On the Box side: Collaborations, Users, Groups, Tasks. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Box and Microsoft 365: A copy that outlives the tool; Feed a data lake or downstream pipeline; Archive what Microsoft 365 produces into Box. A continuously synced copy in Box preserves records and documents even as they age out of Microsoft 365 or get changed inside it, so history stays intact and reachable.
-
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 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
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 446 integrations available for Box and Microsoft 365.
Popular · 7 of 446
-
Box ⇄ NextGen Healthcare -
Box ⇄ Orderful -
Box ⇄ Resend -
Box ⇄ ServiceNow -
Microsoft 365 ⇄ Amazon S3 -
Microsoft 365 ⇄ Sharepoint -
Microsoft 365 ⇄ Egnyte
No integrations match .
