Connect SAP SuccessFactors to Active Directory (on-premise)

How does Joinly sync SAP SuccessFactors to Active Directory?

Joinly reads each HR change in Employee Central in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Employee Central holds the authoritative employment record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in Employee Central. Joinly reads the new records, determines the role from department, job classification and cost center, and instructs the AD Agent to create the user in the correct OU, build the sAMAccountName and UPN from your rules, and add the right security groups — timed to the effective start date.

2. Mover. When someone changes position, department or legal entity, Joinly tells the agent to move the user to the matching OU, swap security-group membership and update attributes. Access that no longer fits the new position is removed, so permissions stay aligned with the actual job.

3. Leaver. On the termination date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Concurrent employments are taken into account, so an account is only disabled when the last active employment ends.

Example: A logistics company runs Employee Central and an on-premise AD across three sites. It hires a warehouse planner with a start date next Monday. Joinly reads the effective-dated record, and on Monday morning the AD Agent creates the user in the Site-A > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Warehouse-Operations group. When the planner later moves to dispatch, the agent moves the object to the new OU and swaps the groups the same day.

What manual AD account management costs

Without automation, every account starts as a SuccessFactors ticket that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Microsoft's Entra provisioning agent can push SuccessFactors data to on-premise AD, but it offers limited mapping, no role-to-group logic and the same effective-dating and concurrent-employment gaps, so the decisions still fall to people.

• Onboarding delays. New joiners wait for an AD account and group access while a ticket sits in a queue, losing productive days in their first week.

• Permissions that don't keep up (privilege creep). When movers change position, old security-group membership often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren't disabled on time are a security and audit risk — and with concurrent employment it is easy to disable an account while another employment is still active.

Joinly vs. the Entra provisioning agent for AD

Microsoft's Entra provisioning agent can write SuccessFactors data to on-premise AD, but it stops short of the part that actually decides access. Here's how the two compare for an Employee Central-driven AD setup.

Watch-outs when connecting SAP SuccessFactors to Active Directory

A few details decide whether this connection stays reliable at scale.

• sAMAccountName uniqueness and length. AD limits the sAMAccountName to 20 characters and it must be unique across the domain. Joinly builds it from your rules with a fallback pattern, so duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from foundation objects. Legal entity, business unit, division and department don't map one-to-one to your OU structure. Joinly builds explicit rules that place each user — and move them on a transfer — into the correct OU.

• Effective-dated future hires. Employee Central stores a hire as a future-dated record before the first working day. Joinly reads the effective start date and has the agent create the account on the right day, not before.

• Concurrent employment. An employee can hold more than one active employment. Joinly applies rules to keep a single, stable AD object driven by the home employment, so a second assignment adds groups rather than creating a duplicate account.

• Service-account permissions. The agent acts under a service account with delegated rights. Joinly works with least-privilege delegation scoped to the target OUs, so the agent can create, move and disable users without domain-admin rights.

Joinly handles each of these by default with custom mapping and transformation.

Always audit-ready

Every account action the Joinly AD Agent performs is logged in the Joinly cloud: who was affected, when it happened, which OU and groups changed and which SuccessFactors change triggered it. For NIS2 that matters directly: access can be traced back to an authorised HR source rather than an ad-hoc request. Joinly is ISO 27001 certified, runs in an EU data centre in Amsterdam, applies least-privilege by default, and is built to meet NIS2 and ISO 27001.

Example case

A regional healthcare provider with around 2,400 employees across twelve locations ran Employee Central but still lived in an on-premise Active Directory for its clinical systems. Every new nurse, doctor or support worker started as a SuccessFactors ticket that IT processed by hand in AD — creating the object, choosing the OU, building the login, adding groups. With seasonal contracts and frequent internal transfers the queue never emptied, and new joiners regularly waited until day two or three for their account.

After connecting SAP SuccessFactors to Active Directory with Joinly, that work disappeared. The Joinly AD Agent now creates each user in the right OU on the start date, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer and disables accounts on the termination date with a 30-day grace window — all driven by the HR change in Employee Central.

"An account is simply ready in the right OU when the nurse walks in, transfers move themselves, and we can show the auditor exactly which SuccessFactors change created every bit of access." (Head of IT at a regional healthcare provider)

The result: onboarding time dropped from days to zero touch, privilege creep from old roles was eliminated, and the team walked into its last NIS2 assessment with a complete, source-backed audit trail.