How does Joinly sync rexx systems to Active Directory?

Joinly reads each HR change in rexx in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. rexx HR holds the authoritative personnel record; the agent is the only component that touches your domain. Because the rexx export is bulk-oriented, Joinly diffs each import to work out exactly what changed before the agent acts.

1. Joiner. HR completes the hire in rexx. Joinly reads the new record, determines the role from Abteilung, Position and Kostenstelle, 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 (Eintrittsdatum).

2. Mover. When someone changes position, department or location (Standort), 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 (Austrittsdatum), Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A grace window keeps the account recoverable for a set period before it is retired.

Example: A logistics company runs rexx and an on-premise AD across three sites. It hires a warehouse planner with a start date next Monday. Joinly reads the rexx record, and on Monday morning the AD Agent creates the user in the Site-A > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Warehouse-Operations group. When the planner later moves to dispatch, 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 rexx 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 plain rexx CSV export can list personnel, but it offers no role-to-group logic, no OU placement and no joiner/mover/leaver signal, 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 or location, 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 — easy to miss when the source only delivers a full export rather than a clear leaver signal.

Joinly vs. the Entra provisioning agent for AD

Microsoft’s Entra provisioning agent can write a CSV or API HR feed to on-premise AD, but it stops short of the part that actually decides access. Here’s how the two compare for a rexx-driven AD setup.

Watch-outs when connecting rexx systems 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 rexx org structures. Abteilung, Standort and Kostenstelle 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.

• Bulk export, not delta updates. The rexx API export is primarily one-directional and returns the full population with no native joiner/mover/leaver event. Joinly compares each import against its last known state, so the agent only creates, moves or disables the objects that actually changed.

• Module and tenant variations. rexx is modular and hosted in different ways, so the exact fields exposed differ per tenant and module mix. Joinly maps the fields you actually have via Liquid templates, so a local personnel number or a custom attribute still lands in the right AD attribute.

• 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 rexx 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 logistics company with around 2,600 employees across nine depots, running rexx systems but still living in an on-premise Active Directory for its warehouse and transport systems. Every new driver, planner or dock worker starts as a rexx ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With seasonal peaks and frequent moves between depots the queue never empties, and new joiners wait until day two or three for their account.

Connect rexx systems 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 exit date with a 30-day grace window — all driven by the HR change in rexx and the daily diff that turns the bulk export into precise actions.

“A new driver is simply ready in the right OU when the shift starts, moves between depots handle themselves, and we can show the auditor exactly which rexx change created every bit of access.” — Head of IT, logistics company

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.