How does Joinly sync Bizneo HR to Microsoft Entra ID?

Joinly reads each HR change in Bizneo HR through its REST API and applies it to the matching Entra ID account automatically. The Bizneo employee database holds the authoritative record, so it is the starting point for each identity action.

1. Joiner. HR completes the hire in Bizneo HR. Joinly reads the new employee record and determines the role from attributes like department, team and position. It then creates the account in Entra ID, assigns the right licences and maps the person into the correct groups — timed to the recorded start date.

2. Mover. When someone changes position, team, department or office in Bizneo HR, 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. On the end date recorded in Bizneo HR, Joinly disables the Entra ID account automatically. There are no orphaned accounts left active after someone has left, and a soft-delete grace window keeps the account recoverable for a set period before it is removed.

Example: A professional-services firm hires a consultant in Bizneo HR with a start date next Monday, in its Madrid office. Joinly reads the record, waits until the start date, creates the Entra ID account, assigns an Office E3 licence and adds the consultant to the Consulting-Madrid group. When that consultant later moves to the Barcelona office and a senior position, Joinly swaps the office and team groups the same day without breaking sign-in.

What manual user management costs

Without automation, every account starts as a Bizneo HR notification or a line in a spreadsheet that IT works through by hand. Because there is no ready-made Entra provisioning app for Bizneo, the alternative is usually a custom script against the API that moves a few attributes across but leaves role-to-group mapping, licence assignment and offboarding logic 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.

• Permissions that don’t keep up (privilege creep). When movers change position, team or office, 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 licences keep costing money long after someone has left.

Joinly vs. a native Entra integration for Bizneo HR

Because there is no dedicated Entra gallery app for Bizneo HR, the native route is Entra ID inbound provisioning built against the Bizneo API (plus Cloud Sync for AD). It can move attributes, but it stops short of the part that actually decides access. Here’s how the two compare.

Watch-outs when connecting Bizneo HR to Microsoft Entra ID

A few Bizneo-specific details decide whether this connection stays reliable at scale.

• Modular suite — know your source fields. Bizneo is a suite of independent modules, and not every customer licenses every one. The employee database is always the reliable source; fields from Time & Attendance, Performance or other modules are only present if you use them. Joinly maps against the employee record and pulls extra fields only where the module is active, so the sync doesn’t break when a module isn’t in play.

• Recruitment candidates vs. hired employees. Records in the ATS / recruitment module are candidates, not employees, and provisioning them would create accounts for people who were never hired. Joinly triggers account creation only when a person becomes a hired employee in the Bizneo employee database.

• Mapping department, team and position to Entra groups. Company, department, team and position don’t translate one-to-one to Entra ID groups. Joinly builds explicit mapping rules from Bizneo’s structure to the correct groups and licences, so role drives access rather than manual assignment.

• Keep Spanish HR data out of the directory. Bizneo holds Spain-specific payroll and compliance data (SEPE, TGSS filings, DNI/NIF). That data is HR-internal and should not flow to Entra ID. Joinly maps only the identity attributes you choose, so sensitive payroll fields stay in Bizneo.

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

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 Bizneo HR 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 professional-services firm with around 1,200 employees across offices in Madrid, Barcelona and Lisbon, running Bizneo HR as its HR core while account creation still happens by hand. Each new consultant, analyst or support hire starts as a message from HR that IT works through in Entra ID — creating the account, assigning a licence, adding the right groups. With frequent project moves between offices and a steady flow of new joiners, the queue never quite empties and people wait days for full access.

Connect Bizneo HR to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each HR change in Bizneo at the source and acts on it automatically: new hires have their account, Office licence and group access ready on their start date, moves between offices or positions swap the right groups the same day, and leavers are disabled on their end date with a 30-day soft-delete grace window.

“Onboarding used to be a queue of tickets every Monday morning. Now an account is simply ready on the start date, a move to another office just swaps the groups, and we can show exactly which Bizneo change created every bit of access.” — Head of IT, professional-services firm

The outcome this setup is designed for: onboarding drops from days to zero touch, privilege creep from old project roles stops, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.