For Microsoft 365 administrators

Mail merge in Outlook.
Your users asked for it.
Here is what it does in your tenant.

SecureMailMerge is an Outlook add-in. It processes campaign data on the user's device and sends through the user's own Microsoft 365 mailbox. This page covers permissions, data flow, deployment and licensing so you can approve, pilot or decline with the facts.

Free plan available. Requires a Microsoft 365 work or school account.

Publisher: Sol Inventum OÜ, Tallinn, Estonia. Listed on Microsoft AppSource since 2023.

Publisher Attestation published with Microsoft (self-reported)

Illustrative reviewer avatar, not a photograph of the reviewerIllustrative reviewer avatar, not a photograph of the reviewerIllustrative reviewer avatar, not a photograph of the reviewerIllustrative reviewer avatar, not a photograph of the reviewerIllustrative reviewer avatar, not a photograph of the reviewer 4.9/5 from 74 ratings on AppSource

Made for your Outlook. New OutlookClassic OutlookMacWeb No Word required.No Exchange changes to deploy.

What happens when a user runs a campaign.

Two steps inside your tenant, one license check with us.

See the full walkthrough

01 / ON THE DEVICE

The campaign is built in Outlook

The user picks a spreadsheet and writes the message in Outlook. The add-in reads the file locally and generates one message per row inside the Outlook client. No campaign data is processed on a server.

02 / THROUGH THE TENANT

Sent from the user's own mailbox

Messages are sent through the user's own Microsoft 365 mailbox via Microsoft Graph, like any email the user writes. They are saved in Sent Items, and your retention, DLP and audit controls keep applying.

03 / WHAT WE SEE

A license check, nothing else

Our licensing server receives the mailbox's primary email address, the product name and a timestamp to check for a license. Anonymous usage counts and error reports are sent separately and contain no recipient data. Recipient data, message content and attachments are never sent to us.

Where campaign data goes

  1. Spreadsheet and attachments

    Picked by the user from their own files and read locally by the add-in.

  2. Processed in Outlook on the device

    One message per row, generated inside the Outlook client.

  3. Sent through Microsoft 365

    Via Microsoft Graph from the user's own mailbox, under the user's identity. Saved in Sent Items.

  4. License check with www.securemailmerge.com

    The mailbox's primary email address, the product name and a timestamp. No campaign data. Free users' addresses are not stored after the check.

Anonymous usage counts and error reports contain no recipient data. Both can be blocked at the firewall and the add-in keeps working.

Evaluation checklist

What to check
before you approve.

Permissions, data handling, deployment and the limits that stay in your hands. Each item links to the page that documents it.

Permissions & consent

Delegated Microsoft Graph permissions, no application permissions
The add-in signs the user in and calls Microsoft Graph as that user, so it can only reach what that user can reach. It requests User.Read, Contacts.Read, Contacts.Read.Shared, Calendars.Read.Shared, Mail.Send, Mail.ReadWrite and MailboxSettings.Read, plus the openid, profile and offline_access sign-in scopes. Each one is explained in the table below.
No mailbox-wide read beyond the user's own
Contacts.Read.Shared and Calendars.Read.Shared only reach shared mailboxes the user already has access to, and Calendars.Read.Shared reads the Outlook category list, not calendar or event data. Nothing is read from mailboxes the user cannot already open.
Admin consent or user consent
Your tenant's consent settings decide. Where users cannot consent, they see "Need Admin Approval", and an administrator grants consent from that dialog or with the admin consent link in Microsoft Entra.
The token stays between Outlook and Microsoft
The add-in's Microsoft Graph token is only transmitted between the user's computer and Microsoft, never to our servers. The refresh token never leaves the user's Outlook, and nothing runs while the add-in is closed.

Data handling

Processed on the user's device
Spreadsheets, recipients, message content and attachments are processed in Outlook on the user's computer and are not stored by us. Campaign data never reaches our servers during normal use.
What the licensing server stores
For licensed users, the email address with a timestamp of last use, plus account and billing contact data. Free users' email addresses are not stored after the license check. No card data.
Hosting and subprocessors
The licensing server runs in Microsoft Azure data centers in Europe. The website and add-in files are served by Cloudflare. Subprocessors are Microsoft Azure, Cloudflare, Sentry, Help Scout, Fathom Analytics and HelloSign.
Data Processing Addendum
Our standard DPA covers breach notification, deletion within 10 business days after the service ends, audits and no transfers outside the EU or EEA without your prior written consent. A signed copy is available on request.
Privacy policy
What the website and the add-in collect, including the anonymous usage counts on our self-hosted analytics and the error reports sent to Sentry.

Deployment

