Can Hexnode integrate with a private on-premises Active Directory?Solved

Participant
Discussion
4 weeks ago Sep 15, 2026

We are testing an on-premises Active Directory setup for managed Windows devices. The AD environment is inside a private network and is only reachable through VPN; it is not exposed to the internet.

Can this kind of private/on-prem AD be integrated with Hexnode UEM? If yes, what is the recommended architecture? Do we need a connector, VPN, inbound firewall rule, or specific ports for Hexnode to communicate securely with the AD?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 15, 2026
Marked SolutionPending Review

Hello @wilma ,

Yes. A private, on-premises Active Directory can be integrated with Hexnode UEM without exposing the AD server to the public internet.

The recommended approach is to use the Hexnode AD Agent within your internal network. The AD Agent initiates communication outbound to Hexnode, so Hexnode does not need inbound access to your private AD environment. A site-to-site VPN from Hexnode to your network is not required for this integration.

Ensure the machine running the AD Agent can communicate with your domain controllers internally, and allow the following outbound traffic from the AD Agent machine:

  • Port 443 (TCP): Required for secure HTTPS communication with Hexnode services, including “hexnode.com”, “hexnodemdm.com”, and your Hexnode portal domain.
  • Port 8998 (TCP): Required for AD Agent service communication.
  • Port 53 (TCP/UDP): Required for DNS resolution so the agent can resolve and reach Hexnode services.

With this setup, your AD remains private while the agent securely syncs directory information with Hexnode UEM.

Regards,
Simon Scott
Hexnode UEM

Save