How does Joinly sync ADP Workforce Now to Active Directory?

Joinly reads each HR change in Workforce Now in the cloud through the ADP Worker Management API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Workforce Now holds the authoritative worker record; the agent is the only component that touches your domain.

1. Joiner. HR completes the new hire in Workforce Now. Joinly reads the new worker, determines the role from home department, business unit and job title, 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 hire date.

2. Mover. When an associate changes position, home department or business unit, 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. Multiple positions are taken into account, so an account is only disabled when the associate's last active position ends.

Example: A retail chain runs Workforce Now and an on-premise AD across dozens of stores. It hires a store associate with a hire date next Monday. Joinly reads the worker record, and on Monday morning the AD Agent creates the user in the Stores > North-Region OU, sets the sAMAccountName to a unique pattern, and adds the Store-Floor group. When the associate later picks up a second Position ID as a key-holder, the agent adds the key-holder group to the same object instead of creating a duplicate.

What manual AD account management costs

Without automation, every account starts as an ADP report that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. ADP offers no native path to on-premise AD; the gallery app is SSO only, so you either script exports yourself or buy a third-party sync bridge, and either way 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 associates 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 multiple positions it is easy to disable an account while another position is still active.

Joinly vs. a sync bridge for AD

ADP has no native on-premise AD provisioning, so the usual baseline is a third-party sync bridge that writes worker data to AD. Here's how that compares to Joinly for a Workforce Now-driven AD setup.

Watch-outs when connecting ADP Workforce Now 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 home department and business unit. ADP's home department and business unit don't map one-to-one to your OU structure. Joinly builds explicit rules that place each user — and move them on a job change — into the correct OU.

• Associate ID versus Position ID. An associate holds one identity but a separate Position ID per job. Joinly keys on the associateOID so a second position adds groups to a single AD object rather than creating a duplicate account.

• Certificate-based API onboarding. The link to ADP runs over mutual TLS with an X.509 certificate that expires. Joinly manages the certificate and flags rotation in advance, so the agent keeps receiving worker changes without an unexpected outage.

• 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 Workforce Now 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

Take a retail chain with around 4,500 employees across a few hundred stores, running Workforce Now but still living in an on-premise Active Directory for its point-of-sale and back-office systems. Every new store associate, supervisor or warehouse hand starts as an ADP report that IT processes by hand in AD — creating the object, choosing the store OU, building the login, adding groups. With heavy seasonal hiring and constant store-to-store moves the queue never empties, and new joiners wait until day two or three for their account.

Connect ADP Workforce Now to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right store OU on the hire date, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer between stores and disables accounts on the termination date with a 30-day grace window — all driven by the HR change in Workforce Now.

"An account is simply ready in the right store OU when the associate clocks in, transfers between stores move themselves, and we can show the auditor exactly which Workforce Now change created every bit of access." (illustrative — Head of IT, retail chain)

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