Two-way sync
Changes in Azure Active Directory or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Active Directory 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.
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. Azure Active Directory 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 Azure Active Directory is a real security exposure.
Stacksync syncs Dimensions, Companies, Customers, Vendors in Microsoft Dynamics NAV with Groups, Group memberships, Applications, Service principals in Azure Active Directory 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.
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
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 Active Directory objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Directory roles /directoryRoles and roleManagement assignments; read for privileged-access reviews, with role-assignment writes where the granted scopes permit. | Companies Per-company data partitions that scope every sync. | Directory roles is specific to Azure Active Directory and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Devices /devices registered or joined to the tenant; typically read-only into asset and security databases. | Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Devices is specific to Azure Active Directory and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Users /users in Microsoft Graph; synced two-way — profile attributes, accountEnabled, and assignedLicenses are read out while provisioning writes (create, update, disable, delete) are pushed back. | Vendors Vendor cards aligned with procurement and AP tools. | Users is specific to Azure Active Directory and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Groups /groups covering security and Microsoft 365 groups; created, updated, and deleted through Graph, and read into warehouses for entitlement reporting. | Items Item cards and availability mirrored to ecommerce and planning systems. | Groups is specific to Azure Active Directory and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner relationships on /groups/{id}/members; added and removed via the $ref endpoint and tracked for changes with delta query on $select=members. | Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Group memberships is specific to Azure Active Directory and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Applications App registrations under /applications; usually read into a database or CMDB for app ownership and credential-expiry tracking. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Applications is specific to Azure Active Directory and Purchase Orders to Microsoft Dynamics NAV — 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.
DetectionAzure Active Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (deltaLink tokens returning only changed users and groups, with @removed deletions) paired with change-notification.
DeliveryEach detected change is applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
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 Azure Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Active Directory–Microsoft Dynamics NAV connection.
Changes in Azure Active Directory or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Active Directory or Microsoft Dynamics NAV 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 Active Directory or Microsoft Dynamics NAV record.
Track your Azure Active Directory ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Active Directory and Microsoft Dynamics NAV.
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 Active Directory 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.
Pick the Azure Active Directory 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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 502 integrations available for Azure Active Directory and Microsoft Dynamics NAV.