Dayforce logoMicrosoft Entra ID logo

Identity and access management

Dayforce to Entra ID integration: Microsoft accounts for Dutch employees from Dayforce

With an integration between Dayforce and Microsoft Entra ID, new employees of the Dutch organisation in Dayforce get a Microsoft account with job, department, location and manager, and sign-in is blocked after the end date in Dayforce. Hires and terminations entered in advance are carried out on the right day.

What the integration does

Organisations that use Dayforce for HR in every country and manage their own Microsoft environment in the Netherlands receive new colleagues through a list from head office. Leavers sometimes only appear on it weeks later.

  1. KoppelHet asks Dayforce which employees of the Dutch organisation were updated, hired or terminated in the past window.
  2. For those employees KoppelHet fetches the details, as of the effective date.
  3. A new employee gets a Microsoft account before the start date with job, department, location, manager and licence.
  4. On a new work assignment or manager, details and groups in Entra ID follow.
  5. After the end date KoppelHet blocks sign-in and removes the employee from the groups.
Dayforce → KoppelHet → Microsoft Entra IDSOURCEDayforceTARGETMicrosoft Entra IDKoppelHetmapping · logging · monitoringDayforce → KoppelHet → Microsoft Entra IDSOURCEDayforceTARGETMicrosoft Entra IDKoppelHetmapping · logging · monitoring
Out: Microsoft account with XRefCode · Job, department and location from the primary work assignment · Manager · Groups and licence · Blocking after the end date

What to watch for with Dayforce and Microsoft Entra ID

  • Without a filter Dayforce always returns the whole population, and warns about this itself. KoppelHet only requests employees updated in the past window, limited to the parts that matter for Entra ID, such as work assignment, employment status and contact details.
  • A hire or termination is often entered weeks ahead in Dayforce. KoppelHet searches for them separately, on hire date and on end date, so the account is ready in time and blocked on the right day.
  • Dayforce holds managers per employee and per work assignment. Entra ID holds one manager; KoppelHet takes the manager of the primary work assignment, so approvals and the Teams org chart point to the day-to-day manager.
  • Dayforce often serves every country of a group, while this Microsoft environment is only for the Netherlands. KoppelHet only requests employees of the Dutch organisation unit and only has rights on that unit in Dayforce.
  • In Dayforce fields only come through if the API user's role has rights to them. KoppelHet checks after every fetch that job, department and manager are present, so a missing right does not silently produce empty fields in Entra ID.
  • Dayforce can record a single sign-on account per employee. If you have sign-in to Dayforce run through Microsoft, KoppelHet can write the Microsoft account back there, so a new colleague can also sign in to Dayforce on day one.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does the Dutch IT team need access to Dayforce?

No. KoppelHet works with a separate API user in Dayforce, created by head office with read-only rights on the Dutch unit.

Does this also work with Active Directory in our own network?

Yes, we build that integration too.

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.

  • Dayforce is read through the RESTful Web Services (https://www.dayforcehcm.com/api/{CompanyName}/V1/Employees) with filterUpdatedStartDate and filterUpdatedEndDate plus filterUpdatedEntities, filterHireStartDate and filterTerminationStartDate, and orgUnitXRefCode for the Dutch unit. Details per XRefCode with expand for WorkAssignments, EmploymentStatuses, EmployeeManagers, Contacts and SSOAccounts, and contextDate for the position on the effective date.
  • Entra ID is written through Microsoft Graph (user with employeeId, givenName, surname, userPrincipalName, jobTitle, department, officeLocation, usageLocation, manager, employeeType and accountEnabled).

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in DayforceField in Microsoft Entra IDNotes
XRefCodeemployeeIdFixed key; at most 16 characters
FirstName of CommonNamegivenName
LastNamesurname
NaamgevingsregeluserPrincipalName en mail
WorkAssignments (primair): JobjobTitle
WorkAssignments (primair): Departmentdepartment
WorkAssignments (primair): LocationofficeLocation en usageLocation
EmployeeManagersmanager
EmploymentStatusesemployeeTypeFor example permanent or temporary
Termination dateaccountEnabled = false

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.