--- title: "Azure Cosmos DB connector | Stacksync" description: "Azure Cosmos DB integration guide: plan Items (JSON documents), record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/azure-cosmos-db last_modified: 2026-09-15 --- Database · Two-way sync platform # Azure Cosmos DB 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 Cosmos DB workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Items (JSON documents). 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. - **Databases** - **Containers** - **Items (JSON documents)** **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-cosmos-db) ## 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 Cosmos DB records to discuss. These Azure Cosmos DB record examples help scope a technical review. They are not a list of verified Stacksync operations. Databases Identify this record type and the operation you need to review with Stacksync. Containers Identify this record type and the operation you need to review with Stacksync. Items (JSON documents) Keep file/object ID, container, and version. A path can change and a filename can repeat. ### See 3 more record examples Partition keys Identify this record type and the operation you need to review with Stacksync. Change feed entries Identify this record type and the operation you need to review with Stacksync. Stored procedures and triggers Identify this record type and the operation you need to review with Stacksync. Connection setup ## Azure Cosmos DB connection requirements. Review Azure Cosmos DB 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 Cosmos DB account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Azure Cosmos DB, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Azure Cosmos DB integration. Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. 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 Cosmos DB **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 Keep file/object ID, container, and version. A path can change and a filename can repeat. Load related records in the right order Resolve folder/container and parent-record references before attaching metadata. ### Mapping checks by record type #### Items (JSON documents) Confirm object support with Stacksync Identity Keep file/object ID, container, and version. A path can change and a filename can repeat. Fields to consider Source file ID · Container reference · Version · Metadata · Access classification Related records to resolve first Resolve folder/container and parent-record references before attaching metadata. Test before going live Test a renamed file, a new version, a moved folder, and an access-restricted document. [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 Cosmos DB integration in four steps. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### View the four setup tests and expected results 1. ### Verify Azure Cosmos DB connectivity and database privileges After confirming an implementation path, validate the selected access method from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture. **Expected result:** The approved role can access the selected data and capture later changes without depending on an administrator’s personal session. 2. ### Test record matching for Items (JSON documents) Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed file, a new version, a moved folder, and an access-restricted document. **Expected result:** Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. 3. ### Test the operation your workflow needs Review one Azure Cosmos DB 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 Cosmos DB integration. ### Diagnose record matching, delayed changes, and rejected operations A Azure Cosmos DB record appears under the wrong destination record Keep file/object ID, container, and version. A path can change and a filename can repeat. Resolve folder/container and parent-record references before attaching metadata. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Azure Cosmos DB implementation’s change-detection method for Items (JSON documents). 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 Cosmos DB 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 Cosmos DB workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=azure-cosmos-db) ## Azure Cosmos DB 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 Cosmos DB connector FAQ ### How should I plan an integration with Azure Cosmos DB? Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. 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 Cosmos DB connector write changes back? Write-back support is not established for this connection. Review the Azure Cosmos DB 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 Cosmos DB data? Keep file/object ID, container, and version. A path can change and a filename can repeat. ### Which related records should I load first for Azure Cosmos DB? Resolve folder/container and parent-record references before attaching metadata. ### How do I validate Azure Cosmos DB changes after the initial load? Test a renamed file, a new version, a moved folder, and an access-restricted document. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### What will we cover in a Azure Cosmos DB integration demo? Start with one workflow and a sample record from Items (JSON documents). 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 Cosmos DB 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 Cosmos DB and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Azure Cosmos DB. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Azure Cosmos DB record changes.” - “Create a Genie that answers questions about our Azure Cosmos DB 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 Cosmos DB 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 Cosmos DB and Databricks](https://www.stacksync.com/integrations/azure-cosmos-db-and-databricks) - [Azure Cosmos DB and RingCentral](https://www.stacksync.com/integrations/azure-cosmos-db-and-ringcentral) - [Azure Cosmos DB and Snowflake](https://www.stacksync.com/integrations/azure-cosmos-db-and-snowflake) - [Azure Cosmos DB and Google Cloud Spanner](https://www.stacksync.com/integrations/azure-cosmos-db-and-google-cloud-spanner) - [Azure Cosmos DB and Datadog](https://www.stacksync.com/integrations/azure-cosmos-db-and-datadog) - [Azure Cosmos DB and ClickHouse](https://www.stacksync.com/integrations/azure-cosmos-db-and-clickhouse) - [Azure Cosmos DB and SharePoint](https://www.stacksync.com/integrations/azure-cosmos-db-and-sharepoint) - [Aircall and Azure Cosmos DB](https://www.stacksync.com/integrations/aircall-and-azure-cosmos-db) ### CRM · 31 - [Azure Cosmos DB and 6sense](https://www.stacksync.com/integrations/6sense-and-azure-cosmos-db) - [Azure Cosmos DB and Affinity](https://www.stacksync.com/integrations/affinity-and-azure-cosmos-db) - [Azure Cosmos DB and Attio](https://www.stacksync.com/integrations/attio-and-azure-cosmos-db) - [Azure Cosmos DB and Chorusai](https://www.stacksync.com/integrations/azure-cosmos-db-and-chorusai) - [Azure Cosmos DB and Clearbit](https://www.stacksync.com/integrations/azure-cosmos-db-and-clearbit) - [Azure Cosmos DB and Close](https://www.stacksync.com/integrations/azure-cosmos-db-and-close) - [Azure Cosmos DB and Copper CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-copper-crm) - [Azure Cosmos DB and Dun & Bradstreet](https://www.stacksync.com/integrations/azure-cosmos-db-and-dun-bradstreet) - [Azure Cosmos DB and Freshsales](https://www.stacksync.com/integrations/azure-cosmos-db-and-freshsales) - [Azure Cosmos DB and Freshworks CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-freshworks-crm) - [Azure Cosmos DB and Gong](https://www.stacksync.com/integrations/azure-cosmos-db-and-gong) - [Azure Cosmos DB and Gorgias](https://www.stacksync.com/integrations/azure-cosmos-db-and-gorgias) - [Azure Cosmos DB and HubSpot](https://www.stacksync.com/integrations/azure-cosmos-db-and-hubspot) - [Azure Cosmos DB and Infor CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-infor-crm) - [Azure Cosmos DB and Insightly](https://www.stacksync.com/integrations/azure-cosmos-db-and-insightly) - [Azure Cosmos DB and Intercom](https://www.stacksync.com/integrations/azure-cosmos-db-and-intercom) - [Azure Cosmos DB and Kommo](https://www.stacksync.com/integrations/azure-cosmos-db-and-kommo) - [Azure Cosmos DB and Outreach](https://www.stacksync.com/integrations/azure-cosmos-db-and-outreach) - [Azure Cosmos DB and Pipedrive](https://www.stacksync.com/integrations/azure-cosmos-db-and-pipedrive) - [Azure Cosmos DB and Salesforce](https://www.stacksync.com/integrations/azure-cosmos-db-and-salesforce) - [Azure Cosmos DB and Salesloft](https://www.stacksync.com/integrations/azure-cosmos-db-and-salesloft) - [Azure Cosmos DB and SAP Sales Cloud](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-sales-cloud) - [Azure Cosmos DB and Seismic](https://www.stacksync.com/integrations/azure-cosmos-db-and-seismic) - [Azure Cosmos DB and Shopify](https://www.stacksync.com/integrations/azure-cosmos-db-and-shopify) - [Azure Cosmos DB and SugarCRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-sugarcrm) - [Azure Cosmos DB and Veeva CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-veeva-crm) - [Azure Cosmos DB and Vtiger CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-vtiger-crm) - [Azure Cosmos DB and Xactly](https://www.stacksync.com/integrations/azure-cosmos-db-and-xactly) - [Azure Cosmos DB and Zoho CRM](https://www.stacksync.com/integrations/azure-cosmos-db-and-zoho-crm) - [Azure Cosmos DB and Zoho SalesIQ](https://www.stacksync.com/integrations/azure-cosmos-db-and-zoho-salesiq) - [Azure Cosmos DB and ZoomInfo](https://www.stacksync.com/integrations/azure-cosmos-db-and-zoominfo) ### ERP · 24 - [Azure Cosmos DB and Acumatica](https://www.stacksync.com/integrations/acumatica-and-azure-cosmos-db) - [Azure Cosmos DB and Brightpearl](https://www.stacksync.com/integrations/azure-cosmos-db-and-brightpearl) - [Azure Cosmos DB and Cin7](https://www.stacksync.com/integrations/azure-cosmos-db-and-cin7) - [Azure Cosmos DB and Dynamics 365 Business Central](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-dynamics-365-business-central) - [Azure Cosmos DB and Epicor ERP](https://www.stacksync.com/integrations/azure-cosmos-db-and-epicor-erp) - [Azure Cosmos DB and Infor LN](https://www.stacksync.com/integrations/azure-cosmos-db-and-infor-ln) - [Azure Cosmos DB and Infor M3](https://www.stacksync.com/integrations/azure-cosmos-db-and-infor-m3) - [Azure Cosmos DB and Linnworks](https://www.stacksync.com/integrations/azure-cosmos-db-and-linnworks) - [Azure Cosmos DB and Microsoft Dynamics GP](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-dynamics-gp) - [Azure Cosmos DB and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-dynamics-nav) - [Azure Cosmos DB and NetSuite](https://www.stacksync.com/integrations/azure-cosmos-db-and-netsuite) - [Azure Cosmos DB and Odoo](https://www.stacksync.com/integrations/azure-cosmos-db-and-odoo) - [Azure Cosmos DB and Plex ERP](https://www.stacksync.com/integrations/azure-cosmos-db-and-plex-erp) - [Azure Cosmos DB and QAD ERP](https://www.stacksync.com/integrations/azure-cosmos-db-and-qad-erp) - [Azure Cosmos DB and Sage 100](https://www.stacksync.com/integrations/azure-cosmos-db-and-sage-100) - [Azure Cosmos DB and Sage 300](https://www.stacksync.com/integrations/azure-cosmos-db-and-sage-300) - [Azure Cosmos DB and Sage Intacct](https://www.stacksync.com/integrations/azure-cosmos-db-and-sage-intacct) - [Azure Cosmos DB and Sage X3](https://www.stacksync.com/integrations/azure-cosmos-db-and-sage-x3) - [Azure Cosmos DB and SAP](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap) - [Azure Cosmos DB and SAP Business ByDesign](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-business-bydesign) - [Azure Cosmos DB and SAP Business One](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-business-one) - [Azure Cosmos DB and SAP S/4HANA](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-s4hana) - [Azure Cosmos DB and Syspro](https://www.stacksync.com/integrations/azure-cosmos-db-and-syspro) - [Azure Cosmos DB and TikTok Shop](https://www.stacksync.com/integrations/azure-cosmos-db-and-tiktok) ### Database · 18 - [Azure Cosmos DB and Airtable](https://www.stacksync.com/integrations/airtable-and-azure-cosmos-db) - [Azure Cosmos DB and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-azure-cosmos-db) - [Azure Cosmos DB and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-azure-cosmos-db) - [Azure Cosmos DB and Elasticsearch](https://www.stacksync.com/integrations/azure-cosmos-db-and-elasticsearch) - [Azure Cosmos DB and Firebase](https://www.stacksync.com/integrations/azure-cosmos-db-and-firebase) - [Azure Cosmos DB and Google Cloud Spanner](https://www.stacksync.com/integrations/azure-cosmos-db-and-google-cloud-spanner) - [Azure Cosmos DB and InfluxDB](https://www.stacksync.com/integrations/azure-cosmos-db-and-influxdb) - [Azure Cosmos DB and InterSystems IRIS](https://www.stacksync.com/integrations/azure-cosmos-db-and-intersystems-iris) - [Azure Cosmos DB and MarkLogic](https://www.stacksync.com/integrations/azure-cosmos-db-and-marklogic) - [Azure Cosmos DB and MongoDB](https://www.stacksync.com/integrations/azure-cosmos-db-and-mongodb) - [Azure Cosmos DB and MySQL](https://www.stacksync.com/integrations/azure-cosmos-db-and-mysql) - [Azure Cosmos DB and Neo4j](https://www.stacksync.com/integrations/azure-cosmos-db-and-neo4j) - [Azure Cosmos DB and PostgreSQL](https://www.stacksync.com/integrations/azure-cosmos-db-and-postgresql) - [Azure Cosmos DB and RavenDB](https://www.stacksync.com/integrations/azure-cosmos-db-and-ravendb) - [Azure Cosmos DB and SAP ASE (Sybase)](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-ase-sybase) - [Azure Cosmos DB and SAP HANA](https://www.stacksync.com/integrations/azure-cosmos-db-and-sap-hana) - [Azure Cosmos DB and SQL Server](https://www.stacksync.com/integrations/azure-cosmos-db-and-sql-server) - [Azure Cosmos DB and Supabase](https://www.stacksync.com/integrations/azure-cosmos-db-and-supabase) ### Data warehouse · 11 - [Azure Cosmos DB and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-azure-cosmos-db) - [Azure Cosmos DB and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-azure-cosmos-db) - [Azure Cosmos DB and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-azure-cosmos-db) - [Azure Cosmos DB and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-cosmos-db-and-azure-synapse-analytics) - [Azure Cosmos DB and BigQuery](https://www.stacksync.com/integrations/azure-cosmos-db-and-bigquery) - [Azure Cosmos DB and ClickHouse](https://www.stacksync.com/integrations/azure-cosmos-db-and-clickhouse) - [Azure Cosmos DB and Databricks](https://www.stacksync.com/integrations/azure-cosmos-db-and-databricks) - [Azure Cosmos DB and Google Cloud Platform](https://www.stacksync.com/integrations/azure-cosmos-db-and-google-cloud-platform) - [Azure Cosmos DB and Rockset](https://www.stacksync.com/integrations/azure-cosmos-db-and-rockset) - [Azure Cosmos DB and Snowflake](https://www.stacksync.com/integrations/azure-cosmos-db-and-snowflake) - [Azure Cosmos DB and Vertica](https://www.stacksync.com/integrations/azure-cosmos-db-and-vertica) ### Business productivity · 29 - [Azure Cosmos DB and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-azure-cosmos-db) - [Azure Cosmos DB and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-azure-cosmos-db) - [Azure Cosmos DB and Asana](https://www.stacksync.com/integrations/asana-and-azure-cosmos-db) - [Azure Cosmos DB and Atlassian](https://www.stacksync.com/integrations/atlassian-and-azure-cosmos-db) - [Azure Cosmos DB and Braze](https://www.stacksync.com/integrations/azure-cosmos-db-and-braze) - [Azure Cosmos DB and Campfire](https://www.stacksync.com/integrations/azure-cosmos-db-and-campfire) - [Azure Cosmos DB and ConnectWise](https://www.stacksync.com/integrations/azure-cosmos-db-and-connectwise) - [Azure Cosmos DB and Docusign](https://www.stacksync.com/integrations/azure-cosmos-db-and-docusign) - [Azure Cosmos DB and eClinicalWorks](https://www.stacksync.com/integrations/azure-cosmos-db-and-eclinicalworks) - [Azure Cosmos DB and Front](https://www.stacksync.com/integrations/azure-cosmos-db-and-front) - [Azure Cosmos DB and Gainsight](https://www.stacksync.com/integrations/azure-cosmos-db-and-gainsight) - [Azure Cosmos DB and GitHub](https://www.stacksync.com/integrations/azure-cosmos-db-and-github) - [Azure Cosmos DB and Google Sheets](https://www.stacksync.com/integrations/azure-cosmos-db-and-google-sheets) - [Azure Cosmos DB and Ironclad](https://www.stacksync.com/integrations/azure-cosmos-db-and-ironclad) - [Azure Cosmos DB and Klaviyo](https://www.stacksync.com/integrations/azure-cosmos-db-and-klaviyo) - [Azure Cosmos DB and Lusha](https://www.stacksync.com/integrations/azure-cosmos-db-and-lusha) - [Azure Cosmos DB and Microsoft 365](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-365) - [Azure Cosmos DB and Microsoft Dynamics 365](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-dynamics-365) - [Azure Cosmos DB and Monday](https://www.stacksync.com/integrations/azure-cosmos-db-and-monday) - [Azure Cosmos DB and NextGen Healthcare](https://www.stacksync.com/integrations/azure-cosmos-db-and-nextgen-healthcare) - [Azure Cosmos DB and Notion](https://www.stacksync.com/integrations/azure-cosmos-db-and-notion) - [Azure Cosmos DB and Quip](https://www.stacksync.com/integrations/azure-cosmos-db-and-quip) - [Azure Cosmos DB and SendGrid](https://www.stacksync.com/integrations/azure-cosmos-db-and-sendgrid) - [Azure Cosmos DB and ServiceMax](https://www.stacksync.com/integrations/azure-cosmos-db-and-servicemax) - [Azure Cosmos DB and ServiceNow](https://www.stacksync.com/integrations/azure-cosmos-db-and-servicenow) - [Azure Cosmos DB and Smartsheet](https://www.stacksync.com/integrations/azure-cosmos-db-and-smartsheet) - [Azure Cosmos DB and SysAid](https://www.stacksync.com/integrations/azure-cosmos-db-and-sysaid) - [Azure Cosmos DB and Wrike](https://www.stacksync.com/integrations/azure-cosmos-db-and-wrike) - [Azure Cosmos DB and Zendesk](https://www.stacksync.com/integrations/azure-cosmos-db-and-zendesk) ### Accounting and finance · 13 - [Azure Cosmos DB and Adyen](https://www.stacksync.com/integrations/adyen-and-azure-cosmos-db) - [Azure Cosmos DB and Anaplan](https://www.stacksync.com/integrations/anaplan-and-azure-cosmos-db) - [Azure Cosmos DB and BILL](https://www.stacksync.com/integrations/azure-cosmos-db-and-bill) - [Azure Cosmos DB and Braintree](https://www.stacksync.com/integrations/azure-cosmos-db-and-braintree) - [Azure Cosmos DB and Chargebee](https://www.stacksync.com/integrations/azure-cosmos-db-and-chargebee) - [Azure Cosmos DB and Coupa](https://www.stacksync.com/integrations/azure-cosmos-db-and-coupa) - [Azure Cosmos DB and Navan](https://www.stacksync.com/integrations/azure-cosmos-db-and-navan) - [Azure Cosmos DB and QuickBooks](https://www.stacksync.com/integrations/azure-cosmos-db-and-quickbooks) - [Azure Cosmos DB and Ramp](https://www.stacksync.com/integrations/azure-cosmos-db-and-ramp) - [Azure Cosmos DB and Recurly](https://www.stacksync.com/integrations/azure-cosmos-db-and-recurly) - [Azure Cosmos DB and Stripe](https://www.stacksync.com/integrations/azure-cosmos-db-and-stripe) - [Azure Cosmos DB and Workday](https://www.stacksync.com/integrations/azure-cosmos-db-and-workday) - [Azure Cosmos DB and Zuora](https://www.stacksync.com/integrations/azure-cosmos-db-and-zuora) ### AI · 4 - [Azure Cosmos DB and Autopilot](https://www.stacksync.com/integrations/autopilot-and-azure-cosmos-db) - [Azure Cosmos DB and Azure OpenAI](https://www.stacksync.com/integrations/azure-cosmos-db-and-azure-openai) - [Azure Cosmos DB and OpenAI](https://www.stacksync.com/integrations/azure-cosmos-db-and-openai) - [Azure Cosmos DB and Pinecone](https://www.stacksync.com/integrations/azure-cosmos-db-and-pinecone) ### Analytics · 6 - [Azure Cosmos DB and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-azure-cosmos-db) - [Azure Cosmos DB and Microsoft Power BI](https://www.stacksync.com/integrations/azure-cosmos-db-and-microsoft-power-bi) - [Azure Cosmos DB and Mixpanel](https://www.stacksync.com/integrations/azure-cosmos-db-and-mixpanel) - [Azure Cosmos DB and Pendo](https://www.stacksync.com/integrations/azure-cosmos-db-and-pendo) - [Azure Cosmos DB and Splunk](https://www.stacksync.com/integrations/azure-cosmos-db-and-splunk) - [Azure Cosmos DB and Tableau](https://www.stacksync.com/integrations/azure-cosmos-db-and-tableau) ### Communications · 5 - [Azure Cosmos DB and Aircall](https://www.stacksync.com/integrations/aircall-and-azure-cosmos-db) - [Azure Cosmos DB and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-azure-cosmos-db) - [Azure Cosmos DB and Infobip](https://www.stacksync.com/integrations/azure-cosmos-db-and-infobip) - [Azure Cosmos DB and RingCentral](https://www.stacksync.com/integrations/azure-cosmos-db-and-ringcentral) - [Azure Cosmos DB and Zoom](https://www.stacksync.com/integrations/azure-cosmos-db-and-zoom) ### Developer tools · 9 - [Azure Cosmos DB and Azure Service Bus](https://www.stacksync.com/integrations/azure-cosmos-db-and-azure-service-bus) - [Azure Cosmos DB and Datadog](https://www.stacksync.com/integrations/azure-cosmos-db-and-datadog) - [Azure Cosmos DB and Jira](https://www.stacksync.com/integrations/azure-cosmos-db-and-jira) - [Azure Cosmos DB and JMS](https://www.stacksync.com/integrations/azure-cosmos-db-and-jms) - [Azure Cosmos DB and LDAP](https://www.stacksync.com/integrations/azure-cosmos-db-and-ldap) - [Azure Cosmos DB and New Relic](https://www.stacksync.com/integrations/azure-cosmos-db-and-newrelic) - [Azure Cosmos DB and Opsgenie](https://www.stacksync.com/integrations/azure-cosmos-db-and-opsgenie) - [Azure Cosmos DB and PagerDuty](https://www.stacksync.com/integrations/azure-cosmos-db-and-pagerduty) - [Azure Cosmos DB and RabbitMQ](https://www.stacksync.com/integrations/azure-cosmos-db-and-rabbitmq) ### E-commerce · 6 - [Azure Cosmos DB and Akeneo](https://www.stacksync.com/integrations/akeneo-and-azure-cosmos-db) - [Azure Cosmos DB and BigCommerce](https://www.stacksync.com/integrations/azure-cosmos-db-and-bigcommerce) - [Azure Cosmos DB and EasyPost](https://www.stacksync.com/integrations/azure-cosmos-db-and-easypost) - [Azure Cosmos DB and Magento](https://www.stacksync.com/integrations/azure-cosmos-db-and-magento) - [Azure Cosmos DB and Shipwire](https://www.stacksync.com/integrations/azure-cosmos-db-and-shipwire) - [Azure Cosmos DB and Shopware](https://www.stacksync.com/integrations/azure-cosmos-db-and-shopware) ### Human resources · 12 - [Azure Cosmos DB and BambooHR](https://www.stacksync.com/integrations/azure-cosmos-db-and-bamboohr) - [Azure Cosmos DB and Ceridian Dayforce](https://www.stacksync.com/integrations/azure-cosmos-db-and-ceridian-dayforce) - [Azure Cosmos DB and Greenhouse](https://www.stacksync.com/integrations/azure-cosmos-db-and-greenhouse) - [Azure Cosmos DB and Hibob](https://www.stacksync.com/integrations/azure-cosmos-db-and-hibob) - [Azure Cosmos DB and Jobvite](https://www.stacksync.com/integrations/azure-cosmos-db-and-jobvite) - [Azure Cosmos DB and Lever](https://www.stacksync.com/integrations/azure-cosmos-db-and-lever) - [Azure Cosmos DB and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/azure-cosmos-db-and-oracle-fusion-cloud-hcm) - [Azure Cosmos DB and Paylocity](https://www.stacksync.com/integrations/azure-cosmos-db-and-paylocity) - [Azure Cosmos DB and SmartRecruiters](https://www.stacksync.com/integrations/azure-cosmos-db-and-smartrecruiters) - [Azure Cosmos DB and Success Factors](https://www.stacksync.com/integrations/azure-cosmos-db-and-success-factors) - [Azure Cosmos DB and UKG Pro](https://www.stacksync.com/integrations/azure-cosmos-db-and-ukg-pro) - [Azure Cosmos DB and UKG Ready](https://www.stacksync.com/integrations/azure-cosmos-db-and-ukg-ready) ### Marketing · 8 - [Azure Cosmos DB and Bingads](https://www.stacksync.com/integrations/azure-cosmos-db-and-bingads) - [Azure Cosmos DB and Cvent](https://www.stacksync.com/integrations/azure-cosmos-db-and-cvent) - [Azure Cosmos DB and Demandbase](https://www.stacksync.com/integrations/azure-cosmos-db-and-demandbase) - [Azure Cosmos DB and Eloqua](https://www.stacksync.com/integrations/azure-cosmos-db-and-eloqua) - [Azure Cosmos DB and Iterable](https://www.stacksync.com/integrations/azure-cosmos-db-and-iterable) - [Azure Cosmos DB and Marketo](https://www.stacksync.com/integrations/azure-cosmos-db-and-marketo) - [Azure Cosmos DB and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/azure-cosmos-db-and-salesforce-marketing-cloud) - [Azure Cosmos DB and Twitter Ads](https://www.stacksync.com/integrations/azure-cosmos-db-and-twitter-ads) ### Security and identity · 6 - [Azure Cosmos DB and Active Directory](https://www.stacksync.com/integrations/active-directory-and-azure-cosmos-db) - [Azure Cosmos DB and Auth0](https://www.stacksync.com/integrations/auth0-and-azure-cosmos-db) - [Azure Cosmos DB and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-azure-cosmos-db) - [Azure Cosmos DB and JumpCloud](https://www.stacksync.com/integrations/azure-cosmos-db-and-jumpcloud) - [Azure Cosmos DB and Okta](https://www.stacksync.com/integrations/azure-cosmos-db-and-okta) - [Azure Cosmos DB and OneLogin](https://www.stacksync.com/integrations/azure-cosmos-db-and-onelogin) ### Storage · 4 - [Azure Cosmos DB and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-azure-cosmos-db) - [Azure Cosmos DB and Box](https://www.stacksync.com/integrations/azure-cosmos-db-and-box) - [Azure Cosmos DB and Egnyte](https://www.stacksync.com/integrations/azure-cosmos-db-and-egnyte) - [Azure Cosmos DB and SharePoint](https://www.stacksync.com/integrations/azure-cosmos-db-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/)