How does Joinly sync Buddee to Microsoft Entra ID?

Joinly reads each HR change in Buddee through its REST API — using webhooks where available and a frequent scheduled read otherwise — and applies it to the matching Entra ID account automatically. Buddee holds the authoritative employee and employment record, so it is the starting point for every identity action.

1. Joiner. HR completes the hire in Buddee. Joinly reads the new employee and their active employment — including department, team, job title and the employment terms — and determines the role from those attributes. It then creates the account in Entra ID, assigns the right licences and maps the person into the correct groups, timed to the real contract start date.

2. Mover. When someone changes team, department or role in Buddee, or their contract is updated, 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 contract end date recorded in Buddee, Joinly disables the Entra ID account automatically. There are no orphaned accounts left active after someone has left, and a soft-delete grace window can retire the account safely a set number of days later.

Example: A restaurant group runs Buddee for its HR and payroll and hires a new shift manager with a contract starting next Monday. Joinly reads the employment record, waits until the start date, creates the Entra ID account, assigns a Microsoft 365 licence and adds the manager to the Venue-A and Shift-Leads groups. When that person later moves to a second venue, Joinly swaps the venue group the same day while keeping a single, stable account.

What manual user management costs

Without automation, every account starts as a message from HR or a line in a Buddee export that IT works through by hand. Buddee’s Microsoft and Google SSO make sign-in smooth, but they only authenticate accounts that already exist — creating, changing and disabling those accounts is still a manual job, or a script someone has to build and maintain against the API.

• 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 — painful in shift-based teams where day one is a working shift.

• Permissions that don’t keep up (privilege creep). When movers change team or role in Buddee, 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 — easy to miss when a contract simply ends in Buddee and nobody tells IT.

Joinly vs. a self-built Buddee API integration

Buddee gives you a REST API, webhooks and SSO, but no identity provisioning of its own. The realistic alternative is scripting the API yourself or relying on SSO alone. Here’s how that compares to Joinly.

Watch-outs when connecting Buddee to Microsoft Entra ID

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

• Read the employment, not just the employee. In Buddee the definitive contract dates and hours live on the active employment and its employment terms, not only on the employee record. Joinly reads the active employment so the real start and end dates drive provisioning, rather than the day someone was first entered.

• No native identity logic. Buddee is HR and payroll; it has no concept of a UPN, a unique login or Entra groups. Joinly adds explicit rules that turn department, team and job title into the correct groups and licences, so role drives access instead of manual assignment.

• SSO is not provisioning. Microsoft and Google SSO let existing users sign in, but they never create or disable an account. Joinly handles the actual lifecycle, so accounts appear and disappear in step with the Buddee record.

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

• Confirm the API scope up front. Buddee’s developer documentation is lean in places, so Joinly confirms the exact objects, fields and webhook events available on your tenant with Buddee support before go-live, and maps only what is verified.

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 Buddee 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 running around fifteen restaurants on Buddee, with roughly 900 employees and constant churn — seasonal hires, students, people moving between venues every few weeks. Buddee keeps HR and payroll tidy, but every new colleague still means someone in the small IT team creating a Microsoft account by hand, guessing which groups they need, and hoping the leaver list is up to date. New starters routinely work their first shift without a working login, and old accounts linger long after a contract has ended.

Connect Buddee to Microsoft Entra ID with Joinly and that work disappears. Joinly reads each HR change in Buddee at the source and acts on it automatically: new hires have their account, Microsoft 365 licence and group access ready on their contract start date, a move to another venue swaps the right groups the same day, and leavers are disabled on their contract end date with a 30-day soft-delete grace window.

“Our people start on a shift, not on a Monday at nine, so an account that isn’t ready is a real problem. Now it’s simply there when they arrive, and when a contract ends the account goes quiet on its own.” — Head of IT, restaurant group

The outcome this setup is designed for: onboarding drops from a manual queue to zero touch, stale accounts after busy seasons disappear, and the team can show exactly which Buddee change created every bit of access.