Real-time
Two-way sync
Changes in Active Directory or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to SAP S/4HANA integration — real-time, two-way sync
Keep Active Directory and SAP S/4HANA 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 SAP S/4HANA
Keep the employee, group, and account records that SAP S/4HANA 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. SAP S/4HANA 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 SAP S/4HANA and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Products / Materials, Billing Documents (Invoices), Deliveries, Journal Entries in SAP S/4HANA 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 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
- 02 Replicate material master and pricing data to e-commerce and quoting tools.
- 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
Common sync patterns
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.
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.
What you can sync between Active Directory and SAP S/4HANA
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 | SAP S/4HANA objects | How this pairing syncs | |
|---|---|---|---|
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Products / Materials Material master data distributed to e-commerce, PIM, and CRM catalogs. | Group memberships is specific to Active Directory and Products / Materials to SAP S/4HANA — 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. | Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. | Devices is specific to Active Directory and Billing Documents (Invoices) to SAP S/4HANA — 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. | Deliveries Outbound delivery status synced to customer-facing systems for order tracking. | Directory roles is specific to Active Directory and Deliveries to SAP S/4HANA — 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. | Journal Entries Financial postings read into warehouses and consolidation tools for reporting. | Service principals & applications is specific to Active Directory and Journal Entries to SAP S/4HANA — 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. | Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. | Organizational units is specific to Active Directory and Customer / Supplier Roles to SAP S/4HANA — 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. | Production Orders Manufacturing order status surfaced in planning and operations tools. | Organizational contacts is specific to Active Directory and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and SAP S/4HANA
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 SAP S/4HANA 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 SAP S/4HANA through its API, with automatic retries and rate-limit backoff.
SAP S/4HANA Active Directory Interval-based propagation
DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.
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.
- SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Active Directory ⇄ SAP S/4HANA
Connect Active Directory and SAP S/4HANA for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–SAP S/4HANA connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or SAP S/4HANA 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 SAP S/4HANA record.
Observability
Monitoring
Track your Active Directory ⇄ SAP S/4HANA 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 SAP S/4HANA.
How the Active Directory and SAP S/4HANA 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.
SAP S/4HANA
- Integration surface
- OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
- Authentication
- OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
- Change detection
- Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works
How to connect Active Directory to SAP S/4HANA — 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 SAP S/4HANA 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
SAP S/4HANA
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and SAP S/4HANA 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 ⇄ SAP S/4HANACustomers 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 SAP S/4HANACompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and SAP S/4HANA integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and SAP S/4HANA: authenticate both systems, choose the objects to sync (such as Active Directory's Group memberships and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
SAP S/4HANA: Released integration APIs are published as OData services in the SAP Business Accelerator Hub, backed by CDS views. Active Directory: On-premises AD DS has no Graph API and syncs over LDAP/LDAPS using the DirSync control, which needs the DS-Replication-Get-Changes right on the partition. Stacksync's field mapping accounts for these differences between Active Directory and SAP S/4HANA without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Active Directory and SAP S/4HANA records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and SAP S/4HANA connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–SAP S/4HANA integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and SAP S/4HANA. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: 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. On SAP S/4HANA: Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 507 integrations available for Active Directory and SAP S/4HANA.
Popular · 8 of 507
-
Active Directory ⇄ Microsoft Dynamics NAV -
Active Directory ⇄ Plex ERP -
Active Directory ⇄ QAD ERP -
Active Directory ⇄ Rootstock ERP -
SAP S/4HANA ⇄ Auth0 -
SAP S/4HANA ⇄ Jumpcloud - SAP S/4HANA ⇄ Azure Active Directory
-
SAP S/4HANA ⇄ Okta
No integrations match .
