Real-time sync
Changes in Dun And Bradstreet or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Keep Dun And Bradstreet and Microsoft 365 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 Microsoft 365, so Microsoft 365 always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Microsoft 365 holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Enriched fields land directly on records in Dun And Bradstreet, and refreshes keep them from going stale.
Charges, refunds, and subscription changes appear on the account in Dun And Bradstreet, so revenue context lives with the relationship.
Owner, lifecycle stage, or account details from Dun And Bradstreet sync into Microsoft 365, so people working there have the context without switching tools.
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.
| Dun And Bradstreet objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Planner & To Do Tasks Task items synced with project and work-management tools. | Company Information (Data Block) is specific to Dun And Bradstreet and Planner & To Do Tasks to Microsoft 365 — each maps to any object or custom field on the other side. | |
| 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. | Users Entra ID user accounts synced with HR and identity systems. | Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Users to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| 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. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. | |
| 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. | Contacts Personal and org contacts kept consistent with CRM contact records. | Criteria Search is specific to Dun And Bradstreet and Contacts to Microsoft 365 — 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.
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 written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
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 Microsoft 365 records.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Microsoft 365 connection.
Changes in Dun And Bradstreet or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dun And Bradstreet or Microsoft 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dun And Bradstreet or Microsoft 365 record.
Track your Dun And Bradstreet ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and Microsoft 365.
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 Dun And Bradstreet and Microsoft 365 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 Dun And Bradstreet and Microsoft 365 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 Dun And Bradstreet and Microsoft 365 — 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 Microsoft 365. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for Dun And Bradstreet and Microsoft 365: Where Microsoft 365 supplies contact or company data; Where Microsoft 365 processes payments; Where Microsoft 365 can store CRM context: fields kept current. Enriched fields land directly on records in Dun And Bradstreet, and refreshes keep them from going stale.
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. Microsoft 365: REST API (Microsoft Graph). Authentication: OAuth 2.0 via Microsoft Entra ID, with delegated or application permissions. Stacksync manages authentication, retries, and rate limits on both sides.
Microsoft 365: Delta queries return only resources changed since the last sync token, which keeps incremental syncs cheap on large tenants. Dun And Bradstreet: Auth is OAuth 2.0 client-credentials: Base-auth a key/secret to POST /v3/token for a bearer token, and access tokens expire after 24 hours. Stacksync's field mapping accounts for these differences between Dun And Bradstreet and Microsoft 365 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 Dun And Bradstreet and Microsoft 365 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 432 integrations available for Dun And Bradstreet and Microsoft 365.