Deploy from Integrated apps
Deploy to specific users or groups, or to the entire organization, from "Settings" > "Integrated apps" in the Microsoft 365 admin center. Microsoft says a deployed add-in can take 24 to 72 hours to appear in Outlook.
New Outlook, classic Outlook, Mac and web
The same add-in runs in New Outlook and classic Outlook on Windows, Outlook for Mac and Outlook on the web. No Word installation is needed.
Deploying is not licensing
Integrated apps controls who has the add-in. Licenses control whose emails go out without the promotional footer, and are assigned separately.
Firewall requirements
Besides the Microsoft 365 endpoints your tenant already allows, the add-in needs HTTPS to www.securemailmerge.com. The analytics host and Sentry are optional and can be blocked.
Updates and removal
The add-in loads from our servers, so users get new versions without any action in the admin center. If a new version needs more permissions, the admin center asks you to review them. A deployed add-in can only be removed by an administrator.

Limits & controls

Exchange Online sending limits still apply
SecureMailMerge adds no recipient cap of its own. Microsoft 365 limits and your tenant's configuration still apply, and users can set their own daily maximum in the add-in.
Shared mailboxes need Send As
Users run the add-in in their own mailbox and choose the shared address as the sender. You grant Send As permission on the shared mailbox. Sent messages are saved in the user's own Sent Items folder.
No open or click tracking
SecureMailMerge adds no tracking pixels and rewrites no links. Messages look like the personal email they are.
Custom headers for your mail flow rules
Users can add a custom header (names start with x-) to every message, so your mail flow rules can recognise mail merge traffic, or a List-Unsubscribe value.

Every permission and why

All delegated, granted per user. Find the enterprise application in Microsoft Entra by its application ID.

Application ID: e9ce170b-5d81-44cf-8924-08f30720db3c

PermissionWhat it is used for
User.ReadSigns the user in and reads their profile and email address, to show the sending account in the add-in and run the license check.
Contacts.ReadReads the user's own contacts to build a recipient list.
Contacts.Read.SharedReads contacts in shared mailboxes the user already has access to.
Calendars.Read.SharedReads only the Outlook category list of those shared mailboxes, so shared contacts can be filtered by category. No calendar or event data is read; Microsoft's permission model offers no narrower scope, confirmed with Microsoft support.
Mail.ReadWriteCreates draft messages in the user's own mailbox while attachments upload and holds each generated message until it is sent.
Mail.SendSends the generated messages from the user's own mailbox.
MailboxSettings.ReadReads mailbox settings so the add-in respects your sending limits, and the user's own Outlook categories.
offline_accessRefreshes the access token during a campaign so the user is not asked to sign in every few minutes. The refresh token stays in Outlook, and the user signs in again after closing the add-in or Outlook.
openid, profileStandard OpenID Connect sign-in.
  • Also on the app registration: Mail.Send.Shared, configured for a planned feature. The current release does not request it, so users are not asked to consent to it. Admin consent through the admin consent link grants every permission on the registration, so it appears in Entra after that step.
  • Separate from Microsoft Graph, the add-in manifest declares the ReadWriteMailbox permission level of the Outlook add-in API (Office.js).
Read the full permissions guide

Security review

No new place
for your mail data.

Campaign data is processed in Outlook on the user's device, and it leaves only as mail sent from the user's own mailbox.

SecureMailMerge was designed for minimal trust. All primary functionality runs on the user's computer, with no processing on a server. The add-in's Microsoft Graph token is only ever transmitted between the user's computer and Microsoft.

The only server of ours the add-in depends on is the licensing server, which never receives campaign data. We have no SOC 2 report or ISO 27001 certification of our own; the certifications of our hosting providers are listed in the security overview.

Removing the add-in in "Integrated apps" takes it out of users' Outlook after Microsoft's propagation delay. Consent already granted stays on the SecureMailMerge enterprise application in Microsoft Entra until you revoke it there, under "Enterprise applications" > "Permissions".

Share the Trust Center with IT

Hosts the add-in contacts

  1. Microsoft 365 (Microsoft Graph)

    Sending mail, reading contacts and mailbox settings. Required, already allowed in your tenant.

  2. www.securemailmerge.com

    Loading the add-in (GET) and the license check (POST to /api/license). Required.

  3. analytics.solinventum.com

    Anonymous usage counts on our self-hosted Rybbit. Optional, can be blocked.

  4. Sentry (o4504911921414144.ingest.sentry.io)

    Error reports with technical information only. Optional, can be blocked.

The license portal at licensing.solinventum.com is not contacted by the add-in. Only the people who manage licenses need it, in a browser.

Who runs it

Publisher

