How does Joinly sync Oracle PeopleSoft to Active Directory?

Joinly reads each HR change in PeopleSoft HCM in the cloud through the Integration Broker, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. PeopleSoft holds the authoritative Job Data record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in PeopleSoft with a HIR row. Joinly reads the current Job Data — Department, Business Unit, Location and Company — determines the role, 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 effective date on the row.

2. Mover. When someone changes position, department, Business Unit or Company on a new effective-dated row, 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 row (Action TER), Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Multiple Empl Records are taken into account, so an account is only disabled when the last active appointment ends.

Example: A government agency runs PeopleSoft HCM and an on-premise AD across several regional offices. It hires a caseworker with a HIR row effective next Monday. Joinly reads the effective-dated row, and on Monday morning the AD Agent creates the user in the Region-North > Casework OU, sets the sAMAccountName to a unique pattern derived from the EMPLID mapping, and adds the Casework-Staff group. When the caseworker later transfers to policy, 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 PeopleSoft ticket or a PS Query 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. A home-grown Integration Broker feed can push PeopleSoft data toward AD, but it offers no role-to-group logic and the same effective-dating and multiple-Empl-Record gaps, 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 with multiple Empl Records it is easy to disable an account while another appointment is still active.

Joinly vs. the Entra provisioning agent for AD

There is no PeopleSoft gallery app, so the native path to on-premise AD is a custom Integration Broker feed or the Entra provisioning / ECMA agent. Either can write attributes, but it stops short of the part that actually decides access. Here’s how the two compare for a PeopleSoft-driven AD setup.

Watch-outs when connecting Oracle PeopleSoft to Active Directory

A few PeopleSoft-specific 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. EMPLID is the PeopleSoft key, not a login, so Joinly builds the sAMAccountName from your rules with a fallback pattern — duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from PeopleSoft structures. Business Unit, Department, Location and Company 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.

• Effective-dated future rows (EFFDT / EFFSEQ). PeopleSoft stores a hire or transfer as a future-dated Job Data row before the first working day. Joinly reads the effective row and has the agent create the account on the right day, not the moment HR keyed the row.

• Multiple Empl Records. A person can hold more than one job at once, each on its own Empl Record (EMPL_RCD). Joinly applies rules to keep a single, stable AD object driven by the primary appointment, so a second job adds groups rather than creating a duplicate account.

• 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 PeopleSoft 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 public-sector agency with around 3,500 employees across a head office and several regional locations, running PeopleSoft HCM as its system of record but still living in an on-premise Active Directory for its case-management and line-of-business systems. Every new caseworker, analyst or support officer starts as a PeopleSoft ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login from the EMPLID, adding groups. With rotations, secondments and frequent internal transfers the queue never empties, and new joiners wait until day two or three for their account.

Connect Oracle PeopleSoft 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 termination row with a 30-day grace window — all driven by the Job Data change in PeopleSoft.

“An account is simply ready in the right OU when the caseworker walks in, transfers move themselves, and we can show the auditor exactly which PeopleSoft Job Data change created every bit of access.” — Head of IT, public-sector agency

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.