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 | Supported |
Exchange Online (hosted) | Microsoft 365 / Exchange Online | Entra ID | Yes — full path |
Hybrid | Mix of local Exchange Server and Exchange Online mailboxes, with outbound mail sent through Exchange Online | Entra ID (synced from AD) | Yes — where mail egresses through Exchange Online |
Microsoft 365 is required. Every WiseStamp deployment method depends on employee sync from Entra ID, so an Exchange Server environment with no Microsoft 365 tenant is not supported. Moving identity to Entra ID, at minimum in a hybrid configuration, 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.
Configured in the Exchange admin center using connectors + transport rules (automated wizard or manual). Documented in Server-Side Routing.
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.
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?
Need coverage on every device and client (mobile, CRM, non-Outlook senders)? → Server-side routing. Platform/Enterprise.
Mailboxes in Exchange Online, want visible-in-Outlook signatures? → Outlook Add-In. Basic+.
Want both? → Hybrid. Platform/Enterprise.
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. → 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.