How does Joinly sync Darwinbox to Active Directory?

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

1. Joiner. HR completes the hire in Darwinbox. Joinly reads the new record, determines the role from business unit, department and designation, 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.

2. Mover. When someone changes designation, 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 exit date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Across multiple entities, an account is only disabled when the person has genuinely left the group, not on a transfer.

Example: A manufacturer runs Darwinbox and an on-premise AD across three plants. It hires a maintenance technician in the North plant business unit. Joinly reads the new record, and the AD Agent creates the user in the North > Maintenance OU, sets the sAMAccountName to a unique pattern, and adds the Plant-Maintenance group. When the technician later moves to the Central plant, 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 Darwinbox 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. A hand-built script can push Darwinbox data to on-premise AD, but it offers limited mapping, no role-to-group logic and leaves the extract and matching to you, 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 across multiple entities it is easy to miss a leaver in one business unit while another is still active.

Joinly vs. the Entra provisioning agent for AD

Microsoft’s Entra provisioning agent can write Darwinbox-sourced data to on-premise AD once you’ve built the reader, but it stops short of the part that actually decides access. Here’s how the two compare for a Darwinbox-driven AD setup.

Watch-outs when connecting Darwinbox 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 — or locale-specific characters from a multi-country Darwinbox rollout — never produce a collision or a truncated, unreadable login.

• OU placement from business unit. Business unit, department and designation 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.

• Full-load vs delta extract. The Darwinbox employee master API can return a full load or only records changed since a last-modified date. Joinly manages the extract window and matches each record to the existing AD object, so no change is skipped or reprocessed.

• Multi-entity employees. In a group with several Darwinbox entities the same person can appear under more than one business unit. Joinly applies rules to keep a single, stable AD object, so a transfer moves the object 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 Darwinbox 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 manufacturer with around 3,800 employees across four plants and a head office, running Darwinbox but still living in an on-premise Active Directory for its shop-floor and ERP systems. Every new operator, technician or engineer starts as a Darwinbox ticket that IT processes by hand in AD — creating the object, choosing the plant OU, building the login, adding groups. With shift-based hiring and frequent transfers between plants the queue never empties, and new joiners wait until day two or three for their account.

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

“An account is simply ready in the right plant OU when the technician clocks in, transfers between plants move themselves, and we can show the auditor exactly which Darwinbox change created every bit of access.” — Head of IT, industrial manufacturer

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.