Skip to content
Security and identity ⇄ ERP

Active Directory to SAP integration — real-time, two-way sync

Keep Active Directory and SAP 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

Keep the employee, group, and account records that SAP 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 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 and their account still being active in Active Directory is a real security exposure.

Stacksync syncs Sales Orders, Purchase Orders, Outbound Deliveries, Billing Documents in SAP with Organizational units, Organizational contacts, Users, Groups 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 journal entries and billing documents to a warehouse for finance analytics without loading the ERP.
  • 02 Keep MES and WMS systems aligned with production orders and goods movements.
  • 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

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 SAP

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 objects How this pairing syncs
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Business Partners The unified customer and supplier master in S/4HANA, the anchor object for CRM and procurement syncs. Service principals & applications is specific to Active Directory and Business Partners to SAP — 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. Materials (Products) Item master with plant and sales views, synced to commerce, PLM, and CRM systems. Organizational units is specific to Active Directory and Materials (Products) to SAP — 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 status and fulfillment. Organizational contacts is specific to Active Directory and Sales Orders to SAP — 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 portals and spend tools. Users is specific to Active Directory and Purchase Orders to SAP — 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. Outbound Deliveries Shipment documents synced to WMS, carriers, and customer portals. Groups is specific to Active Directory and Outbound Deliveries to SAP — each maps to any object or custom field on the other side.
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Billing Documents Invoices read for AR status and replicated for revenue reporting. Group memberships is specific to Active Directory and Billing Documents to SAP — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and SAP

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 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 through its API, with automatic retries and rate-limit backoff.

SAP Active Directory Sub-second propagation

DetectionSAP notifies Stacksync of record changes through webhook events. Business events via SAP Event Mesh on S/4HANA.

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: Throttling is configured at the gateway and tenant level rather than as a single published rate limit.
What ships with Active Directory ⇄ SAP

Connect Active Directory and SAP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–SAP connection.

Real-time

Two-way sync

Changes in Active Directory or SAP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or SAP 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 record.

Observability

Monitoring

Track your Active Directory ⇄ SAP 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.

How the Active Directory and SAP 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

Integration surface
OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication
OAuth 2.0 or basic auth via communication arrangements on cloud editions; SAP user credentials for RFC on-prem
Change detection
Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC
Capabilities
read · write · webhooks
Rate limits
Throttling is configured at the gateway and tenant level rather than as a single published rate limit
How it works

How to connect Active Directory to SAP — 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 SAP 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
    SAP connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and SAP 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 ⇄ SAP
    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 SAP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and SAP 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 528 integrations available for Active Directory and SAP.

Popular · 6 of 528
All Active Directory integrations All SAP 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