Skip to content
Database ⇄ CRM

Azure Cosmos DB to Dun And Bradstreet integration — real-time data sync

Keep Azure Cosmos DB and Dun And Bradstreet 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 Dun And Bradstreet

Treat Dun And Bradstreet like part of your database: its records live in Azure Cosmos DB as real tables, and writes in either place sync to the other in seconds.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Azure Cosmos DB, so Azure Cosmos DB always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Azure Cosmos DB, where it can be queried and joined like everything else.

Common use cases

  • 01 Pull D&B risk and credit signals (PAYDEX, Failure Score, D&B Rating) into a warehouse for credit-risk, vendor-risk, and third-party-risk analytics.
  • 02 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
  • 03 Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
  • 04 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.

Common sync patterns

Trigger workflows from CRM changes

Field and stage updates in Dun And Bradstreet arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Dun And Bradstreet become tables in Azure Cosmos DB you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Azure Cosmos DB sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.

What you can sync between Azure Cosmos DB and Dun And Bradstreet

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 Dun And Bradstreet objects How this pairing syncs
Containers The unit of partitioning and throughput; each container maps to a synced collection. Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. Containers is specific to Azure Cosmos DB and Criteria Search to Dun And Bradstreet — 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. Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. Items (JSON documents) is specific to Azure Cosmos DB and Monitoring Notifications to Dun And Bradstreet — 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. Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. Partition keys is specific to Azure Cosmos DB and Company Information (Data Block) to Dun And Bradstreet — 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. Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Change feed entries is specific to Azure Cosmos DB and Principals & Contacts (Data Block) to Dun And Bradstreet — 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. Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Stored procedures and triggers is specific to Azure Cosmos DB and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. Databases is specific to Azure Cosmos DB and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Dun And Bradstreet

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 Dun And Bradstreet 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.

DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Azure Cosmos DB records.

Dun And Bradstreet Azure Cosmos DB Interval-based propagation

DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).

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

Rate-limit considerations

  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
What ships with Azure Cosmos DB ⇄ Dun And Bradstreet

Connect Azure Cosmos DB and Dun And Bradstreet for flexible, real-time data sync.

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

Real-time

Real-time sync

Changes in Azure Cosmos DB or Dun And Bradstreet 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 Dun And Bradstreet 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 Dun And Bradstreet record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Dun And Bradstreet 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 Dun And Bradstreet.

How the Azure Cosmos DB and Dun And Bradstreet 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

Dun And Bradstreet

Integration surface
D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
Authentication
OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
How it works

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

    Choose tables

    Pick the Azure Cosmos DB and Dun And Bradstreet 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 ⇄ Dun And Bradstreet
    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 Dun And Bradstreet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Cosmos DB and Dun And Bradstreet 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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 415 integrations available for Azure Cosmos DB and Dun And Bradstreet.

Popular · 7 of 415
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.