Available on: Legacy Plans (Basic, Plus, Enterprise), Current Plans (Basic, Grow, Platform, Enterprise)
Looking for your Employee Hub? The Outlook add-in is deployed centrally by an admin, so employees do not need the Employee Hub to receive their signature. You only need the Hub to view or edit your own signature details, and you can open it yourself at any time. Go to hub.wisestamp.com, enter your work email address and click Sign in, then enter the 4-digit code that is emailed to you.
Your admin must have added you to the company's WiseStamp account as an employee and assigned you at least one signature. An admin can also email you a signature link from the Employees page that opens the Hub directly, but the link is optional and you never have to wait for it. For full details, see Employee Hub.
Installation requirements
The WiseStamp Outlook add-in, which is supported for Outlook Desktop, Outlook Web, and Outlook Mobile, is the recommended method for automatically adding to your employee emails. Your WiseStamp account does not need to be integrated with the Microsoft Entra ID directory to successfully use the add-in. However, before installing the add-in, make sure to review the requirements.
Supported clients
The WiseStamp add-in is available for:
Microsoft 365 Business (Business Standard, Business Premium) version 1701 or later
Office 365 Enterprise (E1/E3/E5/F3) version 1701 or later
Microsoft 365 Enterprise (E3/E5/F3) version 1701 or later (and are signed in to Microsoft 365 using their organizational ID)
Office for Mac version 16.0.9318.1000 or later (Outlook Mac in Legacy mode is not supported)
Outlook mobile for iOS version 2.75.0 or later
Outlook mobile for Android version 2.2.145 or later
Outlook Web
MSI versions of Outlook show admin-installed add-ins in the appropriate Outlook ribbon, not the "My add-ins" section.
Additional Microsoft requirements
Users must also have Exchange Online and active Exchange Online mailboxes. Your subscription directory must either be in or federated to Microsoft Entra ID.
For more information, see Microsoft docs on supported clients (only those supporting v1.10 or above).
Check Outlook version
To check the channel/version of your Outlook desktop in Windows, go to File > Office Account.
The current channel is displayed in the About Outlook section.
To view the Outlook version in macOS, click the About Outlook icon. The version details are displayed at the top of the pop-up.
If your environment does not meet the installation requirements for the Outlook add-in, consider using the WiseStamp Desktop App. The WiseStamp app is compatible with both Windows and Mac, and can be installed on your employee computers to automatically feed signatures to Outlook or Mac Mail. As with the add-in, every change you make to signatures is immediately reflected in Outlook / Mac Mail.
Install the WiseStamp Outlook add-in using centralized deployment
This method automatically installs the add-in and adds signatures to the emails of all employees who have an Active status.
To determine whether centralized deployment is appropriate for your organization, see Microsoft on Centralized Deployment.
Only the domain's Global Admin can enable the integration. If you are not the Global Admin, you can send the setup instructions to the person who is (see step 5). The Global Admin needs to be connected to their Outlook account on a separate tab before integrating and needs to be signed out from any other Outlook account they might have on the same browser.
To perform the installation with centralized deployment:
Sign in to your Microsoft 365 account.
Sign in to your WiseStamp account.
On the main navigation panel, click Integrations.
In the Add-in for Outlook section, click Connect.
In the Connect Add-in for Outlook pop-up, choose one of the two options, then click Connect:
I'm the Global Admin: Choose this if you can complete the setup yourself.
Send instructions to another person: Choose this if someone else is your Microsoft Global Admin, and enter their email to send them the setup instructions. They complete the deployment, then you return to finish linking.
In the next pop-up, under Deploy the add-in, click Open admin center. The Microsoft 365 admin center opens in a new tab.
In the Microsoft Deploy New App wizard, on the Users step, choose who gets the add-in: Just me, All users, or Specific users or groups, then click Next.
On the Accept permissions requests step, review the app permissions for Email Signature Management for Office 365, then click Next.
When Deployment in progress finishes, click Done.
Return to the WiseStamp tab and, in the pop-up under Connect your organization, click Connect. You'll see the confirmation "Outlook Add-in successfully connected."
Deployment to all users can take up to 72 hours.
Manage WiseStamp Outlook add-in integration
After creating the WiseStamp Outlook add-in integration, you can manage this integration from the Management page. From this page, you can perform many management tasks, such as view the integration status, set new features, and remove the integration. To access the Management page, go to the Integrations page and click Manage for the Outlook add-in integration.
The following table lists the management tasks available to you:
Feature | Description |
Embed images | When enabled, this ensures that the images and icons are embedded, so they are always displayed. If disabled, signatures in Outlook may appear without images, unless users download them. This is disabled by default. |
Link to edit employee info from the add-in | Permits employees to edit their signature details, and within the Outlook add-in, a link is provided for accessing and editing these details. The link opens the employee's Employee Hub. This is disabled by default. |
Multiple signatures | This feature enables you to assign different signatures (primary, reply, and forward) for each employee from the Employees page. This is disabled by default. |
Shared inbox | This feature allows employees to apply personal signatures from shared inboxes for more personalized communications. Utilize the Shared inboxes option on the Employees page to map employee signatures to shared inboxes. This is disabled by default. |
Select email types to receive signatures | Select the appropriate checkboxes to specify which types of emails (new, reply, and forward) will receive signatures. This selection will apply to all your employees. |
Status | Displays the current status of the integration. In this section, the following information is displayed:
|
Disconnect | Click Disconnect to run a wizard that instructs you how to uninstall the Outlook add-ins and remove this integration. For more information, see Uninstall the Outlook add-in below. |
WiseStamp Outlook add-in limitations
While the WiseStamp Outlook add-in offers many benefits for deploying company email signatures, there are some limitations and potential issues to consider. Understanding these limitations can help you manage expectations and plan accordingly.
Embedded images may cause slow loading of auto-injected signatures, depending on their size.
In the new Outlook for Windows, the email address associated with your WiseStamp account must be set as the primary email account in Outlook.
Signatures are not supported on Calendar in Outlook Web.
Embedded images are not supported on Calendar in the new Outlook.
Teams meeting signatures may be misplaced above the invite details. This is not an Outlook add-in bug. The Teams meeting is added after the send event, which cannot be controlled by the add-in. Users may want to remove the signature.
Uninstall the Outlook add-in
If you change your domain to Google Workspace or you simply do not want to use the add-in anymore, you can easily uninstall it. Perform the following steps to remove your signature from Outlook.
To uninstall the Outlook add-in (central deployment):
Sign in to your Microsoft 365 account.
Sign in to your WiseStamp account.
On the main navigation panel, click Integrations.
In the Add-in for Outlook section, click Manage.
Click Disconnect, located at the top-right of the page.
In the pop-up, click 365 admin center. The page for the WiseStamp Add-in for Microsoft 365 app opens in the Microsoft 365 admin center.
In the Actions section, click Remove app.
In the Remove app page, select Yes, I'm sure I want to remove the app and associated data, and click Remove.
Once you get a message that the app was successfully removed, go back to the WiseStamp tab and click Disconnect.
To uninstall the Outlook add-in (individual deployment):
Compose a new email. At the bottom of the message, click ... and select Get Add-ins.
If there are tabs near the top of the dialog, verify that the Add-ins tab is selected. Then, select My add-ins.
Locate the Custom add-ins section at the bottom of the dialog.
Click the 3 dots icon next to the WiseStamp for Outlook app and select Remove.You can sync your Microsoft directory from GoDaddy with WiseStamp. However, installing the WiseStamp Outlook Add-in requires access to the Microsoft 365 Admin Center, which GoDaddy-managed accounts don’t provide. To continue, GoDaddy recommends removing your Microsoft account from their platform and setting it up directly with Microsoft.
Troubleshooting
WiseStamp's integration with Microsoft Outlook is a powerful way to manage email signatures, but users may occasionally encounter issues during setup or operation. Below is a guide to identifying and resolving common issues.
Why does my integration show a "Pending connection" status?
Why does my integration show a "Pending connection" status?
The WiseStamp integration with Outlook may show a "Pending connection" status due to Microsoft processing delays. It can take 24-72 hours for the deployment to fully process. If the status remains unchanged after 72 hours, consider rechecking the setup.
Why isn't my signature showing on replies or forwards?
Why isn't my signature showing on replies or forwards?
If your signature appears on new emails but not on replies or forwards, assign the signature as both the Primary, Reply, and Forward signature in WiseStamp. The Outlook add-in can behave inconsistently with reply and forward emails when only a Primary signature is set, so assigning both resolves it. You can set this per employee from the Employees page, or for everyone at once from the Groups page.
Why is my integration faulty or inactive?
Why is my integration faulty or inactive?
Refresh your browser, clear your browser's cache and cookies, and reopen WiseStamp and Outlook to check if the issue is resolved. For step-by-step instructions in Chrome, Firefox, Safari, and Edge, see Clear Cache.
Why is my signature not loading correctly?
Why is my signature not loading correctly?
Clear your browser cache and cookies to resolve data synchronization issues. For step-by-step instructions in Chrome, Firefox, Safari, and Edge, see Clear Cache. If you have multiple WiseStamp organizations, make sure the user is assigned to the intended signature.
Why is the "Connect" button grayed out?
Why is the "Connect" button grayed out?
Why is the "Connect" button grayed out? During integration, begin the connection process from the WiseStamp pop-up and complete the authorization flow from the same browser session.
I cannot open my Employee Hub to edit my signature details
I cannot open my Employee Hub to edit my signature details
You do not need a signature link email to open your Employee Hub. Go to hub.wisestamp.com, enter your work email address, and enter the 4-digit code that is emailed to you. The code expires quickly, so retrieve it promptly, and check your spam folder if it does not arrive. If the sign-in does not work, ask your WiseStamp admin to confirm that you have been added to the company's WiseStamp account and that a signature is assigned to you. See Employee Hub for more detail.
Why does my signature layout look different in Outlook than in the WiseStamp editor?
Why does my signature layout look different in Outlook than in the WiseStamp editor?
Outlook's rendering engine interprets signature HTML at the client level, which can cause layout differences between what you see in the WiseStamp editor and what appears in Outlook. The fixes below cover the most common symptoms.
Address or contact details splitting across multiple lines
This occurs when the signature container width collapses in Outlook, causing content that fits on one line in the Studio editor to wrap. In the Studio editor, add an empty text element and set its right spacing to a value that anchors the full intended width (for example, 420). This stops the container from collapsing and keeps single-line content on one line.
Signature appears flushed left on Mac Outlook
Confirm your email format is set to HTML: go to File > Options > Mail and ensure Compose messages in this format is set to HTML.
If the issue persists, it is caused by Outlook's rendering engine applying its own layout rules when the signature is stored in Outlook's native settings. Switching to server-side deployment bypasses this — the signature is injected after sending and is not subject to Outlook's client-side rendering. See the Server-Side Configuration guide for your setup.
Newly created signatures look broken but older ones still display correctly
Background updates to Outlook's rendering engine can affect how newly generated signatures are displayed, while older signatures already stored in Outlook are not re-processed and remain intact. Switching to server-side deployment bypasses Outlook's client-side rendering entirely and produces consistent results for all signatures. If you are already using the Google Workspace integration, you can run both in a hybrid setup — Google Workspace handles Gmail, server-side handles Outlook — without affecting your existing signatures.
Why is my signature working on Outlook Web but not in the new Outlook app on Windows?
Why is my signature working on Outlook Web but not in the new Outlook app on Windows?
The new Outlook for Windows (the version that opens with olk.exe) runs as a web app and maintains its own internal cache. If your signature shows correctly on Outlook Web but not in the Outlook desktop app on Windows, clearing this cache usually resolves it.
Method 1 — Clear via Network tab:
Close Outlook.
Open Command Prompt. Type olk.exe --devtools and press Enter. This opens Outlook together with a Microsoft Edge DevTools window.
In the DevTools window, select the Network tab.
Right-click anywhere in the Requests table and click Clear browser cache.
Close DevTools and Outlook, then reopen Outlook and check the signature.
Method 2 — Clear via Application tab (Local Storage and Cookies):
Close Outlook.
Open Command Prompt. Type olk.exe --devtools and press Enter.
In the DevTools window, select the Application tab.
Click the arrow next to Local Storage → right-click on https://outlook.office.com → click Clear.
Click the arrow next to Cookies → right-click on https://outlook.office.com → click Clear.
Close DevTools and Outlook, then reopen Outlook and check the signature.
This only applies to the new Outlook for Windows (olk.exe). If you are using classic Outlook (outlook.exe), this step does not apply — use the Safe Mode or Office Repair steps in the Outlook Signature Troubleshooting guide instead.
Related articles
The following articles cover related topics:

