VBA Macros in New Outlook: What Replaces Them

Do VBA macros work in new Outlook?#

No. VBA macros in new Outlook do not run. There is no VBA editor, no Developer tab, and no setting anywhere that turns them on. If your macro buttons vanished the day you switched clients, nothing is broken and nothing is misconfigured.

New Outlook for Windows is a web application in a desktop shell. VBA is Windows desktop code that loads into the classic Outlook process and talks to its object model directly. New Outlook has no such process, so there is nothing for a macro to attach to.

Microsoft lists macros as unsupported in its new-versus-classic feature comparison, alongside COM add-ins, custom forms and voting buttons — a statement about architecture, not a gap waiting on a roadmap. Most load-bearing macros are mundane, though, and this article maps each job to its replacement one at a time.

Which Outlook clients still run macros?#

Only one: classic Outlook for Windows, with its Developer tab and VBA editor. VBA has always been Windows desktop technology, so new Outlook, Outlook on the web, Outlook for Mac and Outlook mobile have never run it — but all of them run Power Automate flows and web add-ins. That is the tell: a flow acts on the mailbox, not on the client in front of you, so it survives a client change where a macro does not.

Inventory your macros before you pick a replacement#

Start with a list, not a replacement. Much of what people call a macro turns out to be a rule, a Quick Step, or a script that last ran in 2019. For each one, write a single business sentence — files this to the client folder, saves the attachment to the shared drive — plus its trigger and whether it touches anything outside the mailbox. Those three columns pick the replacement faster than reading the code does.

Do it in classic Outlook while you still have it. The code lives behind Alt+F11, and all of it sits in one VbaProject.OTM file in your Windows profile — copy that out now, because no migration carries it.

Which replacement fits which macro job?#

Match your one-sentence description to the closest row, then read the trade-off before committing. Where only classic Outlook can do the job, the row says so.

One pattern runs through that table: macros that stayed inside the mailbox have a supported replacement, and macros that reached into Windows do not.

Rules and Quick Steps cover more than people expect#

Filing and categorisation are usually the two biggest groups on a macro list, and both are rule work. Inbox rules in new Outlook run server-side — they fire whether your machine is on or not, and they apply on your phone. The quota is 256 KB across all rules, roomy unless you have hundreds of sender-specific conditions.

Quick Steps are the manual counterpart: one click that moves, marks read, categorises and can start a reply. As of July 2026 they are partially available in new Outlook with fewer actions than classic, and they do not carry across, so budget time to rebuild them.

Two caveats. New Outlook cannot import or export rules, so a saved rules file from classic is no use. And in classic the run-a-script rule action was disabled for security and only returns via an EnableUnsafeClientMailRules registry value — many macro workflows are already half-broken where they live now.

Power Automate: the closest thing to a triggered macro#

Power Automate is Microsoft's supported answer for automation that used to live in a macro. It runs on triggers and actions — when a message arrives with an attachment, save it to SharePoint and post to Teams — and a selected-message trigger covers the manual, one-click case too.

• Licensing: Microsoft 365 plans include standard connectors — Office 365 Outlook, SharePoint, OneDrive. Premium connectors and unattended desktop flows need a separate plan.
• Latency: mail-triggered flows run in seconds to minutes, not instantly — fine for filing, wrong for anything that must finish before you read the message.
• Ownership: a flow belongs to whoever built it and stops when that person leaves, so anything business-critical belongs in a shared or service account.
• Reach: a cloud flow sees your mailbox and your cloud services, never your C: drive, a mapped share, or the Outlook window in front of you. Power Automate for desktop closes part of that gap, at extra licensing cost.

Outlook web add-ins: supported, but a development project#

Web add-ins are the only extension model new Outlook supports: sandboxed JavaScript apps reaching the mailbox through the Office JavaScript API. Event-based activation lets one act when a message is composed or sent, which covers the auto-BCC, mandatory-field and disclaimer class of macros.

