How does Joinly sync Dayforce to Active Directory?

Joinly reads each HR change in Dayforce in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Dayforce holds a single combined HR and payroll record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in Dayforce. Joinly reads the new record, resolves the department, position and location XRefCodes to determine the role, 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 hire date.

2. Mover. When someone changes position, department or location, 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. Because Dayforce termination and AD deprovisioning are otherwise separate, Joinly is what guarantees the account is actually disabled when the last working day arrives.

Example: Illustrative: a regional grocery retailer runs Dayforce and an on-premise AD across its stores and a distribution centre. It hires a store associate with a hire date next Monday. Joinly reads the record, resolves the location and position XRefCodes, and on Monday morning the AD Agent creates the user in the Store-12 > Floor OU, sets the sAMAccountName to a unique pattern, and adds the Store-Associates group. When the associate later moves to a shift-lead position, 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 Dayforce 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. Aquera's connector or Microsoft's Entra provisioning agent can push Dayforce data to on-premise AD, but they offer limited mapping, no role-to-group logic and leave the termination-to-deprovisioning gap open, 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. Because a Dayforce termination doesn't disable the AD account by itself, accounts that aren't disabled on time are a security and audit risk — and a terminated worker can keep domain access for weeks.

Joinly vs. the middleware agents for AD

Aquera's connector and Microsoft's Entra provisioning agent can write Dayforce data to on-premise AD, but they stop short of the part that actually decides access. Here's how the two compare for a Dayforce-driven AD setup.

Watch-outs when connecting Dayforce 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 Dayforce structures. Legal entity, location, department and position 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.

• XRefCode resolution. Every Dayforce lookup is keyed by an XRefCode, and an invalid one returns a bare HTTP 400. Joinly resolves the right XRefCodes from the live tenant before the agent acts, so OU and group mapping doesn't fail silently halfway through a sync.

• Termination decoupled from deprovisioning. A Dayforce termination does not disable the AD account on its own. Joinly bridges the two, so the moment Dayforce records a termination date the agent disables the account — no terminated worker keeps domain access.

• gMSA permissions and Windows Server 2025. The agent runs as a Windows service under a group Managed Service Account (gMSA) that is automatically granted CreateChild, WriteProperty and Reset Password on the OUs you select — no domain-admin and no stored password. On Windows Server 2025 a default gMSA is rejected for still carrying RC4; the Joinly installer creates it AES-only and repairs existing accounts automatically.

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 Dayforce 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 regional grocery retailer with around 3,200 employees across fifty stores and a distribution centre, running Dayforce but still living in an on-premise Active Directory for its till, scheduling and warehouse systems. Every new store associate, cashier or picker starts as a Dayforce ticket that IT processes by hand in AD — creating the object, choosing the store OU, building the login, adding groups. With high seasonal turnover and constant store-to-store transfers the queue never empties, and new joiners wait until day two or three for their account.

Connect Dayforce 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 and disables accounts on the termination date with a 30-day grace window — all driven by the HR change in Dayforce.

"An account is simply ready in the right store OU when the associate clocks in, transfers move themselves, and a termination in Dayforce now actually closes the AD account instead of leaving it open for weeks."

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