You’re drafting a client onboarding email. Your manager just asked for a standardized request—same fields every time: project name, start date, budget code. You open Outlook, type it out… again. It’s 3:47 PM. The deadline is 4:00. You *know* there’s got to be a faster way—but where do you even look? You’ve clicked through File > Options three times already.
The Problem
You’re trying to reuse structured data across emails or tasks—and you assume Outlook must support forms like Word or Excel do. It doesn’t. Not in the way most people imagine. Outlook does have forms, but they’re buried, version-dependent, and disabled by default. Worse: Microsoft quietly deprecated the classic "Custom Forms" feature in Outlook 365 starting with Version 2208 (August 2022), and removed the Form Designer entirely from newer builds. So if you’re running Outlook 365 updated after mid-2022, clicking Developer > Design a Form will either show a grayed-out button—or nothing at all. That’s why so many admins and power users suddenly found their old templates broken. I’ve seen this trip up even experienced users who’d built 20+ custom task forms over five years—only to discover they no longer open or save in Outlook 365 v2308.
This affects anyone who relies on repeatable templates for approvals, requests, or internal workflows: HR coordinators sending onboarding checklists, IT teams logging hardware requests, finance staff collecting PO details. It’s not that Outlook lacks structure—it’s that its form capabilities are split across three disjointed systems: legacy custom forms (gone), Quick Steps + templates (limited), and modern Power Automate integrations (cloud-only). And yes—Outlook for Mac never had custom forms at all. Ever.
The Fix
There’s no single button labeled "Forms"—but there are four working options, ranked here by practicality for day-to-day use. Start with the one that matches your Outlook version and needs.
First, confirm your version: go to File > Account > About Outlook. If it says "Microsoft 365 Apps" and the version number is 2208 or higher, skip legacy forms entirely. They won’t work. Instead, use message templates with placeholders.
Here’s how to build a reusable email form using templates—no coding, no add-ins:
Step
Action
Menu Path
Shortcut
1
Write your email with clear placeholder text (e.g., [Client Name], [Due Date])
New Email > Compose
Ctrl+N
2
Save as Outlook Template (.oft)
File > Save As > Save as type: Outlook Template (*.oft)
Alt+F > A > T
3
Insert template via New Items menu
Home > New Items > More Items > Choose Form > User Templates in File System
Alt+H > N > O > C
4
(Optional) Assign to Quick Step for 1-click access
Home > Quick Steps > Create New > Choose Template
Alt+H > Q > N
That last step—assigning a template to a Quick Step—is the counterintuitive tip most miss. You don’t need macros or VBA. One click replaces the entire draft. Try it with these real-world examples:
For Outlook on the web? No .oft support. But you can save drafts with placeholders, then copy-paste into new messages. Or use Outlook’s built-in Quick Parts (under Insert > Quick Parts > AutoText)—though those only sync to desktop Outlook if you’re signed in with the same Microsoft 365 account and using Exchange Online.
If That Doesn't Work
If templates feel too static—or you need validation, dropdowns, or submission tracking—here’s what actually works today, ranked by likelihood of success:
Power Automate + Outlook connector: Build a flow triggered by an email with specific subject lines or attachments. Parse fields with regex or AI Builder. Works across Outlook Web and Desktop. Requires M365 E3/E5 or Power Automate per-user license.
Third-party add-ins: Tools like Forms for Outlook (by TeamForms) or Outlook Forms Pro add ribbon tabs with drag-and-drop builders. These run inside Outlook as web-based iframes. They work on Windows and Mac, but require admin approval for enterprise deployment.
SharePoint list + Outlook integration: Create a SharePoint list with columns matching your form fields. Use “Send to Outlook” to generate an email with pre-filled links. Users click, fill, and submit—all tracked in SharePoint. This is how many Fortune 500 companies replaced custom forms after 2022.
VBA macros (Outlook Desktop only): Still functional in Outlook 2019 and 2016, and in Outlook 365 if you enable legacy COM add-ins (File > Options > Add-Ins > Manage: COM Add-ins > Go). But Microsoft warns these may break without notice—and they’re blocked by default in many corporate environments.
Preventing It Next Time
Stop building forms that depend on Outlook’s native designer. That ship has sailed. Instead, adopt a two-layer strategy:
First, standardize your placeholder language across all templates: always use square brackets [Field Name], never curly braces or underscores. That makes future migration to Power Automate or SharePoint far easier.
Second, store all your .oft files in a shared network location—not your local Documents folder. Why? Because Outlook’s “Choose Form” dialog defaults to %appdata%\Microsoft\Templates, which isn’t synced or backed up. Put them in \teams\outlook-templates\ instead, and map that path in the dialog each time. Yes—it’s manual. But it means your team can share and update forms without reinstalling anything.
Also: test every template in both Outlook Desktop and Outlook on the web. What works in one rarely works identically in the other. For example, [Today] fields update correctly in Desktop but stay static in Web.
Related Settings
Three settings directly impact whether your forms—or templates—work as expected:
Trust Center > Macro Settings (File > Options > Trust Center > Trust Center Settings > Macro Settings): If macros are disabled, VBA-based form solutions won’t load—even if the code is safe.
Mail > Compose messages > Editor Options (File > Options > Mail > Compose messages > Editor Options): Under “Proofing”, ensure “AutoCorrect Options” includes “Replace text as you type”. That lets you set shortcuts like onboard → full onboarding template text.
Outlook on the web > Settings > View all Outlook settings > Mail > Compose and reply: Turn on “Always use plain text” if your templates include complex formatting. HTML templates often break when pasted into plain-text mode.
And one final note: Outlook for Mac supports none of the above form-building methods. Its only option is copying saved drafts or using third-party add-ins like TextExpander. Don’t waste time hunting for Form Designer—it never existed there.
Use Case
Best Tool
Works on Mac?
Syncs Across Devices?
Basic email templates
.oft files + Quick Steps
No
No (local only)
Dynamic field insertion
Power Automate + Outlook connector
Yes
Yes
Approval workflows
SharePoint list + Outlook rule
Yes
Yes
Legacy custom forms
Outlook 2016 or 2019 only
No
No
Quick text snippets
Quick Parts (AutoText)
No (Desktop only)
Yes (with M365 sync)
Mac-native solution
TextExpander + iCloud sync
Yes
Yes
Michael Lee
Michael covers the latest in office software updates
