How does Joinly sync Oracle EBS HR to Active Directory?

Joinly reads each HR change in Oracle E-Business Suite HRMS in the cloud — through the supported public APIs or a scheduled effective-dated extract — then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. EBS HRMS holds the authoritative person and assignment record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in EBS HRMS. Joinly reads the new person and assignment records, determines the role from HR organization, position and job, 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 assignment’s effective start date.

2. Mover. When someone’s assignment changes position, HR organization or legal entity, 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 assignment is removed, so permissions stay aligned with the actual job.

3. Leaver. On the termination date recorded against the assignment, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Multiple assignments are taken into account, so an account is only disabled when the person’s last active assignment ends.

Example: A regional utilities company runs EBS HRMS and an on-premise AD across three sites. It hires a grid technician with an effective start date next Monday. Joinly reads the DateTrack record, and on Monday morning the AD Agent creates the user in the Region-North > Field-Operations OU, sets the sAMAccountName to a unique pattern, and adds the Field-Ops group. When the technician later moves to the control room, 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 EBS HR ticket 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 PL/SQL extract or an Oracle Identity Governance connector can push EBS data to on-premise AD, but it offers limited mapping, no role-to-group logic and the same DateTrack and multiple-assignment 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 assignment, 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 assignments it is easy to disable an account while another assignment is still active.

Joinly vs. a custom EBS-to-AD extract

The usual on-premise alternative is a home-built PL/SQL / BI Publisher extract or an Oracle Identity Governance connector writing to AD. It can move EBS data across, but it stops short of the part that actually decides access. Here’s how the two compare for an EBS HRMS-driven AD setup.

Watch-outs when connecting Oracle EBS HR 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 work structures. Business group, legal entity, HR organization and position 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.

• DateTrack effective-dating. EBS HRMS stores a hire as a future-dated, effective-dated record before the first working day. Joinly reads the effective start date and has the agent create the account on the right day, not before.

• Multiple assignments. A person can hold more than one assignment, with one marked primary. Joinly applies rules to keep a single, stable AD object driven by the primary assignment, so a secondary assignment 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 Oracle EBS HR 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 regional utilities and energy company with around 3,200 employees across a head office and multiple field depots, running Oracle E-Business Suite HRMS but still living in an on-premise Active Directory for its operational and SCADA-adjacent systems. Every new technician, engineer or control-room operator starts as an EBS HR ticket that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With shift patterns and frequent internal transfers between depots the queue never empties, and new joiners wait until day two or three for their account.

Connect Oracle EBS HR to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the effective 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 EBS HRMS.

“An account is simply ready in the right OU when the technician walks in, transfers move themselves, and we can show the auditor exactly which EBS change created every bit of access.” — Head of IT, regional utilities company

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.