How does Joinly sync Sage HR to Active Directory?

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

1. Joiner. HR completes the hire in Sage HR. Joinly reads the new record, determines the role from team, position and job category, 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 team, position or manager, 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 Sage HR, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU, so no login stays active after someone has left.

Example: A retail SMB runs Sage HR and an on-premise AD across its head office and stores. It hires a store supervisor with a start date next Monday, in the North-Region team. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Stores > North OU, sets the sAMAccountName to a unique pattern, and adds the Store-Supervisors group. When the supervisor later transfers to head office, 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 Sage 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. A CSV export or a third-party gateway can push some Sage HR data to AD, but it 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 team or 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 a shared login left active is exactly what an auditor flags.

Joinly vs. the Entra provisioning agent for AD

There is no Microsoft-published Sage HR provisioning app in the Entra gallery, so writing Sage HR data to on-premise AD normally means a third-party gateway plus the Entra provisioning agent, or a manual CSV. Both stop short of the part that actually decides access. Here’s how the two compare for a Sage HR-driven AD setup.

Watch-outs when connecting Sage 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 a flat org. Sage HR uses teams, positions and job categories rather than a deep hierarchy, so they 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.

• Modular subscription and available fields. Sage HR is a Core HR base with paid add-on modules, so which attributes the API returns depends on your subscription. Joinly maps only the fields that exist on your tenant and applies fallbacks, so a missing module field never leaves an AD attribute blank unexpectedly.

• API access and the admin-bound key. Sage HR’s API key is generated by an admin and is invalidated if that admin loses admin rights. Joinly connects with a dedicated, monitored credential and raises a warning immediately if the key is revoked, so provisioning never silently stops.

• 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 Sage 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 retail SMB with around 300 staff across a head office and a dozen stores, running Sage HR but still living in an on-premise Active Directory for its till, stock and back-office systems. Every new sales assistant, supervisor or office worker starts as a Sage HR notification that IT processes by hand in AD — creating the object, choosing the store OU, building the login, adding groups. With seasonal hiring peaks and frequent moves between stores the queue never empties, and new starters often wait until their second shift for an account.

Connect Sage HR to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right store 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 Sage HR.

“During the Christmas peak we used to hand-build dozens of store logins a week. Now an account is simply ready in the right store OU when the assistant starts their shift, transfers move themselves, and I can show the auditor exactly which Sage HR change created every login.” — IT Manager, retail company

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