Rules you create in the new Outlook for Windows may not run as expected. This happens because the new Outlook uses a different rules engine than the classic desktop application. Your rules might be missing, fail silently, or not trigger on incoming messages. This article explains the root cause and provides steps to rebuild your rules so they work reliably.
Key Takeaways: Fixing Rules in New Outlook
- File > Account Settings > Manage Rules & Alerts: Opens the classic rules management dialog in the new Outlook interface.
- Rules Wizard > New Rule: The tool to rebuild rules from scratch using server-side compatible conditions and actions.
- Run Rules Now: Manually tests a rule on existing messages to verify it works before relying on automation.
Why Rules Fail in the New Outlook App
The new Outlook for Windows is built on a different codebase than the classic Win32 application. It uses a modern web-based architecture shared with Outlook on the web. The rules engine in this new version is designed primarily for server-side processing with Microsoft 365 Exchange Online mailboxes.
Many advanced rules created in the classic Outlook client rely on client-only conditions or actions. Examples include moving messages to a local PST file folder or using VBA script triggers. The new Outlook rules engine cannot process these client-dependent commands. When you switch to the new Outlook, these incompatible rules are either ignored or partially broken.
Server-Side vs. Client-Only Rules
A server-side rule runs on the Microsoft Exchange server. It works even when Outlook is closed. A client-only rule requires the Outlook desktop app to be running on your computer. The new Outlook strongly favors server-side rules for reliability across devices. If your old rule involved a local data file or a custom script, it will not function in the new environment.
Steps to Recreate a Working Rule in New Outlook
The most reliable fix is to delete the broken rule and create a new one using the classic Rules Wizard interface. This ensures you use compatible conditions.
- Open the Rules and Alerts Dialog
In the new Outlook, click File in the top-left corner. Select Account Settings and then choose Manage Rules & Alerts from the dropdown menu. - Delete the Problematic Rule
In the Rules and Alerts dialog, select the rule that is not working from the list. Click the Delete button above the list to remove it. Confirm the deletion if prompted. - Start the Rules Wizard
Click the New Rule button on the dialog’s toolbar. The Rules Wizard window will open, presenting templates like “Move messages from someone to a folder.” - Choose a Template or Start from Blank
Select a template that matches your goal, or choose “Apply rule on messages I receive” at the top to start with a blank rule. Click Next to proceed. - Define Your Conditions
Check the boxes for your conditions, such as “from people or public group” or “with specific words in the subject.” Click the underlined value in the lower pane to specify details like an email address. Click Next. - Select Your Action
Check the box for the action you want, like “move it to the specified folder” or “delete it.” Click the underlined value to choose the target folder. Avoid actions related to PST files or client alerts. Click Next. - Add Any Exceptions and Finish
Add exceptions if needed, then click Next. Give your rule a clear name. Ensure the box for “Turn on this rule” is checked. Click Finish to save it. - Test the Rule Immediately
Back in the Rules and Alerts dialog, select your new rule. Click Run Rules Now. In the dialog, select the rule and choose which folder to test it on. Click Run Now to verify it works on existing messages.
If Your Rule Still Does Not Work After Recreation
“Run a Script” Action Is Missing
The “run a script” action requires Visual Basic for Applications. This feature is not supported in the new Outlook. You cannot recreate this rule. Consider using Power Automate for Microsoft 365 to create a cloud-based workflow as an alternative.
Rule Moves Messages to a PST File Folder
The new Outlook has limited support for local PST files. Rules cannot automatically file messages into them. Move your target folder to your main Exchange mailbox. Update the rule to point to that new mailbox folder instead.
Rule Triggers on a Specific Received Date
The “received in a specific date span” condition is a client-only filter. The new Outlook rules engine will ignore it. Use the “received today” or “received this week” condition as a workaround for recent messages.
Classic Rules vs. New Outlook Rules: Key Differences
| Item | Classic Outlook Rules | New Outlook Rules |
|---|---|---|
| Processing Engine | Client-based or server-based | Primarily server-based for Exchange Online |
| PST File Support | Full support for rules targeting PST folders | Very limited, rules cannot target PSTs |
| Script & Custom Action Support | Supports “run a script” and custom forms | No support for VBA scripts or custom actions |
| Rule Availability | Rules stored on client or server | Rules stored on Exchange server only |
| Advanced Conditions | Includes “with specific words in the body” | May lack some body-text filtering precision |
You can now rebuild email rules that work consistently in the new Outlook. Focus on using server-compatible conditions like sender, subject, and recipient. Test each new rule with the Run Rules Now feature. For complex automation that involved scripts, explore Microsoft Power Automate to create a cloud-based replacement.