How does Joinly sync Talentia to Active Directory?

Joinly reads each HR change in Talentia HCM in the cloud through its web-service or scheduled-extract interface, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Talentia holds the authoritative employment record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in Talentia. Joinly reads the new record, determines the role from department, position and cost center, 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, department, cost center or company, 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. Multi-company employments are taken into account, so an account is only disabled when the last active employment ends.

Example: A manufacturer runs Talentia and an on-premise AD across three plants. It hires a production planner with a start date next Monday. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Plant-A > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Production-Operations group. When the planner later moves to logistics, 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 Talentia 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. Because Talentia has no documented native identity API, teams often drive this from a manual CSV export, which offers no role-to-group logic and no OU rules, 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 in a multi-company group it is easy to disable an account while another employment is still active.

Joinly vs. the Entra provisioning agent for AD

There is no dedicated Talentia-to-AD connector, so the realistic alternatives are Microsoft’s Entra provisioning agent (which has no Talentia source of its own) or manual account creation from an export. Here’s how Joinly compares for a Talentia-driven AD setup.

Watch-outs when connecting Talentia 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, which is tight for accented names and double surnames. Joinly builds it from your rules with transliteration and a fallback pattern, so duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from the organisational model. Company, legal entity, organisational unit, department and cost center 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.

• No documented native identity API. Talentia does not publish a self-service REST or SCIM identity API, so the connection is built over its web services or scheduled extracts. Joinly establishes and maintains that interface and confirms the available fields per tenant, so the agent always has clean data to act on.

• Multi-company records. The same person can hold a role under more than one company in a Talentia group. Joinly applies rules to keep a single, stable AD object driven by the primary employment, so a second role adds groups 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 Talentia 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 Southern-European manufacturer with around 2,800 employees across three plants and two legal entities, running Talentia HCM but still living in an on-premise Active Directory for its shop-floor and ERP systems. Every new operator, planner or engineer starts as a Talentia ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups — because there is no connector, just an export. With seasonal contracts, plant-to-plant transfers and accented and double surnames, the queue never empties and new joiners wait until day two or three for their account.

Connect Talentia 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 from names with accents and two surnames, 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 Talentia.

“We used to rebuild the same spreadsheet import every week and still fix logins for accented and double surnames by hand. Now an account is simply ready in the right OU when the operator walks in, transfers move themselves, and we can show the auditor exactly which Talentia 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 roles is eliminated, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.