HR integrations
An HR integration for every client, whatever HR system they use
One client uses AFAS, the next Nmbrs and a third a system you have never heard of. For an MSP, that is normal. Joinly connects them all to Microsoft Entra ID or Active Directory in the same way.
The short answer
An HR integration connects your client's HR system to Microsoft Entra ID or Active Directory, so accounts automatically follow the HR data. Joinly has 78 ready-made HR integrations, including AFAS, Nmbrs, Visma YouServe and Youforce, Loket, HR2Day, BCS, Unit4 and SD Worx, and a generic integration for any system with an API or a reliable export. Microsoft itself only provides a ready-made HR integration for Workday and SAP SuccessFactors.
A different HR system at every client
An in-house IT department connects one HR system and is done. An MSP gets a different system with every new client, a different way of recording things and different fields. Solve that with a separate script per client and after a few years you are maintaining as many integrations as you have clients.
In Joinly you choose, per client, the integration that fits their HR system. The common Dutch and international systems are ready-made. If a system is not on the list, the generic integration works with any system that has an API or a reliable export. A client with two HR systems, or with a separate source for contractors, works too.
Which data comes across, and which does not
Joinly only retrieves what it needs to determine an account and the right access: employee number, name, start and end date, contact details, department, manager and role. Payroll and absence data stay in the HR system.
For your client, that makes for an easy conversation with the data protection officer, and for you an integration that knows no more than it needs to.
A trial run before anything changes
Switching on an HR integration for an existing environment is the most nerve-racking moment of an implementation. That is why you run a trial import first, a dry run. You see in advance which accounts would be created, changed or blocked, and you can go through it with your client as an Excel file.
Once the integration is live, a threshold stops an import that suddenly changes far more than you expect, for example after a mistake in the HR system. It only goes ahead once someone has looked at it.
To Entra ID, Active Directory or both
If your client works fully in the cloud, Joinly connects HR directly to Microsoft Entra ID. If your client still has an on-premises Active Directory or hybrid Exchange, the Joinly Agent runs there, with outbound traffic only: no VPN and no inbound port.
HR integrations
Frequently asked questions
Which HR systems does Joinly support?
78 HR systems with a ready-made integration, including AFAS, Nmbrs, Visma YouServe and Youforce, Loket, HR2Day, BCS, Unit4 and SD Worx. The full overview is on the integrations page.
What if my client's HR system is not on the list?
Then the generic integration works, for any system with an API or a reliable export.
Can a client have more than one HR system?
Yes. Joinly supports several HR sources at once, for example a separate source for contractors or for a subsidiary.
Which data does Joinly retrieve from the HR system?
Only what it needs to determine an account and the right access: employee number, name, start and end date, contact details, department, manager and role. Payroll and absence data stay in the HR system.
Doesn't Microsoft have its own HR integration?
Microsoft provides a ready-made HR integration for Workday and SAP SuccessFactors. For other HR systems, Microsoft offers a route where you build the integration that supplies the data yourself.
How long does connecting take?
That depends on the HR system and your client's environment. The lead time is mainly in getting access to the HR system and the Microsoft environment, and in the trial runs.
- Joinly for MSPsFor an MSP, every joiner and leaver at a client is a ticket, a checklist and work that is hard to bill for. Joinly picks up those changes from your client's HR system and handles accounts, groups, licences and access automatically. For all your clients, from one login, with each client in its own environment.
- Onboarding and offboardingAn onboarding checklist per client and an offboarding ticket that arrives too late: for most MSPs, that is the work that comes back most often. With Joinly it starts as soon as your client records an employee in HR, and it follows the whole lifecycle.
- Multi-tenant identity managementYou probably have tenant management sorted already. What most MSPs do not do from one place is keep track of who should have an account at each client. That is where Joinly sits alongside your existing tooling.
- Automation without scriptsMost MSPs already automate. A PowerShell script for new users, a Power Automate flow for a client who asked for one. That works, until another client comes along, an HR field changes or the engineer who wrote it leaves.
Account management for your clients as a standard service?
In an introduction we walk through how Joinly would work for your clients: which HR systems, which environments and where you want to start. We agree the terms of a partnership in the same conversation.
Book an introduction