WiseStamp for IT › Exchange › Step 1 of 12 — Setup Overview
Audience: IT manager / system administrator. Most documented steps require Microsoft 365 Global Administrator rights and Exchange admin access.
First: identify your topology
Topology | Mailboxes | Identity | Documented today |
Off-prem (Exchange Online / hosted) | Microsoft 365 / Exchange Online | Entra ID | Yes — full path |
Hybrid | Mix of on-prem + Exchange Online; outbound via EXO | Entra ID (synced from AD) | Yes — where mail egresses through EXO |
Pure on-prem (no M365) | On-prem Exchange Server | On-prem AD only | Not supported — no plan |
Resolved (pure on-prem): Employee sync is not supported for on-prem. No WiseStamp plan supports it. Since employee sync is a prerequisite for every deployment method, a no-M365 on-prem deployment is not supported by WiseStamp — full stop. If you are pure on-prem, migrating identity to Entra ID (hybrid, at minimum) is required before WiseStamp can be deployed.
Deployment methods
Server-side routing (primary for Exchange)
Routes outbound mail through WiseStamp’s SMTP service, which appends the signature in transit. Signatures then appear on all devices and clients with nothing installed for users.
Off-prem / hybrid: configured in the Exchange admin center using connectors + transport rules (automated wizard or manual). Documented in Server-Side Routing.
Pure on-prem: not supported. Employee sync is not supported for on-prem, and no plan supports it, so there is no supported on-prem Send Connector / smart host method.
Plan: Platform or Enterprise.
Outlook Add-In (client-side)
Applies the signature while the user composes, in Outlook (web/desktop/mobile).
Requires Exchange Online mailboxes. Suitable for off-prem and hybrid (EXO) mailboxes.
Not supported for on-prem-only mailboxes. Employee sync is not supported for on-prem, and no plan supports it.
Plan: Basic and above.
Hybrid mode (both)
Client-side applies first; server-side only appends if no WiseStamp signature is detected — preventing duplicates. Gives Outlook preview plus full cross-device coverage. Requires Platform/Enterprise.
Which method should I choose?
Off-prem or hybrid, need coverage on every device/client (mobile, CRM, non-Outlook senders)? → Server-side routing. Platform/Enterprise.
Off-prem or hybrid, mailboxes in Exchange Online, want visible-in-Outlook signatures? → Outlook Add-In. Basic+.
Want both? → Hybrid. Platform/Enterprise.
Pure on-prem (no M365)? → Not supported. Employee sync is not supported for on-prem, and no plan supports it. Migrate identity to Entra ID (hybrid, at minimum) before WiseStamp can be deployed.
Plan requirements at a glance
Capability | Minimum plan |
Outlook Add-In + Entra ID employee sync | Basic |
Server-side routing + signature rules | Platform |
SSO (SAML) | Platform |
Roles & permissions | Platform |
Security Group sync | Enterprise (or trial) |
See Exchange IT Admin Guide for the full matrix.
Order of operations
Confirm prerequisites — topology, plan, admin rights, routing/DNS, allowlist. → Prerequisites Checklist
Establish identity & employee sync — Entra ID (off-prem/hybrid). Not supported for on-prem AD; no plan supports it. → Identity & Employee Sync
Deploy signatures — Outlook Add-In (Outlook Add-In Setup) and/or server-side routing (Server-Side Routing).
(Platform/Enterprise) Configure SSO for admin sign-in. → SSO (SAML)
(Platform/Enterprise) Configure signature rules / scoping. → Signature Rules & Scoping
Activate employees and validate. → Go-Live Checklist
Hand off to employees; operate. → Employee Rollout Handoff, Ongoing Admin Guide.
Key dependency: establishing identity/sync does not by itself put signatures on email. You must also deploy the Add-In and/or server-side routing.
What WiseStamp accesses
Entra ID directory: User.Read.All — import and sync employees.
Outlook Add-In: ReadWriteItem — insert the signature; WiseStamp states it does not read or store email content.
Server-side routing: mail flows through WiseStamp’s SMTP host; WiseStamp states it does not read, store, or change email content or recipients.
Full detail: Permissions Reference.