How does Joinly sync Insperity to Active Directory?

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

1. Joiner. HR completes the hire in Insperity. Joinly reads the new record, determines the role from department, location and job title, 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 role, department or location, 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, keeping it recoverable for a set grace period before removal.

Example: A wholesale distribution company runs Insperity and an on-premise AD across three depots. It hires a warehouse coordinator with a start date next Monday. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Depot-A > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Warehouse-Operations group. When the coordinator later moves to purchasing, 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 Insperity 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. Microsoft’s Entra provisioning agent can push data to on-premise AD, but with Insperity you first have to build the client that feeds it, and it offers limited mapping, no role-to-group logic and no PEO awareness — 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 orphaned objects linger in the directory long after someone has left.

Joinly vs. the Entra provisioning agent for AD

Microsoft’s Entra provisioning agent can write data to on-premise AD, but with Insperity you build and maintain the client that feeds it, and it stops short of the part that actually decides access. Here’s how the two compare for an Insperity-driven AD setup.

Watch-outs when connecting Insperity 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 Insperity org data. Department, location and job title 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.

• Co-employment and the employer of record. Under Insperity’s PEO model it is the employer of record, so records can carry Insperity’s own legal-entity framing. Joinly maps each worksite employee into your own OU and group structure, so AD follows your organisation and not the PEO’s.

• Customer-only, API-key access. The Insperity API is available to customers only and secured with an API key. Joinly reads it as a read-only source of truth and never writes HR data back, so Insperity stays authoritative while the agent does the writing in 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 Insperity 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 wholesale distribution company with around 1,300 employees across a head office and several depots, running Insperity as its HR platform but still living in an on-premise Active Directory for its warehouse and ERP systems. Every new picker, driver or office worker starts as an Insperity export that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. Because Insperity is the employer of record, the records don’t line up neatly with the company’s own depot structure, and with seasonal peaks the queue never empties.

Connect Insperity to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right depot OU on the start date, builds a unique sAMAccountName, 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 Insperity and mapped to the company’s own structure rather than the PEO’s.

“An account is simply ready in the right depot OU when the coordinator walks in, transfers move themselves, and we can show the auditor exactly which Insperity change created every bit of access.” — Head of IT, wholesale distributor

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.