Identity and access management
Hailey HR to Entra ID integration: users from Hailey, with work address and departure on the last working day
With an integration between Hailey HR and Microsoft Entra ID, every employee from Hailey gets a user in Entra ID, with name, work address, phone, job title, department, legal entity, location, start date, employee number and manager. KoppelHet creates the work address according to your naming rule, writes it back to Hailey and disables the account on the last working day.
What the integration does
Organisations that use Hailey HR and have Microsoft 365 as their workplace often still create accounts by hand, after HR has filled in a work address in Hailey.
- KoppelHet fetches the whole employee after each notification from Hailey.
- If the employee has no work address yet, KoppelHet makes it according to the naming rule and writes it back to Hailey.
- KoppelHet creates or updates the user in Entra ID and turns the teams into groups.
- For a departure on the last working day KoppelHet reads that date from Hailey and disables the account on that day.
- With on-premises Active Directory KoppelHet supplies the domain, through an agent in your network.
What to watch for with Hailey HR and Microsoft Entra ID
- Hailey does not create a new employee's work address itself. KoppelHet determines it according to your naming rule and puts it in Hailey through the API.
- If your accounts come from your own domain through Entra Connect, KoppelHet writes to Active Directory.
- Besides the last day of employment Hailey also has a last working day, which can be earlier because of holiday taken. KoppelHet disables on the last working day if you want that.
- An employee can have several job titles and teams in Hailey, and Entra ID has one field for the job title. KoppelHet picks the title you consider leading and turns the teams into groups in Entra ID.
- A notification from Hailey only contains the employee's ID. KoppelHet fetches the whole employee after each notification. What the API returns depends on the rights of the user behind the token, so that user only gets rights on the fields for the account.
- Hailey's API token is valid for a year and can be extended without changing. KoppelHet extends it in time, so the integration does not suddenly stop writing addresses back or disabling leavers after a year.
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
Does salary data go to Entra ID?
No. Only the fields for the account; KoppelHet's token user has no rights on salary.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Hailey HR API (v1) with a personal access token (valid for a year, extend through POST /PersonalAccessToken/Extend). GET /Employees (companyEmail, titleIds, teamIds, managerEmployeeId, employmentStatus, lastWorkingDay, lastDayOfEmployment), PUT /Employee/{employeeId}/CompanyEmail for the work address; webhooks with only employeeId or companyId. To Entra ID through Microsoft Graph (accountEnabled, groups) or API-driven inbound provisioning.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Hailey HR | Field in Microsoft Entra ID | Notes |
|---|---|---|
Company email | userPrincipalName en mail | |
Company email zonder domein | mailNickname | |
First name, last name, full name | givenName, surname, displayName | |
Work phone | businessPhones | |
Title | jobTitle | |
Department | department | |
Legal entity | companyName | |
Location | officeLocation | |
Employment number | employeeId | |
Manager | manager | |
Start date | employeeHireDate | |
lastWorkingDay | accountEnabled = false |
Related
Hailey HR → Active Directory
Hailey HR to Active Directory integration: domain accounts from Hailey, expiring on the last working day
Hailey HR → ADP iHCM
Hailey HR to ADP iHCM integration: approved salaries and end of employment to Dutch ADP payroll
Hailey HR → AFAS Profit
Hailey HR to AFAS integration: employment, scope and salary to Dutch payroll
Hailey HR → Arbodienst (SIVI)
Hailey HR to the occupational health service via SIVI: sick days from the Hailey calendar as absence reports