How does Joinly sync SAP HCM to Active Directory?

Joinly reads each HR change in the SAP HCM infotypes in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. The PA infotypes hold the authoritative employment record and OM the org structure; the agent is the only component that touches your domain.

1. Joiner. HR runs the hire action in SAP HCM, writing IT0000, IT0001 and IT0002 against the new PERNR. Joinly reads those infotypes, determines the role from the OM position, org unit 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 (BEGDA).

2. Mover. When someone changes position, org unit or personnel area in SAP HCM, 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 leaving action recorded in IT0000, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Multiple PERNRs are taken into account, so an account is only disabled when the last active employment ends.

Example: A chemicals and process-industry company runs SAP ERP HCM on-premise and an on-premise AD across three sites. It hires a shift operator with a hire action effective next Monday. Joinly reads the effective-dated infotype, and on Monday morning the AD Agent creates the user in the Site-A > Operations OU based on the OM position, sets the sAMAccountName to a unique pattern, and adds the Plant-Operations group. When the operator later moves to maintenance, 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 an SAP HCM 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. There is no native path from on-premise SAP HCM to AD, so the alternative is a self-built Logic Apps pipeline and the Entra provisioning agent — limited mapping, no role-to-group logic and the same effective-dating and multiple-PERNR 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 in OM, 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 a second PERNR it is easy to disable an account while another employment is still active.

Joinly vs. the Entra provisioning agent for AD

There is no native connector from on-premise SAP HCM to AD, so the alternative is a self-built Azure Logic Apps workflow feeding the Entra provisioning agent, which writes to on-premise AD. Here’s how that compares to the Joinly AD Agent for a PA/OM-driven AD setup.

Watch-outs when connecting SAP HCM 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 the OM position. Org unit, position, cost center and personnel area 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 based on OM.

• Infotype effective dating. PA records carry a validity period (BEGDA/ENDDA) and a hire action is written before the first working day. Joinly reads the effective-dated infotype and has the agent create the account on the right day, not before.

• PERNR is not the person. A rehire or second assignment can give one individual more than one personnel number. Joinly ties the PERNRs to a single AD object driven by the primary 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 SAP HCM change — the infotype and PERNR — 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

Take a chemicals and process-industry company with around 3,500 employees across nine sites, running SAP ERP HCM on-premise but still living in an on-premise Active Directory for its plant and lab systems. Every new operator, engineer or lab technician starts as an SAP HCM ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With shift-work contracts and frequent transfers between plants the queue never empties, and new joiners wait until day two or three for their account.

Connect SAP HCM to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the start date based on the OM position, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer and disables accounts on the recorded leaving date with a 30-day grace window — all driven by the HR change in the SAP HCM infotypes.

“An account is simply ready in the right OU when the operator walks onto the site, transfers between plants move themselves, and we can show the auditor exactly which SAP HCM action created every bit of access.” — Head of IT, chemicals and process-industry company

The outcome this setup is designed for: onboarding drops from days to zero touch, privilege creep from old positions is eliminated, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.