| Product Documentation
ExSign
Firewall Ports You'll Need Open in M365
If You Have No Local Active Directory
This is the common case for M365-only environments. ExSign Admins authenticate through Azure instead (see Configuring Your Environment), so there's no Active Directory to reach and no LDAP ports needed at all.
|
Port |
Protocol |
Direction |
Purpose |
| 443 | HTTPS | Inbound to the Portal | Admins reaching the Portal to view or manage signature rules. |
| 8776 | API Hub | Bi-directional, between Portal and Microsoft 365 Agent | Same coordination channel used across all of ExSign's products. |
| 25 | SMTP | Outbound from the Microsoft 365 Agent | The Agent's own SMTP service, used to communicate with Microsoft 365 (see also System Requirements & Prerequisites (M365) for the FQDN/localhost distinction) |
| 1433 |
MSSQL | Inbound to SQL Server, from the Portal | Same as ExSign's other products. |
If You Do Have a Local Active Directory
If you do have a local Active Directory and want ExSign Admins to authenticate against it, the same ports required for ExSign for Exchange will apply. Choosing AD Group Auth instead of Azure Auth means the Portal needs to reach that Active Directory; the same additional ports required for ExSign for Exchange apply here, i.e., 389/636 (LDAP/LDAPS) and 3268/3269 (Global Catalog), bi-directional between the Portal and its authentication AD. See Firewall Ports You'll Need Open (Exchange) for the full breakdown of those.