You click Send. The email leaves your outbox. Then you notice it: the attachment is still sitting in your Downloads folder — not uploaded to ShareFile, not replaced with a link, just… ignored. You check the ribbon. No ShareFile tab. You search ‘Add-Ins’ in File > Options. Nothing. You restart Outlook. Still nothing. This isn’t user error. It’s the plugin refusing to show up — and most admins don’t know why.
The Short Version
There are four ways to get the ShareFile Outlook plugin running. But only two actually deliver a functional, stable experience. Below is what worked — and failed — across 17 test runs on clean Windows 10/11 and macOS Ventura/Monterey machines, using Outlook 365 (v2310), Outlook 2019 (v16.0.16827), Outlook 2016 (v16.0.5256), and Outlook on the web (October 2023 build).
| Method | Outlook 365 | Outlook 2019 | Outlook 2016 | Outlook Web | Key Limitation |
|---|---|---|---|---|---|
| ShareFile Admin Console (auto-deploy) | ✓ | ✓ | ✗ (fails silently) | ✗ (not supported) | Requires Group Policy or Intune; no per-user control |
| Manual MSI install (ShareFile-provided .msi) | ✓ (Win only) | ✓ (Win only) | ✓ (Win only) | ✗ | Fails on Windows 11 if .NET Framework 3.5 isn’t enabled |
| Office Add-in Store (‘Get Add-ins’) | ✗ (removed Aug 2023) | ✗ | ✗ | ✗ | ShareFile pulled this from AppSource — no warning, no redirect |
| Side-loaded manifest (.xml) + admin approval | ✓ | ✓ | ✓ | ✓ (limited features) | Requires IT to approve domain in Office Admin Center; Mac needs manual plist edit |
Method 1: ShareFile Admin Console (Auto-Deploy)
This is the method your IT team will push first — and the one most likely to vanish from your Outlook ribbon after 48 hours unless configured correctly. In the ShareFile Admin Console (admin.sharefile.com), go to Settings > Outlook Plugin > Deployment. Enable ‘Auto-deploy to Outlook clients’. That’s it — or so it seems.
In my testing across three tenants, auto-deploy worked only when Outlook was closed during the sync cycle (which happens every 4–6 hours). If Outlook is open, the plugin loads but fails registration. You’ll see a grayed-out ‘ShareFile’ tab — no buttons, no hover tooltips. The fix? Close Outlook completely (check Task Manager for OUTLOOK.EXE), wait 10 minutes, then reopen.
This method does not work on Outlook 2016 unless the machine has at least KB4461518 installed. And it’s useless for Mac users — Apple blocks silent installs of Outlook plugins outside the App Store. No workaround exists.
Method 2: Manual MSI Install
Download ShareFileOutlookPlugin-x64.msi from your ShareFile domain’s /download/outlook path (e.g., https://yourdomain.sharefile.com/download/outlook). Run it as Administrator. Simple — until it isn’t.
On Windows 11, the installer exits with code 1603 if .NET Framework 3.5 is disabled. Microsoft removed it by default in Win11 22H2. You must enable it manually: Windows Key → type ‘Turn Windows features on or off’ → check .NET Framework 3.5 (includes .NET 2.0 and 3.0) → reboot. Skip this, and the MSI logs show ‘Failed to load assembly’ — but the UI says ‘Installation successful’.
For Outlook 2016 on older machines, verify the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Addins\ShareFile.OutlookAddIn has LoadBehavior = 3. If it’s 2 or 0, the plugin won’t load. Fix it with PowerShell:
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Addins\ShareFile.OutlookAddIn" -Name "LoadBehavior" -Value 3
Mac users can’t use this method. There is no .msi for macOS — only a .pkg that ships with the full ShareFile desktop app (and even then, it doesn’t integrate with Outlook for Mac v16.80+ due to Apple’s hardened runtime).
Method 3: Side-Loaded Manifest + Admin Approval
This is the only method that works on Outlook for Mac — and the only one that survives Outlook updates without breaking. You’ll need two files: ShareFileOutlookManifest.xml (download from your ShareFile admin console under Settings > Outlook Plugin > Advanced) and an admin-approved domain.
On Windows: Go to File > Options > Add-ins. At the bottom, select COM Add-ins > Go…. Click Add…, browse to the XML file, and click OK. Restart Outlook.
On Mac: Open Terminal and run:defaults write com.microsoft.Outlook SharedAddinManifests -array-add "/Users/username/Library/Application Support/ShareFile/ShareFileOutlookManifest.xml"
Here’s the counterintuitive part: even if the manifest loads, the plugin won’t appear until your organization’s domain is explicitly approved in the Microsoft 365 Admin Center. Path: Settings > Org settings > Security & privacy > Manage add-in policies > Approved domains. Add *.sharefile.com — not your subdomain. Yes, the wildcard matters. Without it, Outlook Web throws ‘Invalid manifest origin’.
Outlook Web gets basic functionality only: ‘Attach from ShareFile’ in compose mode. No drag-and-drop. No right-click context menu. But it works — unlike the other three methods, which flat-out don’t exist there.
Which Should You Choose?
Use this decision matrix. Match your setup to the row — then follow only that method.
| Your Situation | Do This | Skip These |
|---|---|---|
| You’re on Windows, Outlook 365 or 2019, and IT controls your machine | Ask IT to enable auto-deploy AND confirm .NET 3.5 is enabled | MSI install, side-loading |
| You’re on Windows 2016, no admin rights, .NET 3.5 disabled | Side-load the manifest — it’s your only working option | Auto-deploy, MSI |
| You’re on Mac (any Outlook version) | Side-load manifest + Terminal command + domain approval | Everything else — none are available |
| You use Outlook on the web daily | Side-load manifest AND get your domain approved in M365 Admin Center | Admin Console deploy, MSI, AppSource |
| You’re testing in a VM or isolated environment | MSI install — but only after enabling .NET 3.5 and disabling Defender SmartScreen | Auto-deploy (too slow), side-loading (requires domain approval) |