The catch is that this is software development, not an afternoon in the VBA editor: a build, hosting, admin deployment, and someone to maintain it as the API moves. Right for a team with a workflow worth the spend, wrong for one person's filing macro.

Check first whether a vendor already ships an add-in that does the job — our post on COM add-ins in new Outlook covers how to audit that. Commission anything new on Microsoft Graph, not Exchange Web Services, which Microsoft is retiring for third-party applications against Exchange Online.

Staying on classic Outlook is a legitimate answer#

If a macro is load-bearing and nothing above replaces it, keeping classic Outlook is often the right move — not procrastination, and not a stopgap measured in weeks. Microsoft supports classic until at least 2029, and its migration model runs in three staged steps: opt-in, opt-out, then a final cutover.

Years of runway changes the calculus: rebuild the macros with clean replacements now, keep classic for the ones with none, and re-check each quarter. Run two clients deliberately — pick your daily driver, and store the exported OTM file where the next person can find it.

The macros that have no clean equivalent#

The line is whether the code reaches out of the mailbox and into Windows. These have no supported replacement outside classic Outlook.

• Local and network file paths — a mapped drive, a lookup spreadsheet on disk, a log file. No cloud flow can see them.
• The Outlook object model — Explorer, Inspector, the current selection, custom ribbon buttons. None of it exists outside the classic desktop process.
• Driving other desktop apps — building a Word document, pushing rows into a workbook, printing or converting to PDF with the file names someone downstream depends on.
• MAPI-level property work — custom forms, user-defined fields on the message, anything stored where no supported API reaches.

Your options there are classic Outlook, or Power Automate for desktop treated as a Windows automation tool rather than a mail tool. SharePoint often beats a network share, but a macro printing picking lists to a warehouse printer is not so easily argued away.

Tools that automate this natively#

Everything above rebuilds your macros. The alternative is a client where the automation is already a feature. Here is that class of tool, starting with ours.

AI Emaily — we build it, so read this as the informed pitch it is. It connects Outlook and Microsoft 365 alongside Gmail, Yahoo, iCloud and any IMAP account, and puts the automation in the client rather than a scripting host. Rules and the Context brain (/features/rules-brain) take filing and classification: you describe the routing in plain English and it runs across every connected account. Drafting works from a Personal Context you set, plus per-client profiles you control — not from your old mail.

Copilot and Autopilot (/features/copilot-autopilot) take the reply half: in Copilot nothing sends without your approval, in Autopilot the agent acts inside limits you set, and every action has undo and an audit trail — more than a VBA script that misfiled a message ever left behind.

The limit, plainly: we do not run VBA and we are not a macro host. There is no way to paste a module into AI Emaily and have it execute. If your macro manipulates local files, drives Word or Excel, or touches the Outlook object model, we are not the answer — that needs classic Outlook or Power Automate. What we replace is the class of macro that files, classifies, summarises and drafts.

The alternatives, briefly. Power Automate is Microsoft's own and is strongest when the workflow leaves email. A custom or vendor web add-in is the only way to put your own logic inside new Outlook, at the highest cost. Zapier and Make connect Outlook to other apps by task volume, outside the inbox.

Two AI clients come up here with catches worth knowing: Fyxer meters incoming email volume with overage charges as of July 2026, hardest on the busiest inboxes, and Shortwave is Gmail-only, so it is no route for an Outlook macro user.

The short version#

VBA macros in new Outlook do not run, will not run, and no setting changes that. Work the list one macro at a time: filing to inbox rules, one-click actions to Quick Steps, triggered workflows to Power Automate, custom logic to a web add-in when the build is worth it.

Anything touching local files or the desktop object model has no supported replacement, so keep classic Outlook for it — you have until at least 2029, whatever the headlines say. And if what you actually want is for the filing and the first draft to happen without a script at all, that is the job of a client with the automation built in.