Outlook add-insfor Exchange Server.No Microsoft 365.
SecureMail, Disclaimer, SecureFiles, Archive and Awareness right in Outlook, for mailboxes on your own Exchange. Upload the manifest, done.
Why add-ins rarely run on your own Exchange
Three technical hurdles.
Sign-in through Entra ID
Most add-ins sign in with single sign-on at Microsoft. Without Microsoft 365 that path does not exist.
The manifest is rejected
Exchange Server SE only accepts manifests up to API version 1.5. Store versions ask for more and fail on upload.
The new Outlook drops out
The new Outlook for Windows does not support mailboxes on your own Exchange. Add-ins have to run in Outlook classic and on the web.
How the add-ins get into your own Exchange
Three steps, once for the whole organisation.
1. Download the manifest
The portal holds a manifest for Exchange Server per module. It points to the installation the tenant uses: cloud or your own data centre.
2. Upload to Exchange
In the Exchange admin center, add it from file under Organization and Add-ins and enable it for the organisation.
3. Pairing without input
On first launch the add-in exchanges the pairing code from the manifest for its own access. Nobody types a code.
SecureMail
Disclaimer
SecureFiles
Archive
AwarenessEvery module in the ribbon.
Outlook classic and Outlook on the web on Exchange Server SE, paired through the manifest.
No Entra ID, no Microsoft 365
No code for users to type
One manifest per module
Cloud or your own data centre
Five add-ins, one path
What each add-in does on your own Exchange.
SecureMail
Choose protection while composing: S/MIME, PGP, PDF or portal, right in the ribbon.
Disclaimer
Signature templates in the mailbox, maintained centrally in the portal.
SecureFiles
Send large files as a protected link, straight from the message.
Archive
Search the archive from Outlook and open archived messages.
Awareness
Report suspicious messages to IT with one click.
One access per add-in
Every add-in gets its own access. The SecureFiles access does not open the archive.
Store add-in or manifest for Exchange Server
Why typical add-ins never arrive on your own Exchange.
Conbool on Exchange Server | Typical store add-ins | |
|---|---|---|
| Microsoft 365 required | no | yes |
| Sign-in | pairing code in the manifest | single sign-on through Entra ID |
| Manifest for Exchange Server SE | API 1.5, generated by the portal | rejected on upload |
| Code typed by users | none | depends on vendor |
| Operation in your own data centre | possible | rare |
Statements on store add-ins based on Microsoft requirements for add-ins with single sign-on and for manifests on Exchange Server SE.
Frequently asked questions
Do Outlook add-ins run with Exchange Server without Microsoft 365?
Which Outlook clients are supported?
Why does Exchange Server reject my add-in?
How do the add-ins sign in?
Do send events work?
Does it work with Conbool from the cloud?
Can Exchange Online and in-house Exchange be mixed?
Related solutions
Secure Exchange on premises
Filtering, encryption, signatures and archive for Exchange Server SE.
Encrypt internal email
Route mail between two mailboxes through the gateway.
Email security without Entra ID
People, groups and addresses from local Active Directory.
Encryption for Exchange Server
S/MIME, PGP, PDF and portal centrally at the gateway.
Signatures for Exchange Server
Automatic signatures with fields from AD.
See the add-ins on your own Exchange
All five add-ins on an Exchange Server SE, from uploading the manifest to the first message.