Can Exclaimer really integrate with our existing setup? Answering IT’s top questions

Yes. Exclaimer supports:

• Microsoft 365 (server- and client-side)
• Google Workspace (via SMTP relay or Gmail add-on)
• On-premises Exchange and hybrid environments (using our Exchange Transport Agent)

Whether you're all-cloud or running a hybrid deployment, Exclaimer integrates directly with your infrastructure.

In hybrid deployments, emails can be routed through Microsoft 365 connectors or our Exchange Transport Agent depending on your configuration. This ensures that email signatures are applied consistently, regardless of where the mailbox is hosted or how email is routed.

Not for Microsoft 365 or Google Workspace.

For on-prem Exchange or hybrid setups, you’ll install a lightweight MSI-based Transport Agent (~20MB) on each mailbox server. The agent supports high availability environments and can be updated quarterly or on request via remote deployment.

No. Your mail flow stays exactly as it is.

Exclaimer uses TLS-secured smart connectors that operate within your existing routing and security stack—no need to reroute traffic externally.

Built-in options in Exchange Online support only plaintext disclaimers and lack templating, mobile compatibility, and previews. They also don’t support dynamic field insertion, extensive targeting rules, or audit logging, and aren’t user-friendly on mobile or web.

Exclaimer delivers across all these gaps with consistent branding, contextual logic, and full visibility.

Yes. Exclaimer syncs automatically with:

• Microsoft Entra ID (Azure AD) via Graph API
• Google Directory via secure OAuth
• LDAP for on-prem or hybrid setups

We pull only the fields needed for email signature assignment such as name, title, and department. Directory sync occurs every 30 to 60 minutes (customizable), and we support custom fields and extended attributes.

Whether you're cloud-native or mid-migration, Exclaimer fits into your environment without disrupting mail flow.

Exclaimer uses a text-match check mechanism when both client-side and server-side signatures are applied.

If a client-side signature is already in the email, the system will skip server-side application—preventing duplicates and preserving message integrity.

Yes. Exclaimer is independently certified to:

• SOC 2 Type II
• ISO/IEC 27001 and ISO/IEC 27018
• Cyber Essentials
• CSA (Cloud Security Alliance)

We’re the only vendor in our space with Microsoft 365 Certification, which confirms our integration has passed Microsoft’s cloud security and compliance benchmarks—including data handling, access control, and infrastructure resilience.

We also hold a SecurityScorecard rating of 99/100 (A)—a trusted metric for procurement and vendor risk teams.

Third-party penetration tests are performed annually, with summaries available via our Trust Portal.

Only what’s needed to apply a signature:

• Name, title, phone number, email, etc.

We don’t process or store message content. Data is encrypted and stored in 14 regional Microsoft Azure datacenters, with replication across paired zones for high availability and compliance (GDPR, CCPA, ADGM, DIFC).

Yes. With client-side deployment, signatures are applied before the email is sent—right inside Outlook or Gmail.

No external routing, no added latency, and the sender can see their email signature before hitting send.

Yes. We support:

• Single sign-on via Microsoft, Google, and SAML providers
• Multi-factor authentication at the portal level

Passwords aren’t stored, and authentication tokens are encrypted end-to-end.

• Microsoft 365 or Google Workspace: ~1 hour
• Exchange hybrid: ~1–2 hours (including agent install)

Deployment is quick, and you can roll out to pilot groups before going organization-wide.

Yes. Target users, groups, or OUs to validate logic, preview layouts, and test campaign settings before publishing company-wide.

If you use centralized mail transport, setup must follow this order:

• Install the Exchange Transport Agent on-prem
• Configure the hybrid send connector in Microsoft 365 to use a rule with lower priority
• Add an exception via message header (e.g., X-SentonPremise) to avoid routing loops

This ensures your Exclaimer rule runs before the transporter takes over, guaranteeing email signatures apply correctly in all paths.

Yes. Server-side signatures are applied centrally, so users get consistent branding no matter where they send from—mobile, desktop, webmail, shared or delegated inboxes.

Yes. Our optional Sent Items Update feature ensures sent messages display the full, final signature using Microsoft Graph API or EWS. It’s scoped by admin consent and doesn’t affect mail delivery times.

Yes. You can build rules based on:

• Department, job title, or location
• Domain or business unit
• Language preference or region

Rules support nested logic and priority ordering. For example:

“Apply Signature A if user is in Sales and based in New York and sending externally.”

Yes. With role-based access control, you can:

• Let Marketing update banners or layout content
• Give Compliance oversight of disclaimers
• Keep IT in full control of deployment, security, and governance

Everyone gets what they need without cross-team friction.

Yes. Changes take effect instantly once published across the entire organization or for selected users.

Yes. Assign unique templates by:

• Email domain
• Department or location
• Brand or business unit

Each team or brand can have its own visual identity and regional disclaimers.

Exclaimer automatically applies the right signature based on synced directory attributes. No manual reassignments or formatting needed.

Yes. Admins can see who changed what, when, and where it was published.

Logs include signature edits, rule changes, logins, API activity, and publishing events. Audit data is retained for 12 months and can be exported to CSV or accessed via API.

Yes. Marketing teams can:

• Add banners and CTAs
• Schedule campaign windows
• Run regional or departmental promotions

No IT support needed. Templates can be updated any time.

Yes. Exclaimer works alongside these platforms by letting you embed:

• UTM-tracked links
• Meeting scheduling buttons
• Forms or surveys
• Targeted banners
• Social media feeds

Everything can be tailored per user or group.

Yes. Show different content depending on:

• Sender’s department (Sales vs. Support)
• Recipient type (internal vs. external)
• Region or market segment

Recipient-based targeting (e.g., show CTA X for U.S. recipients and CTA Y for EMEA) is available in server-side mode and ideal for localizing campaigns.

Yes. You’ll get insight into:

• Banner click-through rates
• Campaign performance
• Audience engagement

We operate on Microsoft Azure’s active-active infrastructure using:

• High availability clusters (HACs)
• Cross-zone redundancy
• Load-balanced failover between paired regions (e.g., East US / West US)

If one datacenter goes offline, traffic is automatically routed to the paired site.

Recovery Point Objective (RPO): <1 minute
Recovery Time Objective (RTO): <5 minutes

Exclaimer includes fallback logic to handle missing or inconsistent directory attributes. If a field is blank (e.g. job title), a default value or fallback template is applied.

Admins can test logic via rule simulation prior to publishing. This reduces errors or incomplete signature rendering.

All releases go through:

• Load/stress testing
• Antivirus and malware scans
• Regional rollouts during off-peak windows

This minimizes any potential disruption.

Yes. You can:

• Preview layouts
• Simulate logic and rules
• Send test emails to different devices and groups

• 24/5 global technical support
• Enterprise SLAs available
• Onboarding and Customer Success teams
• Access to our knowledge base with hundreds of support articles