--- title: "Azure Service Bus connector | Stacksync" description: "Azure Service Bus integration guide: plan Messages, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/azure-service-bus last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # Azure Service Bus integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Azure Service Bus workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Messages. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Queues** - **Topics** - **Subscriptions** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=azure-service-bus) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Azure Service Bus records to discuss. These Azure Service Bus record examples help scope a technical review. They are not a list of verified Stacksync operations. Queues Identify this record type and the operation you need to review with Stacksync. Topics Identify this record type and the operation you need to review with Stacksync. Subscriptions Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Messages Retain message ID, conversation/thread ID, channel, and sender identity. Rules / Filters Identify this record type and the operation you need to review with Stacksync. Sessions Identify this record type and the operation you need to review with Stacksync. Connection setup ## Azure Service Bus connection requirements. Review Azure Service Bus access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Azure Service Bus account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Azure Service Bus, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Azure Service Bus integration. Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Azure Service Bus **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Retain message ID, conversation/thread ID, channel, and sender identity. Load related records in the right order Resolve conversation, participant, and customer context before associating messages. ### Mapping checks by record type #### Messages Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Azure Service Bus integration in four steps. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### View the four setup tests and expected results 1. ### Verify Azure Service Bus credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Messages Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. **Expected result:** A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. 3. ### Test the operation your workflow needs Review one Azure Service Bus record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Azure Service Bus integration. ### Diagnose record matching, delayed changes, and rejected operations A Azure Service Bus record appears under the wrong destination record Retain message ID, conversation/thread ID, channel, and sender identity. Resolve conversation, participant, and customer context before associating messages. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Azure Service Bus implementation’s change-detection method for Messages. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Azure Service Bus object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Azure Service Bus workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=azure-service-bus) ## Azure Service Bus integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Azure Service Bus connector FAQ ### How should I plan an integration with Azure Service Bus? Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Azure Service Bus connector write changes back? Write-back support is not established for this connection. Review the Azure Service Bus records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Azure Service Bus data? Retain message ID, conversation/thread ID, channel, and sender identity. ### Which related records should I load first for Azure Service Bus? Resolve conversation, participant, and customer context before associating messages. ### How do I validate Azure Service Bus changes after the initial load? Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### What will we cover in a Azure Service Bus integration demo? Start with one workflow and a sample record from Messages. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Azure Service Bus from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Azure Service Bus and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Azure Service Bus. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Azure Service Bus record changes.” - “Create a Genie that answers questions about our Azure Service Bus data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Azure Service Bus connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Azure Service Bus and Microsoft Dynamics 365](https://www.stacksync.com/integrations/azure-service-bus-and-microsoft-dynamics-365) - [Azure Service Bus and RingCentral](https://www.stacksync.com/integrations/azure-service-bus-and-ringcentral) - [Azure Service Bus and Rockset](https://www.stacksync.com/integrations/azure-service-bus-and-rockset) - [Azure Service Bus and SQL Server](https://www.stacksync.com/integrations/azure-service-bus-and-sql-server) - [Azure Service Bus and Elasticsearch](https://www.stacksync.com/integrations/azure-service-bus-and-elasticsearch) - [Azure Service Bus and PostgreSQL](https://www.stacksync.com/integrations/azure-service-bus-and-postgresql) - [Azure Service Bus and Azure SQL Database](https://www.stacksync.com/integrations/azure-service-bus-and-azure-sql-database) - [Azure Service Bus and SharePoint](https://www.stacksync.com/integrations/azure-service-bus-and-sharepoint) ### Database · 50 - [Azure Service Bus and Airtable](https://www.stacksync.com/integrations/airtable-and-azure-service-bus) - [Azure Service Bus and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-azure-service-bus) - [Azure Service Bus and Amazon DynamoDB](https://www.stacksync.com/integrations/azure-service-bus-and-dynamo-db) - [Azure Service Bus and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-azure-service-bus) - [Azure Service Bus and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-azure-service-bus) - [Azure Service Bus and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-azure-service-bus) - [Azure Service Bus and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-azure-service-bus) - [Azure Service Bus and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-azure-service-bus) - [Azure Service Bus and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-azure-service-bus) - [Azure Service Bus and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-azure-service-bus) - [Azure Service Bus and Azure SQL Database](https://www.stacksync.com/integrations/azure-service-bus-and-azure-sql-database) - [Azure Service Bus and Citus](https://www.stacksync.com/integrations/azure-service-bus-and-citus) - [Azure Service Bus and CockroachDB](https://www.stacksync.com/integrations/azure-service-bus-and-cockroachdb) - [Azure Service Bus and Couchbase](https://www.stacksync.com/integrations/azure-service-bus-and-couchbase) - [Azure Service Bus and DuckDB](https://www.stacksync.com/integrations/azure-service-bus-and-duckdb) - [Azure Service Bus and Elasticsearch](https://www.stacksync.com/integrations/azure-service-bus-and-elasticsearch) - [Azure Service Bus and Firebase](https://www.stacksync.com/integrations/azure-service-bus-and-firebase) - [Azure Service Bus and Google AlloyDB](https://www.stacksync.com/integrations/azure-service-bus-and-google-alloydb) - [Azure Service Bus and Google Cloud Spanner](https://www.stacksync.com/integrations/azure-service-bus-and-google-cloud-spanner) - [Azure Service Bus and Google Cloud SQL](https://www.stacksync.com/integrations/azure-service-bus-and-google-cloud-sql) - [Azure Service Bus and IBM AS/400](https://www.stacksync.com/integrations/azure-service-bus-and-ibm-as400) - [Azure Service Bus and IBM Db2](https://www.stacksync.com/integrations/azure-service-bus-and-ibm-db2) - [Azure Service Bus and IBM Informix](https://www.stacksync.com/integrations/azure-service-bus-and-ibm-informix) - [Azure Service Bus and InfluxDB](https://www.stacksync.com/integrations/azure-service-bus-and-influxdb) - [Azure Service Bus and InterSystems IRIS](https://www.stacksync.com/integrations/azure-service-bus-and-intersystems-iris) - [Azure Service Bus and JDBC](https://www.stacksync.com/integrations/azure-service-bus-and-jdbc) - [Azure Service Bus and MariaDB](https://www.stacksync.com/integrations/azure-service-bus-and-mariadb) - [Azure Service Bus and MarkLogic](https://www.stacksync.com/integrations/azure-service-bus-and-marklogic) - [Azure Service Bus and MongoDB](https://www.stacksync.com/integrations/azure-service-bus-and-mongodb) - [Azure Service Bus and MySQL](https://www.stacksync.com/integrations/azure-service-bus-and-mysql) - [Azure Service Bus and Neo4j](https://www.stacksync.com/integrations/azure-service-bus-and-neo4j) - [Azure Service Bus and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/azure-service-bus-and-oci-database) - [Azure Service Bus and OpenSearch](https://www.stacksync.com/integrations/azure-service-bus-and-opensearch) - [Azure Service Bus and Oracle DB](https://www.stacksync.com/integrations/azure-service-bus-and-oracle-db) - [Azure Service Bus and Postgres Heroku](https://www.stacksync.com/integrations/azure-service-bus-and-postgres-heroku) - [Azure Service Bus and PostgreSQL](https://www.stacksync.com/integrations/azure-service-bus-and-postgresql) - [Azure Service Bus and RavenDB](https://www.stacksync.com/integrations/azure-service-bus-and-ravendb) - [Azure Service Bus and Redis Enterprise](https://www.stacksync.com/integrations/azure-service-bus-and-redis-enterprise) - [Azure Service Bus and Reltio](https://www.stacksync.com/integrations/azure-service-bus-and-reltio) - [Azure Service Bus and Render Postgres](https://www.stacksync.com/integrations/azure-service-bus-and-render-postgres) - [Azure Service Bus and SAP ASE (Sybase)](https://www.stacksync.com/integrations/azure-service-bus-and-sap-ase-sybase) - [Azure Service Bus and SAP HANA](https://www.stacksync.com/integrations/azure-service-bus-and-sap-hana) - [Azure Service Bus and Scaleway Postgres](https://www.stacksync.com/integrations/azure-service-bus-and-scaleway-postgres) - [Azure Service Bus and SingleStore](https://www.stacksync.com/integrations/azure-service-bus-and-singlestore) - [Azure Service Bus and SQL Server](https://www.stacksync.com/integrations/azure-service-bus-and-sql-server) - [Azure Service Bus and Supabase](https://www.stacksync.com/integrations/azure-service-bus-and-supabase) - [Azure Service Bus and TiDB](https://www.stacksync.com/integrations/azure-service-bus-and-tidb) - [Azure Service Bus and TimescaleDB](https://www.stacksync.com/integrations/azure-service-bus-and-timescaledb) - [Azure Service Bus and VoltDB](https://www.stacksync.com/integrations/azure-service-bus-and-voltdb) - [Azure Service Bus and YugabyteDB](https://www.stacksync.com/integrations/azure-service-bus-and-yugabytedb) ### Data warehouse · 28 - [Azure Service Bus and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-azure-service-bus) - [Azure Service Bus and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-azure-service-bus) - [Azure Service Bus and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-azure-service-bus) - [Azure Service Bus and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-azure-service-bus) - [Azure Service Bus and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-azure-service-bus) - [Azure Service Bus and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-azure-service-bus) - [Azure Service Bus and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-azure-service-bus) - [Azure Service Bus and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-service-bus-and-azure-synapse-analytics) - [Azure Service Bus and BigQuery](https://www.stacksync.com/integrations/azure-service-bus-and-bigquery) - [Azure Service Bus and ClickHouse](https://www.stacksync.com/integrations/azure-service-bus-and-clickhouse) - [Azure Service Bus and Cloudera Data Platform](https://www.stacksync.com/integrations/azure-service-bus-and-cloudera-data-platform) - [Azure Service Bus and Databricks](https://www.stacksync.com/integrations/azure-service-bus-and-databricks) - [Azure Service Bus and Dremio](https://www.stacksync.com/integrations/azure-service-bus-and-dremio) - [Azure Service Bus and Exasol](https://www.stacksync.com/integrations/azure-service-bus-and-exasol) - [Azure Service Bus and Firebolt](https://www.stacksync.com/integrations/azure-service-bus-and-firebolt) - [Azure Service Bus and Google Cloud Platform](https://www.stacksync.com/integrations/azure-service-bus-and-google-cloud-platform) - [Azure Service Bus and Greenplum](https://www.stacksync.com/integrations/azure-service-bus-and-greenplum) - [Azure Service Bus and IBM Netezza](https://www.stacksync.com/integrations/azure-service-bus-and-ibm-netezza) - [Azure Service Bus and Materialize](https://www.stacksync.com/integrations/azure-service-bus-and-materialize) - [Azure Service Bus and MotherDuck](https://www.stacksync.com/integrations/azure-service-bus-and-motherduck) - [Azure Service Bus and Rockset](https://www.stacksync.com/integrations/azure-service-bus-and-rockset) - [Azure Service Bus and Snowflake](https://www.stacksync.com/integrations/azure-service-bus-and-snowflake) - [Azure Service Bus and Starburst Enterprise](https://www.stacksync.com/integrations/azure-service-bus-and-starburst-enterprise) - [Azure Service Bus and StarRocks](https://www.stacksync.com/integrations/azure-service-bus-and-starrocks) - [Azure Service Bus and Teradata Vantage](https://www.stacksync.com/integrations/azure-service-bus-and-teradata-vantage) - [Azure Service Bus and Tinybird](https://www.stacksync.com/integrations/azure-service-bus-and-tinybird) - [Azure Service Bus and Vertica](https://www.stacksync.com/integrations/azure-service-bus-and-vertica) - [Azure Service Bus and Yellowbrick](https://www.stacksync.com/integrations/azure-service-bus-and-yellowbrick) ### Business productivity · 37 - [Azure Service Bus and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-azure-service-bus) - [Azure Service Bus and Agiloft](https://www.stacksync.com/integrations/agiloft-and-azure-service-bus) - [Azure Service Bus and Asana](https://www.stacksync.com/integrations/asana-and-azure-service-bus) - [Azure Service Bus and Atlassian](https://www.stacksync.com/integrations/atlassian-and-azure-service-bus) - [Azure Service Bus and Braze](https://www.stacksync.com/integrations/azure-service-bus-and-braze) - [Azure Service Bus and Campfire](https://www.stacksync.com/integrations/azure-service-bus-and-campfire) - [Azure Service Bus and ConnectWise](https://www.stacksync.com/integrations/azure-service-bus-and-connectwise) - [Azure Service Bus and Customer.io](https://www.stacksync.com/integrations/azure-service-bus-and-customer-io) - [Azure Service Bus and Docusign](https://www.stacksync.com/integrations/azure-service-bus-and-docusign) - [Azure Service Bus and eClinicalWorks](https://www.stacksync.com/integrations/azure-service-bus-and-eclinicalworks) - [Azure Service Bus and Front](https://www.stacksync.com/integrations/azure-service-bus-and-front) - [Azure Service Bus and FullEnrich](https://www.stacksync.com/integrations/azure-service-bus-and-full-enrich) - [Azure Service Bus and Gainsight](https://www.stacksync.com/integrations/azure-service-bus-and-gainsight) - [Azure Service Bus and Gatekeeper](https://www.stacksync.com/integrations/azure-service-bus-and-gatekeeper) - [Azure Service Bus and GitHub](https://www.stacksync.com/integrations/azure-service-bus-and-github) - [Azure Service Bus and Google Sheets](https://www.stacksync.com/integrations/azure-service-bus-and-google-sheets) - [Azure Service Bus and Ironclad](https://www.stacksync.com/integrations/azure-service-bus-and-ironclad) - [Azure Service Bus and Klaviyo](https://www.stacksync.com/integrations/azure-service-bus-and-klaviyo) - [Azure Service Bus and Lemlist](https://www.stacksync.com/integrations/azure-service-bus-and-lemlist) - [Azure Service Bus and Microsoft 365](https://www.stacksync.com/integrations/azure-service-bus-and-microsoft-365) - [Azure Service Bus and Microsoft Dynamics 365](https://www.stacksync.com/integrations/azure-service-bus-and-microsoft-dynamics-365) - [Azure Service Bus and Microsoft Teams](https://www.stacksync.com/integrations/azure-service-bus-and-microsoft-teams) - [Azure Service Bus and Monday](https://www.stacksync.com/integrations/azure-service-bus-and-monday) - [Azure Service Bus and NextGen Healthcare](https://www.stacksync.com/integrations/azure-service-bus-and-nextgen-healthcare) - [Azure Service Bus and Notion](https://www.stacksync.com/integrations/azure-service-bus-and-notion) - [Azure Service Bus and Orderful](https://www.stacksync.com/integrations/azure-service-bus-and-orderful) - [Azure Service Bus and Quip](https://www.stacksync.com/integrations/azure-service-bus-and-quip) - [Azure Service Bus and Resend](https://www.stacksync.com/integrations/azure-service-bus-and-resend) - [Azure Service Bus and SendGrid](https://www.stacksync.com/integrations/azure-service-bus-and-sendgrid) - [Azure Service Bus and ServiceMax](https://www.stacksync.com/integrations/azure-service-bus-and-servicemax) - [Azure Service Bus and ServiceNow](https://www.stacksync.com/integrations/azure-service-bus-and-servicenow) - [Azure Service Bus and Slack](https://www.stacksync.com/integrations/azure-service-bus-and-slack) - [Azure Service Bus and Smartsheet](https://www.stacksync.com/integrations/azure-service-bus-and-smartsheet) - [Azure Service Bus and SysAid](https://www.stacksync.com/integrations/azure-service-bus-and-sysaid) - [Azure Service Bus and Twilio](https://www.stacksync.com/integrations/azure-service-bus-and-twilio) - [Azure Service Bus and Wrike](https://www.stacksync.com/integrations/azure-service-bus-and-wrike) - [Azure Service Bus and Zendesk](https://www.stacksync.com/integrations/azure-service-bus-and-zendesk) ### Analytics · 3 - [Azure Service Bus and Pendo](https://www.stacksync.com/integrations/azure-service-bus-and-pendo) - [Azure Service Bus and Splunk](https://www.stacksync.com/integrations/azure-service-bus-and-splunk) - [Azure Service Bus and Treasure Data](https://www.stacksync.com/integrations/azure-service-bus-and-treasuredata) ### Communications · 5 - [Azure Service Bus and Aircall](https://www.stacksync.com/integrations/aircall-and-azure-service-bus) - [Azure Service Bus and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-azure-service-bus) - [Azure Service Bus and Infobip](https://www.stacksync.com/integrations/azure-service-bus-and-infobip) - [Azure Service Bus and RingCentral](https://www.stacksync.com/integrations/azure-service-bus-and-ringcentral) - [Azure Service Bus and Zoom](https://www.stacksync.com/integrations/azure-service-bus-and-zoom) ### Security and identity · 6 - [Azure Service Bus and Active Directory](https://www.stacksync.com/integrations/active-directory-and-azure-service-bus) - [Azure Service Bus and Auth0](https://www.stacksync.com/integrations/auth0-and-azure-service-bus) - [Azure Service Bus and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-azure-service-bus) - [Azure Service Bus and JumpCloud](https://www.stacksync.com/integrations/azure-service-bus-and-jumpcloud) - [Azure Service Bus and Okta](https://www.stacksync.com/integrations/azure-service-bus-and-okta) - [Azure Service Bus and OneLogin](https://www.stacksync.com/integrations/azure-service-bus-and-onelogin) ### Storage · 4 - [Azure Service Bus and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-azure-service-bus) - [Azure Service Bus and Box](https://www.stacksync.com/integrations/azure-service-bus-and-box) - [Azure Service Bus and Egnyte](https://www.stacksync.com/integrations/azure-service-bus-and-egnyte) - [Azure Service Bus and SharePoint](https://www.stacksync.com/integrations/azure-service-bus-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)