Skip to content
Developer tools ⇄ Data warehouse

Azure Service Bus to BigQuery integration — real-time, two-way sync

Keep Azure Service Bus and BigQuery 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 Service Bus and BigQuery

Close the gap between analytics and operations: BigQuery holds the record while Azure Service Bus runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

BigQuery is the central store where teams keep Datasets, Projects, Tables, Partitioned tables for reporting and analysis; Azure Service Bus runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Dead-letter queue, Scheduled / deferred messages, Queues, Topics produced in Azure Service Bus are exactly what analysts want to measure in BigQuery, and the curated rows in BigQuery are what should drive the next action in Azure Service Bus. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Datasets, Projects, Tables, Partitioned tables in BigQuery with Dead-letter queue, Scheduled / deferred messages, Queues, Topics in Azure Service Bus field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • 02 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 03 Preserve per-account or per-order processing order by grouping related messages into a session so a single consumer handles them in FIFO sequence.
  • 04 Send new and changed database rows as messages to a Service Bus queue or topic so multiple downstream consumers process the change stream independently.

Common sync patterns

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where Azure Service Bus manages users, directory, or access data, those records stay current in BigQuery — and can be provisioned back from it — so ownership and permissions match across both.

What you can sync between Azure Service Bus and BigQuery

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 Service Bus objects BigQuery objects How this pairing syncs
Messages The synced unit: a body plus system and user properties, MessageId, SessionId, and TTL; capped at 256 KB on Standard and up to 100 MB on Premium over AMQP. Partitioned tables Synced like regular tables; partition columns map to target fields. Messages is specific to Azure Service Bus and Partitioned tables to BigQuery — each maps to any object or custom field on the other side.
Rules / Filters SQL or correlation filters on a subscription that decide which topic messages it receives; a rule can also add or modify properties via a filter action. Clustered tables Supported; clustering is transparent to the sync. Rules / Filters is specific to Azure Service Bus and Clustered tables to BigQuery — each maps to any object or custom field on the other side.
Sessions Message sessions group related messages by SessionId so one consumer handles them in FIFO order; the way ordered processing is achieved in Service Bus. Datasets Organizational container — you pick which dataset’s tables to sync. Sessions is specific to Azure Service Bus and Datasets to BigQuery — each maps to any object or custom field on the other side.
Dead-letter queue A sub-queue on every queue and subscription that automatically holds messages exceeding the max delivery count or their TTL, read for inspection and reprocessing. Projects Connection scope: the service account grants access per project. Dead-letter queue is specific to Azure Service Bus and Projects to BigQuery — each maps to any object or custom field on the other side.
Scheduled / deferred messages Messages enqueued for future delivery at a set time, or deferred and set aside by sequence number for retrieval later, out of the normal receive order. Tables The syncable unit: only tables can be synced per the Stacksync docs. Scheduled / deferred messages is specific to Azure Service Bus and Tables to BigQuery — each maps to any object or custom field on the other side.

How changes propagate between Azure Service Bus and BigQuery

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 Service Bus BigQuery Interval-based propagation

DetectionStacksync polls Azure Service Bus for changes on an incremental schedule, reading only records changed since the previous pass. Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or.

DeliveryEach detected change is applied to BigQuery as a row-level write, with types converted between the two schemas.

BigQuery Azure Service Bus Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

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

Rate-limit considerations

  • Azure Service Bus: Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity.
  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
What ships with Azure Service Bus ⇄ BigQuery

Connect Azure Service Bus and BigQuery for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Service Bus–BigQuery connection.

Real-time

Two-way sync

Changes in Azure Service Bus or BigQuery instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Service Bus or BigQuery 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 Service Bus or BigQuery record.

Observability

Monitoring

Track your Azure Service Bus ⇄ BigQuery sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Service Bus and BigQuery.

How the Azure Service Bus and BigQuery connectors work

Azure Service Bus

Integration surface
AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported)
Authentication
Microsoft Entra ID (Azure AD) RBAC with managed identities - roles Azure Service Bus Data Owner, Data Sender, and Data Receiver - or Shared Access Signature (SAS) policies scoped with Manage, Send, and Listen claims
Change detection
Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or ReceiveAndDelete. No modified-date polling and no native HTTP push; Azure Event Grid can separately raise an 'active messages available' event for intermittent receivers
Capabilities
read · write
Rate limits
Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide
How it works

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

    Choose tables

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

Azure Service Bus and BigQuery 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 421 integrations available for Azure Service Bus and BigQuery.

Popular · 8 of 421
All Azure Service Bus integrations All BigQuery 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