How does Joinly sync Youforce to Active Directory?

Joinly reads each HR change from Youforce in the cloud through the IAM API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Youforce — running on HR Core Beaufort or HR Core Business — holds the authoritative employment record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in Youforce. Joinly reads the new Person, Employment and Assignment records, determines the role from the job profile, organization unit and role assignment, 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 employment start date.

2. Mover. When someone changes job profile, organization unit or manager, 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 employment end date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A soft-delete grace window keeps the object recoverable for a set period before it is retired.

Example: A care organisation runs Youforce on HR Core Business and an on-premise AD across several locations. It hires a nurse with a start date next Monday. Joinly reads the employment record, and on Monday morning the AD Agent creates the user in the Location-A > Care OU, sets the sAMAccountName to a unique pattern, and adds the Care-Staff group. When the nurse later transfers to another ward, 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 Youforce export that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. A generic IAM connector or file import can push Youforce data to AD, but it offers limited role-to-group logic and the same future-dating and per-core field 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 job profile or organization unit, 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 leave access open long after someone has gone.

Joinly vs. a generic Youforce IAM connector for AD

There is no first-party Microsoft provisioning app for Youforce, so the usual AD alternative is a generic IAM middleware on the Youforce IAM API or a legacy file import. Either can write data to on-premise AD, but stops short of the part that actually decides access. Here’s how the two compare for a Youforce-driven AD setup.

Watch-outs when connecting Youforce 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 organization unit. Job profile and organization unit 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.

• HR Core Beaufort vs HR Core Business fields. The two HR cores expose different field sets — cost center and company aren’t available on Beaufort. Joinly builds the mapping against the core you actually run, so nothing maps to an empty attribute.

• Manager and hierarchy from RoleAssignment. Youforce expresses manager and hierarchy through RoleAssignment and OrganizationUnit rather than a single manager field. Joinly resolves those relationships so the AD manager attribute and group mapping reflect the real reporting line.

• 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 Youforce 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 hospital with around 4,000 employees across several sites, running Youforce on HR Core Business but still living in an on-premise Active Directory for its clinical systems. Every new nurse, doctor or support worker starts as a Youforce export that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With rotating contracts and frequent internal transfers between wards the queue never empties, and new joiners wait until day two or three for their account.

Connect Youforce to Active Directory with Joinly and that work disappears. The Joinly AD Agent 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 employment end date with a 30-day grace window — all driven by the HR change in Youforce, with the manager resolved from the role assignment.

“An account is simply ready in the right OU when the nurse walks in, transfers between wards move themselves, and we can show the auditor exactly which Youforce change created every bit of access.” — Head of IT, hospital

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.