How does Joinly sync Cornerstone OnDemand to Active Directory?

Joinly reads each change in Cornerstone in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Cornerstone holds the talent record and its Organizational Units; the agent is the only component that touches your domain — and Joinly does the translation from Cornerstone OU to AD OU for you.

1. Joiner. A new user appears in Cornerstone with their Organizational Units set. Joinly reads the record through the Edge API, determines the role from Division, Position and Cost Center, and instructs the AD Agent to create the user in the correct Active Directory 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 Position, Division or Location in Cornerstone, Joinly tells the agent to move the user to the matching AD 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. When a user’s status moves to inactive or their end date passes in Cornerstone, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Matching runs on the internal Cornerstone userId, so a recycled username never disables the wrong object.

Example: A government agency runs Cornerstone OnDemand for training and an on-premise AD across three regional offices. It onboards a policy officer with a start date next Monday, placed in the Cornerstone Division ‘Regulatory Affairs’ and Location ‘North Office’. Joinly reads the record, and on Monday morning the AD Agent creates the user in the AD OU ‘OU=North,OU=Regulatory,DC=agency,DC=gov’, sets a unique sAMAccountName, and adds the Reg-Affairs group. Note the two OUs in play: the Cornerstone Division is the source signal; the AD OU is where the object actually lives — Joinly maps one to the other.

What manual AD account management costs

Without automation, every account starts as a Cornerstone export that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the AD OU, building the sAMAccountName, adding groups. With no supported native Cornerstone-to-AD provisioning path left, the decisions all fall to people, and the Cornerstone-OU-versus-AD-OU naming clash makes the manual mapping easy to get wrong.

• 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 Division, 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 username-based match can disable the wrong object when a Cornerstone login was recycled.

Joinly vs. manual AD provisioning for Cornerstone

There is no supported native Cornerstone-to-on-premise-AD provisioning path, so the realistic alternative is a flat-file export and manual work in ADUC, or a generic connector. Here’s how that compares with Joinly for a Cornerstone-driven AD setup.

Watch-outs when connecting Cornerstone OnDemand to Active Directory

A few details — one of them a genuine naming trap — decide whether this connection stays reliable at scale.

• Cornerstone OU is not an Active Directory OU. Cornerstone calls its Division, Position, Location, Cost Center and Grade containers ‘Organizational Units (OUs)’ — the exact same term Active Directory uses for the containers that hold objects. They are unrelated. Joinly treats the Cornerstone OU as a source signal and maps it to a target AD OU through explicit rules, so the naming clash never causes a user to land in the wrong container.

• Three identifiers that don’t auto-map. Cornerstone’s internal userId, the login username and the SSO subject are three separate identifiers, and none derives from the others. Joinly keys the AD object on the stable userId and maintains the mapping, so a renamed username never detaches the sAMAccountName from the right person.

• Cornerstone may not be your source of truth. Cornerstone is talent/learning-first and its OU data is often fed from an upstream HRIS. Joinly lets you set which feed is authoritative per attribute, so weaker Cornerstone values don’t overwrite better data before the agent writes it to AD.

• 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.

• Service-account permissions. The agent acts under a service account with delegated rights. Joinly works with least-privilege delegation scoped to the target AD 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 AD OU and groups changed and which Cornerstone 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 government agency with around 3,500 staff across regional offices, running Cornerstone OnDemand for mandatory training but still living in an on-premise Active Directory for its case-management systems. Every new officer starts as a Cornerstone export that IT processes by hand in AD — creating the object, choosing the AD OU, building the login, adding groups. The team has been bitten more than once by the OU naming trap, dropping a user into an AD container that merely shared a name with their Cornerstone Division.

Connect Cornerstone OnDemand to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right AD OU on the start date — mapped explicitly from the Cornerstone OU, never confused with it — 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 matched on the stable Cornerstone userId.

“We kept dropping people into the wrong AD container because a Cornerstone Division and an AD OU happened to share a name. Joinly maps one to the other explicitly, the account is ready in the right place on day one, and we can show the auditor exactly which Cornerstone change created every bit of access.” — Head of IT, government agency

The outcome this setup is designed for: onboarding drops from days to zero touch, the Cornerstone-OU-versus-AD-OU mix-ups stop entirely, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.