How does Joinly sync Lessor to Active Directory?

Joinly reads each HR change from your Lessor employee master data in Emply People in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Lessor holds the authoritative employment record; the agent is the only component that touches your domain.

1. Joiner. HR registers the new medarbejder in Lessor. Joinly reads the new record, determines the role from afdeling and stilling, and instructs the AD Agent to create the user in the correct OU, build the sAMAccountName and UPN from your rules, and add the right security groups — timed to the registered start date.

2. Mover. When someone changes stilling or afdeling, Joinly tells the agent to move the user to the matching OU, swap security-group membership and update attributes. Access that no longer fits the new position is removed, so permissions stay aligned with the actual job.

3. Leaver. On the end date recorded in Lessor, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU, so access ends on the date HR recorded rather than whenever a ticket is processed.

Example: A Danish facility-services company runs Lessor and an on-premise AD across three regions. It registers a new cleaning-team supervisor with a start date next Monday. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Region-Vest > Facility OU, sets the sAMAccountName from a transliterated pattern so the Danish surname resolves cleanly, and adds the Facility-Supervisors group. When the supervisor later moves to another region, the agent moves the object to the new OU and swaps the groups the same day.

What manual AD account management costs

Without automation, every account starts as a message from payroll that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Because there is no native Lessor connector to AD, the usual fallback is a generic middleware export or Entra Cloud Sync, which push attributes but offer no role-to-group logic and leave Danish naming and CPR handling to people.

• Onboarding delays. New joiners wait for an AD account 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 stilling or afdeling, old security-group membership often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren’t disabled on time are a security and audit risk, and it is easy to lose track of an account once the payroll message has been filed away.

Joinly vs. the Entra provisioning agent for AD

There is no native Lessor connector to on-premise AD, so the usual path is Entra Cloud Sync or a generic middleware export writing to AD. That stops short of the part that actually decides access. Here’s how the two compare for a Lessor-driven AD setup.

Watch-outs when connecting Lessor to Active Directory

A few Lessor-specific details decide whether this connection stays reliable and compliant at scale.

• sAMAccountName uniqueness and length. AD limits the sAMAccountName to 20 characters and it must be unique across the domain — and Danish names with æ, ø, å plus common surnames make collisions likely. Joinly transliterates and builds the name from your rules with a fallback pattern, so duplicates never produce a collision or a truncated, unreadable login.

• OU placement from afdeling and stilling. Danish department and position structures don’t map one-to-one to your OU tree. Joinly builds explicit rules that place each user — and move them on a transfer — into the correct OU.

• CPR-nummer is sensitive data. The Danish CPR-nummer must never become a sAMAccountName, UPN or group name. Joinly keeps CPR inside Lessor as a matching key only and builds AD attributes from name and organisation data instead.

• Where the identity data lives. LessorLøn and Lessor5 are payroll-first; the identity-usable attributes generally sit in Emply People. Joinly reads from the right source, so AD reflects the HR record rather than the payroll run.

• Service-account permissions. The agent acts under a service account with delegated rights. Joinly works with least-privilege delegation scoped to the target OUs, so the agent can create, move and disable users without domain-admin rights.

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

Always audit-ready

Every account action the Joinly AD Agent performs is logged in the Joinly cloud: who was affected, when it happened, which OU and groups changed and which Lessor 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

Take a Danish facility-services company with around 1,800 employees across cleaning, catering and maintenance teams at dozens of client sites, running Lessor for payroll and Emply People as its HR core but still living in an on-premise Active Directory for its scheduling and access systems. Every new supervisor, coordinator or office worker starts as a payroll registration that IT then processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With high turnover and constant transfers between regions the queue never empties, and Danish surnames regularly break the login pattern.

Connect Lessor to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the start date, builds a unique transliterated sAMAccountName, adds the correct security groups, moves people on a transfer and disables accounts on the end date with a 30-day grace window — all driven by the HR change in Lessor, with the CPR-nummer kept safely inside the HR source.

“With our turnover the AD queue was never empty, and Danish names kept breaking the login rule. Now an account is simply ready in the right OU when someone starts, the name always resolves cleanly, and we can show the auditor exactly which Lessor change created every bit of access.” — Head of IT, facility-services provider

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.