How does Joinly sync Partena Professional to Microsoft Entra ID?

Joinly reads each HR change from your Partena payroll administration and applies it to the matching Entra ID account automatically. Partena holds the authoritative employment record — contract, function, joint committee and start and end dates — so it is the starting point for each identity action.

1. Joiner. The employee is set up in Partena and declared to the NSSO through Dimona. Joinly reads the new employment record, determines the role from attributes like department, function and cost centre, then creates the account in Entra ID, assigns the right licences and maps the person into the correct groups — timed to the contractual start date.

2. Mover. When someone changes function, department or cost centre in Partena, 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 the departure is recorded in Partena — the contract end and the Dimona out declaration — Joinly disables the Entra ID account automatically on the end date. No orphaned accounts stay active after someone has left, and no unused licences keep billing.

Example: A Belgian non-profit runs its payroll through Partena’s ProSalary and hires a project coordinator with a start date on the first of next month. Joinly reads the new employment record, waits until the start date, creates the Entra ID account, assigns a Microsoft 365 licence and adds the coordinator to the Programmes group. When the coordinator later moves from Programmes to Fundraising, Joinly swaps the groups the same day the change lands in Partena.

What manual user management costs

Without automation, every account starts as an email from the Partena payroll consultant or a line in a spreadsheet that IT works through by hand. Partena’s own platform integrations can import employee data into another HR tool, but they don’t create Entra ID accounts, map functions to groups or disable leavers — so the part that actually decides access still 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.

• Permissions that don’t keep up (privilege creep). When movers change function or department, 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 someone’s contract has ended.

Joinly vs. a Partena partner connector or manual export

Partena’s partner integrations import HR data into another HR tool, and a manual CSV/SFTP export gets data out — but neither provisions identities. Here’s how Joinly compares with the do-it-yourself alternatives for a Partena-driven setup.

Watch-outs when connecting Partena Professional to Microsoft Entra ID

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

• The data channel depends on your Partena setup. As a social secretariat, Partena surfaces employee data through ProSalary or ExpertSalary and its partner API, or through an export you arrange — the exact channel and cadence vary by contract. Joinly is built to read whichever channel your setup exposes, so provisioning doesn’t hinge on a single documented API.

• Payroll structure isn’t IT identity. Partena records are shaped for Dimona, DmfA and gross-to-net calculation, keyed on the worker number (matricule) and joint committee rather than on directory groups. Joinly builds explicit rules from department, function and cost centre to the correct Entra ID groups and licences, so role drives access.

• Bilingual names and diacritics. Values arrive in Dutch and French, often with accented characters. A naive rule produces inconsistent or colliding usernames. Joinly transliterates and applies custom transformation rules so every UPN is unique, clean and predictable from day one.

• Contract end vs. actual last day. The Dimona out and the contract end date drive offboarding. Joinly keys account disablement to the recorded end date, with an optional grace window, so access ends on the right day and not before or long after.

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 Partena Professional 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 non-profit in the social sector with around 900 employees across a head office and a dozen local branches, running its payroll through Partena’s ProSalary while its IT team still creates every account by hand. New social workers and support staff start as an email from the payroll consultant, and IT keys them into Entra ID one at a time — choosing groups, assigning a Microsoft 365 licence, matching Dutch and French names to a username. With short project contracts and frequent internal moves the queue never empties, and joiners often wait until day two or three for access.

Connect Partena Professional to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each change in the Partena payroll administration at the source and acts on it automatically: new hires have their account, licence and group access ready on their start date, moves between programmes swap the right groups the same day, bilingual names resolve to one clean UPN, and leavers are disabled on their contract end date with a 30-day soft-delete grace window.

“Onboarding used to be a stack of emails from our payroll consultant that we typed into Entra ID by hand. Now an account is simply ready on the start date, moves happen the same day, and we can show the auditor exactly which Partena change created every bit of access.” — Head of IT, social-sector non-profit

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