The Problem
Folio is a document collaboration platform built for version-controlled PDFs, annotations, and client-facing deliverables. Outlook is an email and calendar client that treats external links like second-class citizens — especially those requiring session tokens, SSO handshakes, or embedded iframe permissions. The issue isn’t user error. It’s architectural. Folio uses modern OAuth2 flows and short-lived JWTs. Outlook Desktop (365/2019/2016) strips or blocks these tokens when rendering previews. Outlook on the Web (OWA) does slightly better — but only if the link is opened *outside* the preview pane. This hits consultants, proposal managers, and sales engineers who send Folio links daily. They assume ‘it’s just a link’ — but Outlook sees it as a potential security risk and sandboxes it aggressively.The Fix
There’s no native integration. But there *is* a reliable workaround — one that works across Outlook 365, 2019, and 2016 on Windows. It takes 45 seconds. No admin rights needed.Step 1: In Folio, open the document you want to share. Click the Share button (top-right corner).
Step 2: Under Link Settings, uncheck Require sign-in. Yes — this feels wrong. But it’s the only way Outlook will render the preview reliably. Folio still logs access and shows viewer names — it just skips the redirect-to-SSO step.
Step 3: Copy the generated link. Paste it into Outlook. Before sending, right-click the link > Edit Hyperlink. In the Address field, append
?utm_source=outlook to the end. This helps Folio tag the traffic source — and more importantly, prevents some Outlook caching bugs.Step 4 (Windows only): Go to File > Options > Mail > Compose messages. Scroll down to Internet format. Select HTML — *not* Rich Text. Rich Text mode corrupts Folio URL parameters silently. On Mac Outlook, this setting doesn’t exist — HTML is always used.
This works because you’re removing the authentication handshake that Outlook breaks, while preserving auditability and tracking. Folio still knows who opened it — just not *how* they got there.
If That Doesn't Work
Sometimes even the simplified link fails — usually due to corporate proxy rules, conditional access policies, or Outlook cached credentials. Try these in order:• Attach a static PDF snapshot: In Folio, click Export > PDF (Current Version). Attach it directly. Yes — you lose live updates and annotations, but recipients get immediate access. Use this for urgent client sends.
• Embed as an Outlook inline image (for cover pages only): Export Folio’s first page as PNG. Insert > Pictures > This Device. Right-click > Size and Position > set width to 500px. Not ideal for long docs — but perfect for proposal covers.
• Use Outlook’s built-in cloud attachment: In Outlook Desktop, click Insert > Attach File > Browse Cloud Locations. If your Folio account connects to OneDrive or SharePoint (via Folio’s connector), upload the file there first — then insert as a cloud link. This bypasses Folio’s auth layer entirely.
• Switch to OWA for critical sends: Outlook on the web handles Folio links more gracefully — especially if the recipient also uses OWA. Test it: send yourself a test email via outlook.office.com, then open it from there.
Preventing It Next Time
Don’t wait until you’re mid-send to troubleshoot. Build this into your workflow:• Add a quick-check step to your pre-send routine: paste the Folio link into a new Outlook message, then hover over it. If you see ‘Loading…’ for more than 2 seconds, or a broken chain icon, re-generate with sign-in disabled.
• Save a Folio template email in Outlook: Draft a message with the clean link + standard intro (“Here’s the latest version of…”). Save as Quick Part (Insert > Quick Parts > Save Selection to Quick Part Gallery). Name it “Folio Link – Clean”. Reuse it every time.
• Disable Outlook’s auto-preview for external links. Go to File > Options > Trust Center > Trust Center Settings > Automatic Download. Uncheck Download pictures automatically in HTML e-mail messages. This stops Outlook from trying (and failing) to fetch Folio thumbnails.
Surprising tip: Folio links sent from *Outlook Mobile* (iOS/Android) almost always work — even with sign-in required. Why? Because the mobile app opens links in Safari or Chrome, not a sandboxed WebView. So if timing is tight, send from your phone.
Related Settings
Folio behavior in Outlook overlaps with several other Outlook settings — especially around security, preview handling, and link hygiene. These often get overlooked but directly affect whether your Folio links survive the send process.| Action | Shortcut | Alt Sequence | Notes |
|---|---|---|---|
| Edit hyperlink in message | Ctrl+K | Alt+K | Works in all Outlook versions. Critical for cleaning Folio URLs. |
| Toggle reading pane | Ctrl+R | Alt+O+R | Turn off to avoid accidental preview-triggered auth failures. |
| Open message in new window | Ctrl+Shift+O | Alt+H+O | Bypasses preview pane entirely. Useful for testing Folio links before sending. |
| Disable automatic image download | — | Alt+F+T → Trust Center → Automatic Download | Stops Outlook from fetching broken Folio thumbnails and slowing sends. |
| Set default message format to HTML | — | Alt+F+T → Mail → Compose messages → Format | Required for Windows Outlook. Mac has no equivalent setting. |
| Check current Outlook version | Alt+F+I | Alt+F+I | Version matters: Outlook 365 builds post-2308 handle external links better than 2019 or 2016. |
| Send test to yourself | Ctrl+Enter | Alt+S | Always do this before hitting Send on any Folio link — especially after updating Folio permissions. |
