Real-time sync
Changes in Azure Cosmos DB or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Field and stage updates in Dun And Bradstreet arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from Dun And Bradstreet become tables in Azure Cosmos DB you can join with application data directly.
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.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Dun And Bradstreet connection.
Changes in Azure Cosmos DB or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
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.
Handle millions of events per minute without losing a single Azure Cosmos DB or Dun And Bradstreet record.
Track your Azure Cosmos DB ⇄ Dun And Bradstreet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Dun And Bradstreet.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between Azure Cosmos DB and Dun And Bradstreet — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into Azure Cosmos DB. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for Azure Cosmos DB and Dun And Bradstreet: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Dun And Bradstreet arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.
Azure Cosmos DB: 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. Dun And Bradstreet: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Dun And Bradstreet: D&B Direct+ is a reference-data / enrichment API - read and enrich only. You retrieve firmographics, contacts, hierarchy, and risk scores for a D-U-N-S Number; there is no endpoint to write business records back into D&B. Azure Cosmos DB: The same account can be exposed through multiple wire-compatible APIs (NoSQL, MongoDB, Cassandra, Gremlin, Table), and the API choice fixes how a connector must speak to it. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and Dun And Bradstreet without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Cosmos DB and Dun And Bradstreet records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 415 integrations available for Azure Cosmos DB and Dun And Bradstreet.