New Outlook vs Classic Outlook VBA Macros: What to Use Instead

If you rely on VBA macros to automate tasks in Classic Outlook, you may have discovered that the New Outlook for Windows does not support VBA at all. Microsoft removed the VBA engine from the New Outlook architecture to improve security, performance, and cross-platform compatibility. This article explains why Classic Outlook supports VBA macros, why New Outlook blocks them, and what automation tools you can use instead to replace your existing macros.

You will learn the technical differences between the two Outlook versions regarding macro execution, the exact features that are lost, and the alternative automation methods available in New Outlook. The focus is on practical replacements such as Power Automate, COM add-ins, and script-based solutions that work without VBA. By the end, you will know exactly which automation path to take based on your specific macro use case.

Why Classic Outlook Supports VBA Macros and New Outlook Does Not

Classic Outlook runs the full Microsoft Office VBA engine, which allows users to write and execute macros that automate repetitive tasks such as moving emails, formatting messages, or exporting calendar items. The VBA engine is a local component that runs with the same privileges as the Outlook process. This design gives users deep control but also introduces security risks because malicious macros can execute arbitrary code on the machine.

New Outlook for Windows is built on a web-based architecture that uses the same codebase as Outlook on the web and the Outlook mobile apps. This architecture does not include the VBA runtime. Microsoft made this decision to reduce the attack surface, simplify updates, and ensure consistent behavior across platforms. As a result, any VBA macro that worked in Classic Outlook will not run in New Outlook. The macro editor, the Visual Basic Editor, and the Trust Center settings for macros are all absent.

What Happens to Existing VBA Macros When You Switch

When you migrate from Classic Outlook to New Outlook, your existing VBA macros are not carried over. The macro projects stored in the VBAProject.OTM file are ignored by New Outlook. You cannot import them, run them, or edit them. The only way to keep using those macros is to stay on Classic Outlook. If you switch to New Outlook, you must recreate the automation using one of the alternative methods described in the next section.

Alternative Automation Methods for New Outlook

Microsoft provides three main alternatives to VBA macros in New Outlook: Power Automate, COM add-ins, and Office Scripts. Each method has different capabilities and limitations. The table below summarizes the key differences, and the following sections explain how to set up each option.

Power Automate Flows for Email Automation

Power Automate is a cloud-based service that lets you create flows triggered by Outlook events such as receiving an email, creating a calendar event, or sending a message. You do not need to write code. Flows are built using a visual designer with prebuilt connectors for Outlook, Teams, SharePoint, and hundreds of other services.

1. Open Power Automate
   Go to make.powerautomate.com and sign in with your Microsoft 365 work or school account.
2. Create a new automated cloud flow
   Click Create and select Automated cloud flow. Choose a trigger such as When a new email arrives (V3) for Outlook.
3. Add actions to the flow
   Click New step and select an action like Move email, Send an email, or Create a calendar event. Configure the parameters based on your original macro logic.
4. Test and enable the flow
   Click Test to run the flow with a sample email. Once it works, turn on the flow toggle so it runs automatically.

COM Add-ins for Complex Local Automation

COM add-ins are compiled DLL files that extend Outlook functionality. Unlike VBA macros, COM add-ins run as separate processes and can be installed by an administrator. They work in both Classic Outlook and New Outlook, but only if the add-in is built using the Outlook JavaScript API or the Web Add-in framework. Classic COM add-ins built with .NET or C++ may not work in New Outlook unless they are updated to use the new extensibility model.

To install a COM add-in in New Outlook, go to File > Options > Add-ins. Click Manage and select COM Add-ins. Browse to the add-in file and confirm the installation. Note that many third-party add-ins already support New Outlook. Check the vendor documentation before switching.

Office Scripts for Web-Based Automation

Office Scripts is a TypeScript-based scripting language that works in Excel on the web and is gradually expanding to other Office applications. As of now, Office Scripts does not support Outlook directly. However, you can use Office Scripts in Excel to process data exported from Outlook. This is not a direct replacement for Outlook VBA macros, but it can handle tasks like formatting exported email data or generating reports.

Common Limitations When Replacing VBA Macros

Power Automate Cannot Access Local Files

Power Automate flows run in the cloud and cannot access files on your local hard drive. If your VBA macro reads or writes files on your PC, you need to use a desktop flow in Power Automate Desktop or switch to a COM add-in that runs locally. Power Automate Desktop is a separate application that can automate desktop applications, including Outlook, but it requires a per-user license.

Real-Time Event Triggers Are Limited

VBA macros can respond to Outlook events such as ItemSend, ItemOpen, or FolderChange with sub-second latency. Power Automate flows have a delay of several seconds to a few minutes depending on the trigger type and service load. For time-critical automation, such as blocking emails before they are sent, Power Automate may not be fast enough. In that case, a COM add-in or staying on Classic Outlook is the better choice.

No Direct Replacement for Custom Dialog Boxes and Forms

VBA macros can display custom dialog boxes and modify Outlook forms. New Outlook does not support custom forms or VBA-based user forms. The alternative is to build a custom web-based add-in using the Outlook JavaScript API, which can display task panes and dialogs. This requires development skills in HTML, CSS, and JavaScript. For simple prompts, you can use Power Automate with a manual trigger that asks for input when the flow runs.

Classic Outlook VBA vs New Outlook Automation: Key Differences

Item	Classic Outlook VBA	New Outlook Alternatives
Execution environment	Local VBA engine inside Outlook process	Cloud (Power Automate) or separate process (COM add-in)
Latency	Sub-second response to events	Several seconds to minutes for Power Automate
File system access	Full access to local files and folders	No local file access in Power Automate; COM add-ins can access local files
Custom UI	Custom dialog boxes and forms	Task panes via web add-ins; no custom forms
License requirement	Included with Microsoft 365	Power Automate requires a separate license for premium connectors; COM add-ins may require purchase
Security model	Trust Center settings control macro execution	Admin-managed add-in policies; no macro trust settings

If you depend on VBA macros for daily tasks, switching to New Outlook requires planning. For simple email sorting and notification flows, Power Automate is the easiest replacement. For advanced automation that needs local file access or real-time response, a COM add-in or staying on Classic Outlook is the only viable option. Microsoft has not announced any plans to bring VBA support to New Outlook, so the alternatives listed here are the long-term solutions.