Skip to content
Data warehouse ⇄ Storage

Azure Synapse Analytics to Box integration — real-time, two-way sync

Keep Azure Synapse Analytics and Box 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 Azure Synapse Analytics and Box

Bridge query-ready tables and stored files: Azure Synapse Analytics and Box keep the same records in step, in real time, in both directions.

Azure Synapse Analytics keeps the tables and query results a business reports on; Box keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Box that has to become rows in Azure Synapse Analytics, or a result in Azure Synapse Analytics that people downstream need back as a file in Box. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.

Stacksync syncs SQL pools, Tables (dedicated SQL pool), External tables, Views in Azure Synapse Analytics with Users, Groups, Tasks, Events in Box field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Consolidate SaaS data alongside lake data so analysts join both through one SQL surface.
  • 02 Load CRM and ERP records into Synapse dedicated SQL pool tables for enterprise reporting.
  • 03 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
  • 04 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.

Common sync patterns

Where Box holds the file inventory: make it queryable

The catalog of documents, owners, and folders in Box appears as SQL pools, Tables (dedicated SQL pool), External tables, Views in Azure Synapse Analytics, so file metadata can be joined against the rest of your data and reported on.

Where Azure Synapse Analytics computes the labels: push them onto the files

Classifications, scores, or status derived in Azure Synapse Analytics are written back onto the matching Users, Groups, Tasks, Events in Box as metadata or tags, so the file store reflects what analytics decided.

Where Box receives the raw files: land them as query-ready rows

Files and exports that arrive in Box are parsed into SQL pools, Tables (dedicated SQL pool), External tables, Views in Azure Synapse Analytics as they land, so analysts query current data instead of waiting on the next scheduled load.

What you can sync between Azure Synapse Analytics and Box

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.

Azure Synapse Analytics objects Box objects How this pairing syncs
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. 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. SQL pools is specific to Azure Synapse Analytics and Events to Box — each maps to any object or custom field on the other side.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. 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. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Files to Box — each maps to any object or custom field on the other side.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. 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. External tables is specific to Azure Synapse Analytics and Folders to Box — each maps to any object or custom field on the other side.
Views Curated projections used when downstream tools should not read base tables directly. Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Views is specific to Azure Synapse Analytics and Metadata to Box — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. 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. Schemas is specific to Azure Synapse Analytics and Collaborations to Box — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Materialized views is specific to Azure Synapse Analytics and Users to Box — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics and Box

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.

Azure Synapse Analytics Box Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.

Box Azure Synapse Analytics 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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

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 Azure Synapse Analytics ⇄ Box

Connect Azure Synapse Analytics and Box for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Box connection.

Real-time

Two-way sync

Changes in Azure Synapse Analytics or Box instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Synapse Analytics or Box 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 Azure Synapse Analytics or Box record.

Observability

Monitoring

Track your Azure Synapse Analytics ⇄ Box sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Box.

How the Azure Synapse Analytics and Box connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

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.
How it works

How to connect Azure Synapse Analytics to Box — 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 Azure Synapse Analytics and Box 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
    Azure Synapse Analytics connected
    Box connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics and Box 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 · Azure Synapse Analytics ⇄ Box
    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
    Azure Synapse Analytics Box
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Synapse Analytics and Box 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 532 integrations available for Azure Synapse Analytics and Box.

Popular · 7 of 532
All Azure Synapse Analytics integrations All Box 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