Coming SoonThis integration is on our roadmap. Sign up to be notified when it launches.
Active Directory Integration

Sync On-Premises Active Directory with Siggly

Bridge the gap between your on-premises AD environment and cloud-based signature management. Siggly reads LDAP attributes to generate and deploy signatures for Outlook and Exchange users.

LDAP
Secure directory protocol support
15 min
Default sync interval
256-bit
AES encryption for cached data

What You Get with Siggly + Active Directory

LDAP Attribute Mapping

Map any AD attribute including custom fields to Siggly signature placeholders for fully dynamic signatures.

OU-Based Deployment

Assign signature templates based on Active Directory Organizational Units so each branch or department is handled automatically.

Scheduled Sync Agent

A lightweight sync agent runs on your network, pulling AD changes on a configurable schedule without opening inbound firewall ports.

On-Premises Data Control

User data never leaves your network until it is mapped to signature fields. The sync agent transmits only the attributes you authorize.

How to Connect Active Directory to Siggly

1

Install the Sync Agent

Download and install the lightweight Siggly sync agent on a server joined to your Active Directory domain.

2

Configure LDAP Connection

Provide the domain controller address, bind credentials, and base DN. The agent supports LDAPS for encrypted connections.

3

Map AD Attributes

Choose which AD attributes populate each signature field. Common mappings include displayName, title, telephoneNumber, and thumbnailPhoto.

4

Deploy Signatures to Exchange

Siggly pushes signatures to Exchange Online or on-premises Exchange via transport rules or direct mailbox injection.

"We still run on-prem AD with Exchange hybrid. Siggly is the only modern signature tool that met us where we are instead of forcing a full cloud migration first."

Thomas Bauer

Systems Administrator, Heidrich Manufacturing

Frequently Asked Questions

Does the sync agent require internet access?
The agent needs outbound HTTPS access to the Siggly cloud service. No inbound ports need to be opened on your firewall.
Can I filter which AD users are synced?
Yes. You can configure LDAP filters to include or exclude users based on OU, group membership, or any attribute condition.
Is the sync agent compatible with Windows Server versions?
The agent supports Windows Server 2016 and later. It runs as a Windows service and requires .NET Framework 4.7.2 or higher.
What if I also use Azure AD Connect?
If your AD syncs to Azure AD via AD Connect, you can use either the on-prem sync agent or the Azure AD integration. Using both is not required but both can coexist.

Connect Active Directory to Siggly

Deploy the sync agent and start generating email signatures from your on-premises directory data today.