How does Joinly sync Bizneo HR to Active Directory?

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

1. Joiner. HR completes the hire in Bizneo HR. Joinly reads the new employee record, determines the role from department, team and position, 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 recorded start date.

2. Mover. When someone changes position, team, department or office, 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 end date recorded in Bizneo HR, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU, so no orphaned accounts stay active after someone leaves.

Example: A manufacturer runs Bizneo HR and an on-premise AD across three plants. It hires a maintenance technician with a start date next Monday. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Plant-North > Maintenance OU, sets the sAMAccountName to a unique pattern, and adds the Maintenance-Shift group. When the technician later moves to the quality team, 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 Bizneo HR notification that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Because there is no ready-made connector for Bizneo, the alternative is a custom script plus Entra Cloud Sync, which offers limited mapping and no role-to-group logic, so the decisions still fall to people.

• Onboarding delays. New joiners wait for an AD account and group access while a request sits in a queue, losing productive days in their first week.

• Permissions that don’t keep up (privilege creep). When movers change position or team, 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 a path into your network long after someone has gone.

Joinly vs. the Entra provisioning agent for AD

Because there is no dedicated connector for Bizneo HR, the native route to on-premise AD is a custom API integration feeding Entra Cloud Sync or the Entra provisioning agent. It can write data to AD, but it stops short of the part that actually decides access. Here’s how the two compare.

Watch-outs when connecting Bizneo HR 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 Bizneo structure. Company, department, team and office 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.

• Recruitment candidates vs. hired employees. Records in Bizneo’s ATS / recruitment module are candidates, not employees. Joinly triggers AD object creation only when a person becomes a hired employee in the employee database, so candidates never get accounts.

• Modular suite — know your source fields. Not every customer licenses every Bizneo module. Joinly maps against the always-present employee record and pulls extra fields only where the relevant module is active, so the sync doesn’t break when a module isn’t in play — and Spanish payroll data (SEPE, TGSS, DNI/NIF) stays out of AD.

• 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 Bizneo HR 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 2,000 employees across three plants, running Bizneo HR but still living in an on-premise Active Directory for its shop-floor and ERP systems. Every new operator, technician or supervisor starts as a Bizneo HR notification that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With shift patterns, seasonal contracts and frequent moves between plants, the queue never empties and new joiners wait until day two or three for their account.

Connect Bizneo HR 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 end date with a 30-day grace window — all driven by the HR change in Bizneo HR.

“An account is simply ready in the right OU when the operator clocks in, moves between plants sort themselves out, and we can show the auditor exactly which Bizneo change created every bit of access.” — Head of IT, manufacturer

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