How does Joinly sync TriNet to Active Directory?

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

1. Joiner. HR completes the hire in TriNet. Joinly reads the new worksite-employee record, determines the role from department, job title and location, 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.

2. Mover. When someone changes department, location 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 role is removed, so permissions stay aligned with the actual job.

3. Leaver. On the termination recorded in TriNet, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Because TriNet deactivates a terminated record rather than deleting it, Joinly reads the employment status, so the account is disabled on time rather than lingering.

Example: A manufacturing SMB runs TriNet and an on-premise AD across two plants. It hires a machine operator with a start date next Monday. Joinly reads the new worksite-employee record, and on Monday morning the AD Agent creates the user in the Plant-1 > Production OU, sets the sAMAccountName to a unique pattern, and adds the Production-Floor group. When the operator later moves to maintenance, 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 request from TriNet 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 custom script against the TriNet API can push data to AD, but it offers no role-to-group logic, no worksite-employee filtering and no status-aware offboarding, 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 — and because TriNet only deactivates terminated records rather than deleting them, a status-blind script can leave the AD account active.

Joinly vs. the Entra provisioning agent for AD

Microsoft’s Entra provisioning agent can write directory data to on-premise AD, but there is no first-party TriNet reader feeding it, so in practice you compare Joinly’s agent against a custom script against the TriNet API writing to AD. Here’s how the two compare for a TriNet-driven AD setup.

Watch-outs when connecting TriNet 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 TriNet attributes. TriNet’s department, location and job title don’t map one-to-one to your OU structure. Joinly builds explicit rules that place each worksite employee — and move them on a transfer — into the correct OU.

• Co-employment record retention. Because TriNet is a co-employer, a terminated worker’s record is deactivated for compliance rather than deleted. Joinly keys on the employment status so the AD account is disabled on the actual termination, not left active because the record still exists.

• Worksite employees vs the rest. Not every TriNet record should get an AD account — contractors and non-WSE entries often shouldn’t. Joinly filters by employment type and status, so only the right people get an object in your domain.

• 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 TriNet 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 manufacturing SMB with around 350 employees across two plants, running TriNet for HR but still living in an on-premise Active Directory for its shop-floor and ERP systems. Every new operator, technician or planner starts as a request from TriNet that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With shift patterns and frequent internal moves the queue never empties, and new hires wait until day two or three for their account.

Connect TriNet to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each worksite employee 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 when the TriNet status flips to terminated — with a 30-day grace window — all driven by the HR change in TriNet.

“An account is simply ready in the right OU when the operator clocks in for their first shift, moves between lines sort themselves out, and terminated staff are disabled on the leave date instead of hanging around because the record was only deactivated.” — IT Manager, manufacturing SMB

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.