Skip to content
Database ⇄ ERP

Azure Cosmos DB to Microsoft Dynamics NAV integration — real-time, two-way sync

Keep Azure Cosmos DB and Microsoft Dynamics NAV 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 Microsoft Dynamics NAV

Give your engineers Microsoft Dynamics NAV's data in Azure Cosmos DB: read it with normal queries, write back through the sync, and skip the ERP API entirely.

ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.

Stacksync mirrors Items, Sales Orders & Invoices, Purchase Orders, G/L Entries from Microsoft Dynamics NAV into Azure Cosmos DB and keeps both sides consistent in real time. Whatever Microsoft Dynamics NAV is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in Azure Cosmos DB sync back into Microsoft Dynamics NAV with its validations respected.

Common use cases

  • 01 Consolidate documents from multiple containers into a single reporting store.
  • 02 Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
  • 03 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.
  • 04 Sync customers, items, and orders between NAV and a CRM in both directions.

Common sync patterns

Where Microsoft Dynamics NAV is the HR system of record: people data for internal systems

Worker and org records stay current in Azure Cosmos DB for provisioning, access, and reporting systems that read from the database.

Controlled write-back

Choose exactly which tables and fields may flow from Azure Cosmos DB back into Microsoft Dynamics NAV, keeping the ERP authoritative.

Read ERP records with a query

Records from Microsoft Dynamics NAV live in Azure Cosmos DB as ordinary tables or collections, joinable with the rest of your data.

What you can sync between Azure Cosmos DB and Microsoft Dynamics NAV

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 Microsoft Dynamics NAV objects How this pairing syncs
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Stored procedures and triggers is specific to Azure Cosmos DB and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Item Ledger Entries Inventory movement history read for stock and costing analytics. Databases is specific to Azure Cosmos DB and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Dimensions Analytical codes carried on documents and entries for reporting splits. Containers is specific to Azure Cosmos DB and Dimensions to Microsoft Dynamics NAV — 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. Companies Per-company data partitions that scope every sync. Items (JSON documents) is specific to Azure Cosmos DB and Companies to Microsoft Dynamics NAV — 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. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Partition keys is specific to Azure Cosmos DB and Customers to Microsoft Dynamics NAV — 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. Vendors Vendor cards aligned with procurement and AP tools. Change feed entries is specific to Azure Cosmos DB and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB and Microsoft Dynamics NAV

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 Microsoft Dynamics NAV 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.

DeliveryEach detected change is applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.

Microsoft Dynamics NAV Azure Cosmos DB Sub-second propagation

DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.

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

What ships with Azure Cosmos DB ⇄ Microsoft Dynamics NAV

Connect Azure Cosmos DB and Microsoft Dynamics NAV for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Microsoft Dynamics NAV connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Microsoft Dynamics NAV 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 Microsoft Dynamics NAV 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 Microsoft Dynamics NAV record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Microsoft Dynamics NAV 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 Microsoft Dynamics NAV.

How the Azure Cosmos DB and Microsoft Dynamics NAV 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

Microsoft Dynamics NAV

Integration surface
SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
Authentication
Windows authentication or NavUserPassword credentials
Change detection
Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
Capabilities
read · write · CDC
How it works

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

    Choose tables

    Pick the Azure Cosmos DB and Microsoft Dynamics NAV 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 ⇄ Microsoft Dynamics NAV
    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 Microsoft Dynamics NAV
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Cosmos DB and Microsoft Dynamics NAV 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.

Learn more about 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 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 436 integrations available for Azure Cosmos DB and Microsoft Dynamics NAV.

Popular · 7 of 436
All Azure Cosmos DB integrations All Microsoft Dynamics NAV integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own