Skip to content
Security and identity ⇄ ERP

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

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

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

Stacksync syncs Journal Entries, Warehouses, Price Lists, Activities in SAP Business One with Devices, Directory roles, Service principals & applications, Organizational units 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 invoices and journal entries into a SQL database for reporting without direct ERP database access.
  • 02 Sync activities and service data with external support tools for teams that do not log into Business One.
  • 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
  • 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.

Common sync patterns

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.

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.

What you can sync between Active Directory and SAP Business One

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 Business One objects How this pairing syncs
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. Warehouses Stock locations that scope inventory quantities in item syncs. Organizational units is specific to Active Directory and Warehouses to SAP Business One — 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. Price Lists Pricing data synced to quoting and e-commerce platforms. Organizational contacts is specific to Active Directory and Price Lists to SAP Business One — 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. Activities CRM-style tasks and interactions aligned with external sales tools. Users is specific to Active Directory and Activities to SAP Business One — 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. Business Partners Combined customer, vendor, and lead master records; the anchor object for most syncs. Groups is specific to Active Directory and Business Partners to SAP Business One — 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. Items Product master data including inventory levels, aligned with e-commerce and warehouse systems. Group memberships is specific to Active Directory and Items to SAP Business One — 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. Sales Orders Order documents with header and line structure created from external channels. Devices is specific to Active Directory and Sales Orders to SAP Business One — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and SAP Business One

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

SAP Business One Active Directory Interval-based propagation

DetectionStacksync polls SAP Business One for changes on an incremental schedule, reading only records changed since the previous pass. Polling on update timestamps.

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 ⇄ SAP Business One

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

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

Real-time

Two-way sync

Changes in Active Directory or SAP Business One 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 Business One 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 Business One record.

Observability

Monitoring

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

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

Integration surface
Service Layer, a REST API based on OData, plus the legacy COM-based DI API
Authentication
Session-based login with company database, username, and password against the Service Layer
Change detection
Polling on update timestamps; no general-purpose webhook mechanism on the standard surface
Capabilities
read · write
How it works

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

    Choose tables

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

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

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