Connect INAZ to Active Directory (on-premise)

How does Joinly sync INAZ to Active Directory?

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

1. Joiner. HR completes the hire in HR Inaz. Joinly reads the new resource’s dossier, determines the role from department, job title and cost centre, 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 start date recorded in INAZ.

2. Mover. When someone changes position, department or cost centre, 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 INAZ, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A grace window keeps the object recoverable in case of a quick rehire.

Example: A logistics and transport company runs HR Inaz and an on-premise AD across three depots. It hires a warehouse operative with a start date next Monday. Joinly reads the INAZ dossier, and on Monday morning the AD Agent creates the user in the Depot-North > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Warehouse-Operations group. When the operative 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 an INAZ 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. Because there is no native INAZ-to-AD path, even a home-built feed 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, 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 — especially when the only trigger is a manual note from HR that the person has left.

Joinly vs. the Entra provisioning agent for AD

There is no native INAZ-to-AD connector, so the realistic baseline is Microsoft’s Entra provisioning agent driven by a file feed. It can write attributes to on-premise AD, but it stops short of the part that actually decides access. Here’s how the two compare for an INAZ-driven AD setup.

Watch-outs when connecting INAZ 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 the organization chart. The INAZ organization chart, function charts and cost centres 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 standard provisioning API. INAZ does not publish a general-purpose provisioning API and its data path depends on how it is deployed. Joinly reads the structured export, database or middleware channel your instance exposes and drives the agent from it, so the lack of an API doesn’t block automation.

• Italian payroll fields. INAZ carries Italian-specific data such as CCNL contractual tables and the codice fiscale that you rarely want in AD. Joinly maps only the attributes you need, so the right fields reach AD and the rest stay in INAZ.

• 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 INAZ 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 and transport operator with around 1,800 employees across warehouses, depots and a head office in Italy, running HR Inaz but still living in an on-premise Active Directory for its warehouse and fleet systems. Every new driver, warehouse operative or dispatcher starts as an INAZ export line that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With shift work, seasonal peaks and frequent moves between depots the queue never empties, and new joiners wait until day two or three for their account.

Connect INAZ 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 HR Inaz.

“An account is simply ready in the right depot OU when the driver starts, moves between sites take care of themselves, and we can show the auditor exactly which INAZ change created every bit of access.” — Head of IT, logistics and transport operator

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.