Add the Send It Secure Outlook Add-in: AppSource or per-user
There are two ways to get the Send It Secure Outlook Add-in into Outlook: you or your administrator can deploy it through Microsoft AppSource, or you can add it yourself, one account at a time. Both give you the same add-in — the difference is who sets it up, how many people it reaches, and how quickly it appears. This article explains the difference so you can pick the right one.
At a glance
| Admin deployment (Microsoft AppSource) | Add it yourself (per-user) | |
|---|---|---|
| Best for | Rolling out to a team or whole organization | Testing, or getting one person set up right now |
| Who sets it up | You or your Microsoft 365 administrator | You, the individual user |
| How many people | Everyone the admin assigns | One account at a time |
| How fast it appears | Not immediate — can take up to 24 hours (see below) | Right away, after you restart Outlook |
| Control | Admin chooses exactly who gets it (and who doesn't) | Anyone with permission can add it themselves |
| Permissions | Requires an administrator | May be limited by your organization's settings |
Admin deployment (Microsoft AppSource)
With centralized deployment, you or a Microsoft 365 administrator adds the Send It Secure Outlook Add-in from Microsoft AppSource for the people you choose — a team, a department, or the whole organization. It's the right choice for a managed rollout: the admin controls exactly who gets the add-in and who doesn't, and no one has to add it individually.
The trade-off is time. Once an admin deploys the add-in, Microsoft has to roll it out across its systems before it shows up in each person's Outlook — it is not immediate. According to Microsoft:
- A new deployment can take up to 24 hours to appear for all assigned users.
- Later changes — updating the add-in, turning it on or off, or changing who it's assigned to — can take up to 72 hours to take effect.
Users may also need to close and reopen Outlook before the add-in appears on the ribbon. If it hasn't shown up yet, this propagation delay is usually the reason — give it time before troubleshooting.
Add it yourself (per-user)
You can also add the Send It Secure Outlook Add-in directly for a single account. This is the fastest way to get going — it appears right away, after you restart Outlook — which makes it ideal for testing the add-in or getting one person live immediately, without waiting on a deployment.
For step-by-step instructions, see Add the Send It Secure Outlook Add-in app.
Note: you may need admin permission to add the app yourself, depending on your organization's settings. Some organizations turn off the ability for people to add Store add-ins on their own. If yours has, you'll see a message that your organization has disabled it — in that case, ask your administrator to deploy the add-in for you.
Which should I choose?
- Rolling out to a team or organization? Use admin deployment through AppSource, and allow time for it to propagate.
- Testing, or setting up one person right now? Add it yourself for the account you need.
Once the add-in appears in Outlook, see The Send It Secure Outlook Add-in to sign in and send your first protected message.