Skip to main content
Joinly by KoppelHet

On-premises Active Directory

Clients with on-premises Active Directory: the same lifecycle, without a VPN

Plenty of clients are not fully in the cloud. An Active Directory in the server cupboard, hybrid Exchange, an application that runs on AD groups: for many MSPs that is daily work. Joinly handles the same lifecycle there as in the cloud.

The short answer

For clients with on-premises Active Directory, you install the Joinly Agent in their network. The agent collects its instructions from Joinly and uses outbound traffic only, so you need no VPN and no inbound port. From HR, Joinly creates accounts in Active Directory, updates them, manages group memberships and creates the mailbox for hybrid Exchange. The agent works alongside Microsoft Entra Connect.

Plenty of clients are not cloud-only

A manufacturer with an application that runs on AD groups, a school with a local network, a healthcare organisation in the middle of a migration that will take a while yet. For an MSP, a client with on-premises Active Directory is the rule more than the exception, and that is exactly where account management is often still done by hand.

The Joinly Agent: outbound traffic only

The Joinly Agent runs as a service in your client's network. It asks Joinly what needs to happen and reports the result back. Because all traffic goes from inside to outside, you do not need to open a port or set up a VPN.

From HR, Joinly creates accounts in Active Directory and updates them according to that client's conventions, adds employees to groups and removes them, and creates the mailbox for hybrid Exchange. A workflow only moves on once the agent has reported that it worked.

De Joinly Agent die een hybride en on-premise Active Directory beheert

Alongside Entra Connect

Most clients with on-premises Active Directory already sync with Microsoft Entra ID through Entra Connect. That stays as it is. Joinly decides what needs to happen and carries it out in the source you point it to. Which way your sync runs, you decide per client.

On-premises Active Directory

Frequently asked questions

  • Does Joinly need a VPN or an inbound port?

    No. The Joinly Agent collects its instructions from Joinly and uses outbound traffic only.

  • Does Joinly work alongside Microsoft Entra Connect?

    Yes. Joinly carries out changes in the source you point it to, and you decide per client which way your sync runs.

  • Can Joinly manage groups in Active Directory?

    Yes. Joinly adds employees to groups in Active Directory and removes them, based on their role.

  • Does it work with hybrid Exchange?

    Yes. With hybrid Exchange, Joinly creates the mailbox through the agent.

  • What if the agent is briefly offline?

    Then the instructions wait until the agent is connected again. A workflow only moves on once the agent has reported the result back.

Account management for your clients as a standard service?

In an introduction we walk through how Joinly would work for your clients: which HR systems, which environments and where you want to start. We agree the terms of a partnership in the same conversation.

Book an introduction