Sol Inventum OÜ, an EU company registered in Estonia. Sepapaja 6, Tallinn. Company number 14665482.

About us

Rating

4.9/5 from 74 ratings on Microsoft AppSource, where SecureMailMerge has been listed since 2023.

Read the reviews

Publisher Attestation

A self-reported questionnaire published by Microsoft, not a Microsoft security review. Security contact [email protected], also published in security.txt.

View the attestation

Licensing

Free to evaluate. One license per person who sends, using their own email address to remove the footer.

Full pricing details
  • Pilot without licenses

    Every feature works in the free version, with no time limit. It adds a short promotional footer to each email, so a pilot needs no purchase.

    Compare the plans
  • One license per person who sends, using their own email address

    Only users who send campaigns need one; recipients need nothing. Licenses are reassignable within your subscription when staff change. No limit on campaigns, emails or attachments, so there are no per-recipient or per-message charges.

    Full pricing details
  • Buy on our website or through Microsoft

    Pay by card or PayPal on our website, or buy the SecureMailMerge SaaS offer on Microsoft AppSource for Microsoft 365 billing. Microsoft purchases are billed, resized and cancelled in the Microsoft 365 admin center, with volume discounts from 10 licenses.

    Set up a company subscription
  • Assign licenses on the licensing server

    Website and Microsoft purchases are both assigned to email addresses at licensing.solinventum.com. The subscription owner can invite delegated admins who assign licenses without billing access.

    Assign licenses to your team

A pilot in four steps

Deploy to a small group, let them send on the free version and check the controls you care about. Nothing to buy until you widen the rollout.

  1. 01

    Deploy to a test group

    In "Settings" > "Integrated apps", choose "Specific users/groups" instead of the entire organization. Users need a Microsoft 365 Business or Education mailbox; the add-in appears in their Outlook without any action from them.

    See the deployment steps
  2. 02

    Settle consent once

    If your tenant lets users consent, they accept the permissions at first sign-in. If they see "Need Admin Approval", grant consent for everyone with the admin consent link.

    Grant admin consent
  3. 03

    Have a user send a real test

    The free version has every feature and adds a promotional footer. Check that the messages sit in the user's Sent Items and that the footer is the only difference from a normal email.

    What users do first
  4. 04

    Check the controls you need

    Block the analytics host and Sentry if you want to, ask users to set a custom header (names start with x-) so your mail flow rules can see the traffic, and grant Send As where a shared mailbox is the sender.

    Firewall requirements

Questions admins
ask before approving.

Short answers, each with the page that documents it.

Visit the Help Center
Which Microsoft Graph permissions does it request, and are they delegated or application?

Delegated only, no application permissions. The add-in signs the user in and calls Microsoft Graph as that user with User.Read, Contacts.Read, Contacts.Read.Shared, Calendars.Read.Shared, Mail.Send, Mail.ReadWrite and MailboxSettings.Read, plus the standard openid, profile and offline_access sign-in scopes. Separately, its add-in manifest declares the ReadWriteMailbox permission level of the Outlook add-in API.

Read the permissions guide
Does any message content or recipient data leave our tenant?

No campaign data is sent to us. Spreadsheets, message content and attachments are processed in Outlook on the user's device and sent through the user's own mailbox via Microsoft Graph. Our licensing server receives the mailbox's primary email address, the product name and a timestamp. Anonymous usage counts and error reports contain no recipient data and can be blocked at the firewall.

Read the security overview
Can we deploy it to a pilot group first?

Yes. In "Integrated apps", choose specific users or groups instead of the entire organization, and widen the assignment later. Deployed users can use every feature for free with a promotional footer, so a pilot needs no licenses.

See the deployment steps
Can we control who uses it and who manages licenses?

Who has the add-in is set in "Integrated apps". Whose emails go out without the footer is set by license assignment on the licensing server, where the subscription owner can invite delegated admins to assign licenses without billing access.

See centralized license management
Does it work in New Outlook and on Mac?

Yes. SecureMailMerge supports New Outlook, classic Outlook on Windows, Outlook for Mac and Outlook on the web with a Microsoft 365 work or school account. Outlook.com and personal Microsoft accounts are not supported.

Read about New Outlook support
How do we remove it, and what happens to licenses?

Remove it in "Integrated apps"; it disappears from users' Outlook after Microsoft's propagation delay. Revoke the granted consent under the enterprise application in Microsoft Entra if you want it gone there too. Removing the add-in does not cancel a subscription. Cancel website purchases on the licensing server and Microsoft purchases in the Microsoft 365 admin center; licenses stay active until the end of the paid term.

See removal and cancellation

Ready to approve a pilot?

Send security questions, vulnerability reports and requests for a signed DPA to [email protected].