Identity and access management
Oracle HCM to Entra ID integration: Microsoft accounts from Oracle Fusion HR
With an integration between Oracle HCM Cloud and Microsoft Entra ID, every new employee hired in Oracle gets a Microsoft account with job title, department, line manager and licence. On a termination in Oracle sign-in is blocked on the last day, and a cancelled hire removes the prepared account again.
What the integration does
Organisations that run HR worldwide on Oracle HCM Cloud and manage Microsoft 365 per region often pass new Dutch colleagues to IT with an export from Oracle. If that export arrives once a week, a new colleague sometimes waits days for an account.
- HR completes the hire in Oracle, often weeks before the start date. Oracle reports the new employee.
- KoppelHet fetches the employee and creates the Microsoft account if they belong to the Dutch legal employer, with preferred name, job, department and line manager.
- The work address goes back to Oracle, so it is right in Oracle and in self-service.
- When job, department or manager change, details and groups in Entra ID follow.
- On the termination date KoppelHet blocks sign-in. If a hire is cancelled in Oracle, KoppelHet deletes the still unused account.
What to watch for with Oracle HCM Cloud and Microsoft Entra ID
- Oracle reports a new hire as soon as it is recorded with a future date. KoppelHet then prepares the account, so laptop and access are sorted before the first working day.
- Oracle has a separate notification for a cancelled work relationship, for example when a candidate drops out before the start. KoppelHet then deletes the prepared account, instead of blocking and keeping it as a leaver.
- In Oracle an employee can have several kinds of managers, such as a line manager and a project leader. Entra ID holds only one. KoppelHet takes the line manager of the primary assignment, so approvals and the Teams org chart point to the actual manager.
- On a transfer to another country Oracle creates a new work relationship with another legal employer. KoppelHet keeps the account tied to the person number, so the colleague keeps their mailbox, and only adjusts country, licence and entity.
- Oracle has a field for the preferred name next to the official first name. We use it in Entra ID, so Teams and Outlook show the name colleagues actually use.
- Oracle also reports changes for contingent workers. Whether they get an account is up to you; the worker type is passed to Entra ID, so access rules for contingent staff can differ.
- Worldwide all employees are in Oracle, while this Microsoft environment is only for the Netherlands. KoppelHet looks at the legal employer of the primary assignment and keeps the rest out of this tenant.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
How quickly does a new employee appear in Entra ID?
Within an hour of Oracle reporting the hire, usually well before the first working day.
Does this also work with Active Directory in our own network?
Yes, through a small program in your network.
We already have an integration platform. Does this fit alongside it?
Yes. This integration runs on the KoppelHet platform and asks nothing of your existing integration platform. Every action is in the audit logging, so operations and audit know what happened.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud is read through the employee Atom feeds newhire (also for a future-dated hire), empassignment, termination and cancelworkrelship, and then the workers resource with the child resources names (KnownAs), workRelationships, assignments and managers. The work address goes back through the emails child (POST or PATCH with EmailType). Feeds fire for employee, contingent worker and pending worker.
- Entra ID is written through Microsoft Graph (user) with employeeId (at most 16 characters), givenName, surname, jobTitle, department, companyName, manager, usageLocation, employeeType, employeeHireDate and accountEnabled; deletion on a cancelled hire. Integration user in Oracle with read access to feeds and workers and write access to email.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Microsoft Entra ID | Notes |
|---|---|---|
PersonNumber | employeeId | Per person, not per assignment; at most 16 characters |
KnownAs of FirstName | givenName | |
LastName | surname | |
Naamgevingsregel | userPrincipalName en mail | Goes back to Oracle as work email |
Job (primaire assignment) | jobTitle | |
Department | department | |
Legal employer | companyName | |
Line manager | manager | Line manager type only |
Land van de locatie | usageLocation | |
Worker type | employeeType | Employee or contingent worker |
Hire date | employeeHireDate |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud