How does Joinly sync Oracle PeopleSoft to Microsoft Entra ID?

Joinly reads each HR change in PeopleSoft HCM through the Integration Broker’s web services and applies it to the matching Entra ID account automatically. PeopleSoft holds the authoritative Job Data record, so it is the starting point for each identity action.

1. Joiner. HR completes the hire in PeopleSoft with an Action of HIR on a new Job Data row. Joinly reads the person and their current (max-EFFDT/EFFSEQ) Job Data — Department, Business Unit, Location, Company and Position — determines the role, then creates the account in Entra ID, assigns the right licences and maps the person into the correct 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 updates their group membership, permissions and licences to match. Access that no longer fits the new position is revoked, so permissions stay aligned with the actual job rather than an old one.

3. Leaver. On the termination row (Action TER) in PeopleSoft, Joinly disables the Entra ID account automatically on the effective date. No orphaned accounts are left active after someone leaves, and where a person holds more than one Empl Record, access is only removed when the last active employment ends.

Example: A university hires a lecturer in PeopleSoft with a HIR row effective next Monday, in the Faculty of Science Business Unit. Joinly reads the effective-dated row, waits until the start date, creates the Entra ID account, assigns an Office E3 licence and adds the lecturer to the SCI-Staff group. When that lecturer later picks up a second, concurrent appointment on a new Empl Record in another department, Joinly keeps one stable account and adds the extra group without breaking sign-in.

What manual user management costs

Without automation, every account starts as a PeopleSoft ticket or a PS Query export that IT works through by hand. A raw Integration Broker feed or a partner ECMA connector can move attributes across, but it maps roles to groups through hand-built rules and stumbles on effective dating and multiple Empl Records — so the part that actually decides access still falls to people.

• Onboarding delays. New joiners wait for accounts, licences 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, department or Business Unit, old access often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren’t disabled on time are both a security and audit risk, and unused licences keep costing money — and with multiple Empl Records it is easy to disable an account while another appointment is still active.

Joinly vs. a custom PeopleSoft Integration Broker feed

There is no Microsoft Entra gallery app for PeopleSoft, so the native path is a custom Integration Broker service (or an Entra ECMA / IGA connector). That is a fine baseline for moving attributes, but it stops short of the part that actually decides access. Here’s how the two compare for a PeopleSoft HCM-driven setup.

Watch-outs when connecting Oracle PeopleSoft to Microsoft Entra ID

A few PeopleSoft-specific details decide whether this connection stays reliable at scale.

• Effective-dated future rows (EFFDT / EFFSEQ). PeopleSoft stores a hire or transfer as a future-dated Job Data row, and the current state is the max-EFFDT/EFFSEQ row as of today. Reading naively provisions too early or picks the wrong row. Joinly reads the effective row and times account creation to the EFFDT, so access is ready on the right day and not before.

• Integration Broker setup. Data only flows once the Integration Broker is configured — gateway, nodes, and the service operations or Component Interfaces that expose Job Data. Joinly works with your existing services or the delivered CIs, so you connect to what PeopleSoft already publishes instead of building a bespoke feed from scratch.

• EMPLID is the key, not the login. PeopleSoft identifies a person by EMPLID, which is not the Entra ID UPN. Joinly maps EMPLID to a stable, unique UPN and keeps that link across rehires and transfers, so a person is never duplicated and never loses their account on a job change.

• Multiple Empl Records. A person can hold more than one job at once, each on its own Empl Record (EMPL_RCD, starting at 0). Joinly applies explicit rules to pick the driving employment for the account while still reflecting the extra access, so a second appointment adds groups rather than a second account.

• Mapping PeopleSoft structures to Entra groups. Business Unit, Department, Location, Company and Position don’t translate one-to-one to Entra ID groups. Joinly builds explicit mapping rules from those structures to the correct groups and licences, so role drives access rather than manual assignment.

Joinly handles each of these by default with custom mapping and transformation.

Always audit-ready

Every account action Joinly performs is logged: who was affected, when it happened, which access 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

Picture a university with around 9,000 staff and a long-standing on-premise PeopleSoft HCM as its system of record, while its identity provisioning never quite keeps up. There is no gallery app to lean on, so a home-grown Integration Broker export feeds a nightly script — which handles the simple cases but breaks on the rest: future-dated academic appointments provision the moment HR keys the row rather than on the start date, and staff with a second Empl Record in another faculty end up with the wrong employment driving their account.

Connect Oracle PeopleSoft to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each Job Data change at the source and acts on it automatically: new hires have their account, Office licence and group access ready on the effective start date, transfers between Business Units swap the right groups the same day, a second appointment simply adds access on one stable account, and leavers are disabled on the termination row with a 30-day soft-delete grace window.

“We used to babysit a script that read PeopleSoft every night and still got future-dated hires and second appointments wrong. Now an account is simply ready on the start date, a second Empl Record just adds access, and we can show the auditor exactly which Job Data change created every bit of access.” — Head of IT, higher-education institution

The outcome this setup is designed for: onboarding drops from days to zero touch, effective-dating and multiple-appointment errors stop entirely, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.