Connecting on-premises Active Directory to the HR system

What it is

If you run hybrid, with on-premises Active Directory next to Entra ID, you need an integration that can reach the local domain controller. Preferably without opening a port or setting up a VPN.

The account has to land in the right OU, with the right groups, and in a hybrid Exchange environment with a remote mailbox. Existing accounts have to be recognised, or duplicates appear.

How Joinly handles it

• The Joinly Agent is a light service in your own network that only makes outbound connections. No inbound port has to be opened and no VPN is needed.
• The AD account lands in the right OU, with name, UPN, email address, employee number, manager and the attributes from your mapping.
• Membership of on-premises groups follows the role.
• In a hybrid Exchange environment Joinly creates the remote mailbox.
• The same HR source can feed on-premises AD and Entra ID at the same time.
• Existing AD accounts are recognised and taken over, not created twice.
• On departure the AD account is disabled and group memberships lapse.

What KoppelHet does

KoppelHet has worked out per HR system how the integration with Active Directory runs, with the fields and the choices you make up front.

Common integrations

• Active Directory
• AFAS Profit
• Visma Raet YouForce
• HR2day
• Nmbrs
• Visma YouServe
• Workday
• Personio
• HiBob
• SAP SuccessFactors
• Nedap ONS

Customer case

DAEL Groep

Installation engineering

AFAS is the source for Active Directory and Entra ID. Accounts, email addresses and groups are created, updated and deactivated automatically based on HR changes.

“Thanks to KoppelHet's user comparison between the HR system and our AD, we quickly saw where AFAS and Microsoft differed.”

Read the customer story

Frequently asked questions

More on Identity and access management

Identity and access management: the overview