Real-time
Two-way sync
Changes in Active Directory or Sage X3 instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to Sage X3 integration — real-time, two-way sync
Keep Active Directory and Sage X3 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 Sage X3
Keep the employee, group, and account records that Sage X3 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. Sage X3 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 Sage X3 and their account still being active in Active Directory is a real security exposure.
Stacksync syncs GL Journals, Deliveries, Business Partners (Customers and Suppliers), Products in Sage X3 with Groups, Group memberships, Devices, Directory roles 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 Replicate GL journals and sales history to a warehouse for multi-company, multi-legislation reporting.
- 02 Feed work order and BOM data to MES or planning tools on the shop floor.
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
One roster on a shared key
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.
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.
What you can sync between Active Directory and Sage X3
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 | Sage X3 objects | How this pairing syncs | |
|---|---|---|---|
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Deliveries Shipment documents synced to logistics providers and customer portals. | Directory roles is specific to Active Directory and Deliveries to Sage X3 — 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. | Business Partners (Customers and Suppliers) Shared partner master synced with CRMs and procurement systems. | Service principals & applications is specific to Active Directory and Business Partners (Customers and Suppliers) to Sage X3 — 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. | Products Item master with units, costing, and site data, synced to commerce and PLM tools. | Organizational units is specific to Active Directory and Products to Sage X3 — 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. | Sales Orders Order documents written from external channels and read for fulfillment status. | Organizational contacts is specific to Active Directory and Sales Orders to Sage X3 — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Purchase Orders Procurement documents synced with supplier-facing systems. | Users is specific to Active Directory and Purchase Orders to Sage X3 — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Work Orders Production orders read by MES and scheduling integrations. | Groups is specific to Active Directory and Work Orders to Sage X3 — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Sage X3
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 Sage X3 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 applied to Sage X3 as a row-level write, with types converted between the two schemas.
Sage X3 Active Directory Interval-based propagation
DetectionStacksync polls Sage X3 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
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.
What ships with Active Directory ⇄ Sage X3
Connect Active Directory and Sage X3 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Sage X3 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Sage X3 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 Sage X3 record.
Observability
Monitoring
Track your Active Directory ⇄ Sage X3 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 Sage X3.
How the Active Directory and Sage X3 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.
Sage X3
- Integration surface
- SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem
- Authentication
- Dedicated web-service user credentials (Basic auth) against configured connection pools
- Change detection
- Scheduled polling; no general webhook surface on the classic web services layer
- Capabilities
- read · write
How it works
How to connect Active Directory to Sage X3 — 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.
- 01
Connect your apps
Authenticate Active Directory and Sage X3 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Sage X3
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Sage X3 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.
objects · Active Directory ⇄ Sage X3Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Active Directory Sage X3Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Sage X3 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Sage X3: authenticate both systems, choose the objects to sync (such as Active Directory's Directory roles and Service principals & applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Sage X3 side: GL Journals, Deliveries, Business Partners (Customers and Suppliers), Products, plus custom fields where Sage X3 exposes them. On the Active Directory side: Groups, Group memberships, Devices, Directory roles. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Active Directory and Sage X3: Align group and department membership; One roster on a shared key; Create accounts from new records. When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
-
Active Directory: 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. Sage X3: SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem. Authentication: Dedicated web-service user credentials (Basic auth) against configured connection pools. Stacksync manages authentication, retries, and rate limits on both sides.
-
Sage X3: One X3 instance can run multiple companies, sites, and legislations, and integrations must carry that context (company, site) on each document. Active Directory: Microsoft Graph delta tokens for directory objects expire after about seven days; a sync paused longer must reinitialize with a full read. Stacksync's field mapping accounts for these differences between Active Directory and Sage X3 without custom code.
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 506 integrations available for Active Directory and Sage X3.
Popular · 8 of 506
-
Active Directory ⇄ Macola ERP -
Active Directory ⇄ Manhattan Associates WMS -
Active Directory ⇄ Microsoft Dynamics GP - Active Directory ⇄ Microsoft Dynamics NAV
-
Sage X3 ⇄ Jumpcloud - Sage X3 ⇄ Azure Active Directory
-
Sage X3 ⇄ Okta -
Sage X3 ⇄ Onelogin
No integrations match .
