Skip to content
ERP ⇄ Security and identity

Microsoft Dynamics NAV to Okta integration — real-time, two-way sync

Keep Microsoft Dynamics NAV and Okta 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 Microsoft Dynamics NAV and Okta

Keep the employee, group, and account records that Microsoft Dynamics NAV and Okta share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.

An ERP and an identity system describe the same workforce from two angles. Microsoft Dynamics NAV holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Okta controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Microsoft Dynamics NAV and their account still being active in Okta is a real security exposure.

Stacksync syncs Item Ledger Entries, Dimensions, Companies, Customers in Microsoft Dynamics NAV with Groups, Applications, Group Rules, Factors (Authenticators) in Okta in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.

That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.

Common use cases

  • 01 Replicate G/L and ledger entries into a warehouse for consolidated finance reporting.
  • 02 Keep inventory availability current in storefronts and customer portals.
  • 03 Drive Group Rules and policy assignments from HR attributes so access changes the moment a title, department, or location changes.
  • 04 Sync Groups and their memberships two-way between Okta and a database or IdP so downstream app access stays aligned with source-of-truth org data.

Common sync patterns

Create accounts from new records

A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.

Disable access at offboarding

When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.

Keep profile attributes current

A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.

What you can sync between Microsoft Dynamics NAV and Okta

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.

Microsoft Dynamics NAV objects Okta objects How this pairing syncs
Items Item cards and availability mirrored to ecommerce and planning systems. System Log Immutable audit event stream of logins, admin changes, and lifecycle events; read-only, polled by timestamp and used as the change feed and SIEM source. Items is specific to Microsoft Dynamics NAV and System Log to Okta — each maps to any object or custom field on the other side.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Devices Registered and managed device records tied to users; read to correlate access with device posture and to feed inventory or conditional-access reporting. Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Devices to Okta — each maps to any object or custom field on the other side.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Users Universal Directory user records with profile attributes, credentials, and lifecycle status (staged, active, suspended, deprovisioned); full CRUD, so users are created, updated, activated, and deactivated to match an HR or identity source. Purchase Orders is specific to Microsoft Dynamics NAV and Users to Okta — each maps to any object or custom field on the other side.
G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Groups Okta groups (OKTA_GROUP, APP_GROUP, BUILT_IN) and their memberships; OKTA_GROUP records and membership are written to drive app and resource access. G/L Entries is specific to Microsoft Dynamics NAV and Groups to Okta — each maps to any object or custom field on the other side.
Item Ledger Entries Inventory movement history read for stock and costing analytics. Applications App integrations (SAML, OIDC, SWA) with per-user and per-group assignments; read and updated to manage which identities can reach each downstream app. Item Ledger Entries is specific to Microsoft Dynamics NAV and Applications to Okta — each maps to any object or custom field on the other side.
Dimensions Analytical codes carried on documents and entries for reporting splits. Group Rules Dynamic rules that add users to groups from profile attributes; read and written to automate access based on department, title, or location. Dimensions is specific to Microsoft Dynamics NAV and Group Rules to Okta — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV and Okta

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.

Microsoft Dynamics NAV Okta 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 written to Okta through its API, with automatic retries and rate-limit backoff.

Okta Microsoft Dynamics NAV Sub-second propagation

DetectionOkta notifies Stacksync of record changes through webhook events. Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time.

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

Rate-limit considerations

  • Okta: Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
What ships with Microsoft Dynamics NAV ⇄ Okta

Connect Microsoft Dynamics NAV and Okta for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or Okta instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics NAV or Okta 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 Microsoft Dynamics NAV or Okta record.

Observability

Monitoring

Track your Microsoft Dynamics NAV ⇄ Okta sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics NAV and Okta.

How the Microsoft Dynamics NAV and Okta connectors work

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

Okta

Integration surface
REST API (Okta Management API, /api/v1) with Event Hooks for outbound events and the System Log API as the change feed
Authentication
SSWS API tokens (Authorization: SSWS {token}) scoped to the creating admin's permissions, or OAuth 2.0 for Okta service apps using a private-key-JWT client-credentials grant with granular scopes (DPoP supported)
Change detection
Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time verification handshake); the System Log API (/api/v1/logs) is polled by the since parameter and the next Link header for a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
How it works

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

    Choose tables

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

Microsoft Dynamics NAV and Okta 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 502 integrations available for Microsoft Dynamics NAV and Okta.

Popular · 6 of 502
All Microsoft Dynamics NAV integrations All Okta 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