Skip to content
Security and identity ⇄ ERP

Active Directory to Dynamics 365 F&O integration — real-time, two-way sync

Keep Active Directory and Dynamics 365 F&O 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 Active Directory and Dynamics 365 F&O

Keep the employee, group, and account records that Dynamics 365 F&O and Active Directory 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. Dynamics 365 F&O holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. 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 Dynamics 365 F&O and their account still being active in Active Directory is a real security exposure.

Stacksync syncs Vendors, Released Products, Sales Orders, Purchase Orders in Dynamics 365 F&O with Users, Groups, Group memberships, Devices in 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.

Common use cases

  • 01 Mirror GL journals and invoice lines into a warehouse for finance reporting without recurring DMF exports.
  • 02 Distribute product and price master data from F&O to downstream channels through a synced database.
  • 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
  • 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.

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 Active Directory and Dynamics 365 F&O

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.

Active Directory objects Dynamics 365 F&O objects How this pairing syncs
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Customer Invoices AR billing documents; status synced back to CRM and customer success tools. Group memberships is specific to Active Directory and Customer Invoices to Dynamics 365 F&O — each maps to any object or custom field on the other side.
Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. Vendor Invoices AP documents; synced with invoice automation systems. Devices is specific to Active Directory and Vendor Invoices to Dynamics 365 F&O — each maps to any object or custom field on the other side.
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. General Journal Entries GL postings; read-only extracts for consolidated finance reporting. Directory roles is specific to Active Directory and General Journal Entries to Dynamics 365 F&O — each maps to any object or custom field on the other side.
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. Service principals & applications is specific to Active Directory and On-hand Inventory to Dynamics 365 F&O — each maps to any object or custom field on the other side.
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. Customers Customer master records; kept aligned with CRM accounts in two-way syncs. Organizational units is specific to Active Directory and Customers to Dynamics 365 F&O — each maps to any object or custom field on the other side.
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Vendors Supplier master records; synced with procurement and AP tools. Organizational contacts is specific to Active Directory and Vendors to Dynamics 365 F&O — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Dynamics 365 F&O

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.

Active Directory Dynamics 365 F&O Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

DeliveryEach detected change is written to Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.

Dynamics 365 F&O Active Directory Sub-second propagation

DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.

DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
What ships with Active Directory ⇄ Dynamics 365 F&O

Connect Active Directory and Dynamics 365 F&O for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Dynamics 365 F&O connection.

Real-time

Two-way sync

Changes in Active Directory or Dynamics 365 F&O instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Dynamics 365 F&O 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 Active Directory or Dynamics 365 F&O record.

Observability

Monitoring

Track your Active Directory ⇄ Dynamics 365 F&O sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Active Directory and Dynamics 365 F&O.

How the Active Directory and Dynamics 365 F&O connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

Dynamics 365 F&O

Integration surface
OData REST endpoint over data entities, plus the Data Management Framework for batch
Authentication
OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
Change detection
Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
Capabilities
read · write · CDC · webhooks
Rate limits
OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
Dynamics 365 F&O setup guide
How it works

How to connect Active Directory to Dynamics 365 F&O — 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 Active Directory and Dynamics 365 F&O 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
    Active Directory connected
    Dynamics 365 F&O connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and Dynamics 365 F&O 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 · Active Directory ⇄ Dynamics 365 F&O
    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
    Active Directory Dynamics 365 F&O
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Active Directory and Dynamics 365 F&O 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 412 integrations available for Active Directory and Dynamics 365 F&O.

Popular · 6 of 412
Coworkers laughing in front of a laptop in a casual office setting

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