Skip to content
Database ⇄ Developer tools

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

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

Keep Azure Cosmos DB and Azure Service Bus in step: the rows in your database and the Sessions, Dead-letter queue, Scheduled / deferred messages, Queues your engineering tools track stay consistent in real time, in both directions.

Azure Cosmos DB is where your application's durable data lives; Azure Service Bus is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Stored procedures and triggers, Databases, Containers, Items (JSON documents) in Azure Cosmos DB with Sessions, Dead-letter queue, Scheduled / deferred messages, Queues in Azure Service Bus 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, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 02 Consolidate documents from multiple containers into a single reporting store.
  • 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

React to changes on either side in near real time

Updates in Azure Service Bus arrive as row changes in Azure Cosmos DB, and writes to Azure Cosmos DB propagate to Azure Service Bus within seconds, so triggers, jobs, and alerts fire without polling.

Where Azure Service Bus manages users or groups: keep identity aligned

Directory and identity records in Azure Service Bus stay matched to the users or owners table in Azure Cosmos DB, so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in Azure Cosmos DB creates or updates the matching record in Azure Service Bus, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

What you can sync between Azure Cosmos DB and Azure Service Bus

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 Cosmos DB objects Azure Service Bus objects How this pairing syncs
Containers The unit of partitioning and throughput; each container maps to a synced collection. 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. Containers is specific to Azure Cosmos DB and Messages to Azure Service Bus — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. 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. Items (JSON documents) is specific to Azure Cosmos DB and Rules / Filters to Azure Service Bus — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. 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. Partition keys is specific to Azure Cosmos DB and Sessions to Azure Service Bus — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. 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. Change feed entries is specific to Azure Cosmos DB and Dead-letter queue to Azure Service Bus — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. 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. Stored procedures and triggers is specific to Azure Cosmos DB and Scheduled / deferred messages to Azure Service Bus — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Queues Point-to-point entity: a sender writes messages and one competing consumer at a time receives them under PeekLock, then completes or abandons each message. Databases is specific to Azure Cosmos DB and Queues to Azure Service Bus — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Azure Service Bus

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 Cosmos DB Azure Service Bus Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

Azure Service Bus Azure Cosmos DB 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 Azure Cosmos DB as a row-level write, with types converted between the two schemas.

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.
What ships with Azure Cosmos DB ⇄ Azure Service Bus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Azure Cosmos DB and Azure Service Bus connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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

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

    Choose tables

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

Azure Cosmos DB and Azure Service Bus 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 317 integrations available for Azure Cosmos DB and Azure Service Bus.

Popular · 8 of 317
All Azure Cosmos DB integrations All Azure Service Bus 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