Skip to content
Developer tools

Connect Azure Service Bus to any app with two-way sync.

Two-way sync Azure Service Bus across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Azure Service Bus.

These objects sync between Azure Service Bus and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Azure Service Bus exposes them.

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.
Topics
Publish/subscribe entity a publisher sends to; each message is fanned out to every subscription whose filter rules match, so many consumers get their own copy.
Subscriptions
A virtual queue attached to a topic; a consumer receives its own stream of matching messages here, independent of other subscriptions on the same topic.
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.
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.
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.
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.
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.
API surface

How Stacksync connects to Azure Service Bus.

The connector runs on Azure Service Bus's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Not available
What ships with Azure Service Bus

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

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every connection.

Real-time

Two-way sync

Changes in Azure Service Bus instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your 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.

Use cases

What teams run on the Azure Service Bus connector.

Azure Service Bus is Microsoft's enterprise message broker on Azure, owned by platform, integration, and backend engineering teams. It is a system of engagement and event bus, not a system of record: publishers send order events, workflow commands, and service-to-service messages to queues and topics, and consumers receive them independently. Messages are in-flight and transient - held until completed, expired by TTL, or dead-lettered - so it decouples producers from consumers and smooths load between .NET and other enterprise systems rather than storing state long term.

  • Platform engineering
  • Integration / middleware engineers
  • Backend application engineers
  • DevOps / SRE
  • Enterprise .NET architects

  1. Send new and changed database rows as messages to a Service Bus queue or topic so multiple downstream consumers process the change stream independently.

  2. Receive messages from a queue or subscription with an AMQP receiver and write them into a Postgres or warehouse table for durable, SQL-queryable storage.

  3. Fan out CRM or ERP record changes to a topic and let billing, analytics, and notification subscriptions each filter with SQL rules and react without coupling to the source.

  4. Bridge order or workflow events off a subscription into an ERP or ticketing system as they arrive, mapping message properties and the payload to target fields.

  5. Preserve per-account or per-order processing order by grouping related messages into a session so a single consumer handles them in FIFO sequence.

  6. One-way out: Stacksync reads new and changed rows from a database or a CRM such as Salesforce and sends them as messages to a Service Bus queue or topic, so downstream services consume the change stream without querying the source system directly.

All Azure Service Bus integrations

Pick the system you need to keep in sync with Azure Service Bus. Each page covers the sync setup, field mapping, and common workflows for that pair.

Database · 50

Data warehouse · 28

Business productivity · 37

How it works

Set up Azure Service Bus in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Service Bus objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Azure Service Bus connector FAQ

What can I sync with the Azure Service Bus connector?

Azure Service Bus's core objects — Queues, Topics, Subscriptions, Messages and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Azure Service Bus?

Via AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported), authenticated with 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. Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Azure Service Bus connector two-way?

Yes. Changes made in Azure Service Bus propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does an Azure Service Bus integration take to set up?

Most Azure Service Bus integrations go live in minutes: authenticate Azure Service Bus and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Azure Service Bus data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Azure Service Bus data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
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