How to set up server-side signatures
Server-side signatures are applied in transit, after the message leaves Exchange Online. Setup takes eight steps and is done once by your Microsoft Global Admin.
Add SPF records for every domain you plan to route. The wizard checks this for you and will not let you continue until each domain passes.
In WiseStamp, open Integrations, click Connect in the Server-side section, and select Microsoft Exchange.
Select I'm the Global Admin and click Connect, then click Authorize. If you are not the Global Admin, WiseStamp sends them an invitation to run the configuration.
Select the domains you want to route and click Connect.
Click the Copy icon to copy the code, then click Connect.
In the Microsoft window, paste the code and click Next, select your account, then click Continue to confirm the sign-in to Microsoft Exchange REST API-based PowerShell.
Close that tab. The management page for the integration opens in WiseStamp, where you can see the status and change settings later.
Activate your user in WiseStamp and send a test email from Outlook to confirm the signature is appended.
WiseStamp applies the Exchange Online configuration for you. There is nothing to install on your servers, no mail flow rules to write by hand, and nothing for your employees to do.
What happens after you set it up
After the configuration is in place, every message sent from your routed domains passes through WiseStamp on its way out and arrives with the signature already applied.
Signatures appear on email sent from any device and any mail client, including phones, tablets, and apps that connect to your mail server. Nothing has to be installed per person or per device.
Because the signature is added in transit, it does not appear in the compose window or in the Sent folder. Hybrid mode keeps a signature visible while composing where a client-side signature exists, and applies the server-side one only when it does not.
Signatures are always current. The signature is built at send time, so a template change takes effect on the next message without anything being pushed to employees.
What your environment needs
Before you start, confirm the following:
Microsoft Exchange Online, with Microsoft Global Admin credentials. Only the Global Admin can run the configuration, change which domains are included, or disconnect the integration.
Server-side deployment on your WiseStamp plan. It is available on Advanced and Enterprise.
SPF records on every domain you route.
Your employees in your WiseStamp account, each with a signature assigned and set as the default for new emails and for replies and forwards. A signature assigned only to new emails will not appear on replies.
Outgoing mail in HTML rather than Exchange rich text. In the Exchange admin center, under Mail flow > Remote Domains, set Exchange rich-text format to Never so signatures render as designed.
If you already have mail flow rules in Exchange Online, the WiseStamp rule needs stop processing more rules set on it, so your other rules run after the signature has been added.
What you are approving
Server-side deployment routes your outgoing mail through WiseStamp, so it is worth being precise about what that does and does not involve.
WiseStamp configures your mail flow through Microsoft Exchange REST API-based PowerShell, authorized by your Global Admin through Microsoft's own sign-in. You see and approve that sign-in as part of the setup.
WiseStamp appends the signature and does not read or store the content of your email. Each account is processed in isolation.
Nothing is installed on your servers and no agent runs in your environment.
The setup is reversible at any time, and you keep the switch. You can disconnect the integration from its management page in WiseStamp, and in an emergency you can disable the routing rule in your Exchange admin center so mail goes out without passing through WiseStamp. Full security details are on the WiseStamp Security and Compliance page.
Routing only some domains
To route only part of your organization, select the domains you want during setup. You can change the list later from the integration's management page, under Included domains, by clicking Edit. Domains you leave out send mail exactly as they do today.