How does Joinly sync Liantis to Microsoft Entra ID?

Joinly reads each change in your Liantis personnel file and applies it to the matching Entra ID account automatically. Liantis holds the authoritative employment record — the contract, the joint committee, the start and end date behind the Dimona — so it is the starting point for every identity action.

1. Joiner. HR records the new hire in Liantis and the Dimona is declared. Joinly reads the new employment record — name, job / function, joint committee, employee number and effective start date — and determines the role. It then creates the account in Entra ID, assigns the right licences and maps the person into the correct groups, timed to the effective start date rather than the moment the record was entered.

2. Mover. When someone changes job, department or contract in Liantis, Joinly updates their group membership, permissions and licences to match. Access that no longer fits the new position is revoked, so permissions stay aligned with the actual job.

3. Leaver. When Liantis records the end of the employment (the leaver Dimona / contract end), Joinly disables the Entra ID account automatically on the termination date. No orphaned accounts stay active after someone has left, and licences are freed up.

Example: A Belgian retail chain runs its payroll through Liantis and hires a store assistant with a start date next Monday. Joinly reads the employment record, waits until the effective start date, creates the Entra ID account, assigns a Microsoft 365 licence and adds the assistant to the Retail-StoreStaff group — while the rijksregisternummer stays in the HR record and never touches the login name.

What manual user management costs

Without automation, every account starts as an export from My Liantis or a message from the payroll administrator that IT re-keys into Entra ID by hand. Because Liantis is a social-secretariat and payroll system rather than an identity provider, there is no native connector that decides access for you — so the part that actually assigns groups and licences falls to people.

• Onboarding delays. New joiners wait for accounts, licences and group access while a request sits in a queue, losing productive days in their first week — often the busiest, in retail and services.

• Permissions that don’t keep up (privilege creep). When movers change job or store, old access often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren’t disabled on time are both a security and audit risk, and unused Microsoft 365 licences keep costing money after the contract has ended in Liantis.

Joinly vs. a manual Liantis export

Liantis has no native identity-provisioning connector for Entra ID, so the realistic alternative is a CSV/Excel export from My Liantis re-keyed by hand, or a generic unified-API connector wired up with custom scripts. Here’s how that compares to Joinly.

Watch-outs when connecting Liantis to Microsoft Entra ID

A few Liantis-specific details decide whether this connection stays reliable.

• Liantis is payroll-first, not an identity source. The personnel file is structured for the sociaal secretariaat — contract, joint committee, seniority — not for IT access. Joinly derives the role from job, paritair comité and cost data and builds explicit mapping rules to Entra ID groups and licences, so access follows the record rather than a manual decision.

• Start date behind the Dimona. The employment record and its official start are tied to the Dimona declaration, and the record can exist before the person’s real first working day. Joinly keys account creation to the effective employment start date, so access is ready on the right day and not before.

• The national number is sensitive. The rijksregisternummer (INSZ/NISS) uniquely identifies a person in Liantis but must never become a login attribute. Joinly uses it only for matching where appropriate and builds the UPN from name rules instead.

• UPN format with duplicate names. When two employees share a name, a naive UPN rule produces collisions. Joinly applies custom transformation rules — a suffix, site code or controlled tiebreaker — so every UPN is unique and predictable from day one.

• Data arrives via export or connector, not a live event stream. Liantis exposes the personnel file through the portal and available connectors rather than a rich real-time API. Joinly runs a frequent scheduled import and applies your mapping on top, so changes flow through reliably without assuming a webhook feed Liantis doesn’t publish.

Joinly handles each of these by default with custom mapping and transformation.

Always audit-ready

Every account action Joinly performs is logged: who was affected, when it happened, which access changed and which Liantis 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

Picture a Belgian retail chain with around 1,800 employees across 90 stores, running its payroll through Liantis while IT still creates every account by hand. The store managers hire constantly — students, seasonal staff, replacements — and each new name arrives as an export from My Liantis or a note from the payroll administrator that someone re-keys into Entra ID. New joiners routinely wait until their second or third shift for a working login, and when a contract ends in Liantis the Microsoft 365 account often stays active for weeks.

Connect Liantis to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each change in the Liantis personnel file at the source and acts on it automatically: new hires have their account, licence and group access ready on their effective start date, job or store changes swap the right groups the same day, and leavers are disabled on the contract end date with a 30-day soft-delete grace window — with the rijksregisternummer never leaving the HR record.

“We were re-typing every new starter from a Liantis export, and losing track of leavers. Now an account is simply ready on the first shift and gone when the contract ends, and we can show exactly which Liantis change created it.” — Head of IT, retail chain

The outcome this setup is designed for: onboarding drops from days to zero touch, leaver accounts and licences are cleaned up on time, and the team has a complete, source-backed audit trail for its next NIS2 assessment.