How does Joinly sync Fluida to Microsoft Entra ID?

Joinly reads each change in Fluida through the API and applies it to the matching Entra ID account automatically. The Fluida people directory holds who works where — in which Sede, Reparto and Team — so it is the starting point for each identity action.

1. Joiner. HR adds the person in Fluida and assigns them to a Sede, Reparto and Team. Joinly reads the new record on its next sync, determines the role from those fields, then creates the account in Entra ID, assigns the right licences and maps the person into the correct groups.

2. Mover. When someone changes Sede, Reparto or Team in Fluida, Joinly updates their group membership, permissions and licences to match. Access that no longer fits the new assignment is revoked, so permissions stay aligned with where the person actually works.

3. Leaver. When the person is set to leave in Fluida — or their end date passes — Joinly disables the Entra ID account automatically. No orphaned accounts are left active after someone has gone, and licences are freed up.

Example: A hospitality group runs Fluida for attendance and shifts across four hotels. It adds a new front-desk agent in Fluida, assigned to the Milano Sede and the Reception Reparto. On the next sync Joinly creates the Entra ID account, assigns a Microsoft 365 Business licence and adds the agent to the Milano-Reception group. When that agent later transfers to the Roma property, Joinly moves them out of the Milano groups and into the Roma ones the same day.

What manual user management costs

Without automation, every account starts as a message from HR — a line in a shift plan or a Fluida notification — that IT works through by hand. Fluida is excellent at attendance, shifts and leave, but it was never meant to drive Entra ID: there is no native connector, so the native alternative is to build a SCIM client against Microsoft’s API-driven inbound provisioning yourself. Until then, the part that actually decides access falls to people.

• Onboarding delays. New joiners — often frontline staff who need access on day one of a shift — wait for accounts, licences and group access while a request sits in a queue.

• Permissions that don’t keep up (privilege creep). When movers change Sede or Reparto, 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 — a real problem in high-turnover, shift-based teams.

Joinly vs. native Entra API-driven provisioning

There is no packaged Fluida connector for Entra ID. The native route is Microsoft’s API-driven inbound provisioning — you build and run a SCIM client that reads Fluida and bulk-uploads to Entra ID. Here’s how that compares to Joinly for a Fluida-driven setup.

Watch-outs when connecting Fluida to Microsoft Entra ID

A few Fluida-specific details decide whether this connection stays reliable in a shift-based, SME setting.

• Fluida is attendance-driven, not a full HRIS. Fluida models people through their Sede, Reparto and Team rather than a rich contract or position hierarchy. Joinly builds explicit rules from those fields to the right Entra groups and licences, so an attendance app becomes a reliable joiner-mover-leaver source.

• Frontline staff without a work email. In hospitality and other shift-based teams, many people are identified by badge or personal contact rather than a company mailbox. Joinly applies custom UPN rules — from name plus Sede code or a controlled tiebreaker — so every account still gets a unique, predictable sign-in.

• Read-only, scheduled sync. Fluida’s API is export- and integration-oriented, so Joinly connects with a Read Only API key and reads the directory on a frequent schedule rather than assuming push events. Provisioning stays current without ever writing back to Fluida.

• Mapping Sedi and Reparti to Entra groups. A Sede or Reparto doesn’t translate one-to-one to an Entra ID group. Joinly builds explicit mapping rules from those structures to the correct groups and licences, so role drives access rather than manual assignment.

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 Fluida 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 hospitality group with around 350 employees across four hotels, running Fluida for attendance, shifts and leave while its identity provisioning never quite keeps up. With high seasonal turnover and staff moving between properties, every new receptionist, housekeeper or kitchen hire is an email to IT — and with no native Fluida-to-Entra connector, accounts are created by hand, licences are guessed at, and leavers linger long after their last shift.

Connect Fluida to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each change in the Fluida people directory at the source and acts on it automatically: new hires have their account, Microsoft 365 licence and group access ready for their first shift, a move from one hotel to another swaps the right groups the same day, staff without a work email still get a unique, predictable UPN, and leavers are disabled with a soft-delete grace window.

“We hire in waves for the season, and IT used to be the bottleneck. Now a new receptionist is simply ready on their first shift, a transfer between hotels just swaps their access, and we can show exactly which Fluida change created every account.” — Head of IT, hospitality group

The outcome this setup is designed for: onboarding drops from days to zero touch, seasonal leavers are cleaned up automatically, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.