Outlook Rules Stop Working After Mailbox Migration: Fix

After migrating your mailbox to a new server or a different Microsoft 365 tenant, your Outlook rules may stop running. The rules remain visible in the Rules and Alerts dialog but do not fire for incoming or outgoing messages. This happens because the rule conditions or actions reference the old server path, folder IDs, or account names that no longer exist in the new environment.

The root cause is that Outlook stores rules in two places: locally in the mailbox as a hidden message in the Inbox folder and in the Exchange mailbox server. When the mailbox moves, the server-side copy of the rules may become stale or its internal identifiers may break. This article explains how to force Outlook to re-sync and rebuild the rule set so that your rules work again after a migration.

You will learn three methods to fix broken rules: clearing and re-creating the client-side rule cache, using Outlook Web App to remove and re-add the rules, and running a PowerShell command to flush the server-side rule cache. Each method targets a different layer of the rule storage problem.

Why Outlook Rules Stop Working After a Mailbox Migration

When you migrate a mailbox between Exchange servers, on-premises to Exchange Online, or between Microsoft 365 tenants, the underlying folder IDs and mailbox GUIDs change. Outlook rules store references to specific folders by their Entry ID, which is a binary value that changes after migration. If a rule moves messages to a folder that no longer has the same Entry ID, the rule fails silently. The rule remains in the list but does not execute.

A second cause is that Outlook maintains a local copy of rules in a file called Outlook.srs (Send/Receive Settings) and in the mailbox as a hidden message. After migration, the local copy may reference the old server path. Outlook cannot match the old references to the new server, so it disables the rule. The rule still appears enabled in the UI, but the client marks it as invalid and skips it during mail processing.

A third cause involves the Exchange Mailbox Replication Service (MRS). During a migration, MRS copies the rule collection from the source mailbox to the target mailbox. If the migration tool encounters a corrupted or oversized rule, it may skip the entire rule collection. The user sees zero rules after migration, even though rules were present on the source.

How Rule Storage Works in Exchange and Outlook

Outlook stores rules in a hidden folder named Inbox under the IPM.Rule.Message message class. Exchange Online and on-premises Exchange keep a server-side copy that is applied by the transport agent. When you create or modify a rule in Outlook, the client sends a SetInboxRule command to Exchange. After migration, the server-side copy may become the authoritative version, but the client-side cache still holds the old data. This mismatch causes the rule to fail.

Method 1: Clear the Client-Side Rule Cache in Outlook

This method forces Outlook to discard its local copy of the rules and download a fresh copy from the server. It works when rules appear in the list but do not execute after migration.

1. Open the Rules and Alerts dialog
   In Outlook, go to File > Manage Rules & Alerts. If you use Outlook on the web, skip to Method 2.
2. Click Options
   In the top-right corner of the Rules and Alerts dialog, click the Options button. A new dialog named Options appears.
3. Click Clear Client-Side Rules Cache
   In the Options dialog, locate the section labeled Client-Side Rules Cache. Click the button Clear Client-Side Rules Cache. Outlook deletes the local cache file but does not remove rules from the server.
4. Restart Outlook
   Close and reopen Outlook. The client detects that the cache is empty and downloads the rules from the server again. Test a rule by sending a test message that matches a rule condition.

If the rules still do not fire after restarting Outlook, proceed to Method 2.

Method 2: Delete and Recreate Rules Using Outlook Web App

Outlook Web App (OWA) does not use a local cache. Editing rules in OWA forces a direct server-side update. This method works when Outlook shows rules but OWA does not execute them.

1. Open Outlook Web App
   Sign in to your mailbox at outlook.office.com or your on-premises OWA URL.
2. Go to Mail settings
   Click the gear icon in the top-right corner, then click View all Outlook settings. In the left pane, click Mail, then click Rules.
3. Delete all existing rules
   Select each rule one by one and click the Delete icon (trash can). Write down the rule conditions and actions if you need to recreate them exactly.
4. Recreate the rules
   Click Add a new rule. Enter the same conditions and actions you wrote down. Use the same folder names as before. Click Save.
5. Test the rules in OWA
   Send a test email to yourself. Check if the rule runs in OWA. If it works in OWA but not in Outlook, go to File > Manage Rules & Alerts in Outlook and click Run Rules Now to force a sync.

Method 3: Use PowerShell to Remove and Reapply Server-Side Rules

This method is for administrators who manage mailboxes in Exchange Online or on-premises Exchange. It removes the server-side rule collection so that the client can upload a clean set.

1. Connect to Exchange Online PowerShell
   Open Windows PowerShell as administrator. Run Connect-ExchangeOnline -UserPrincipalName admin@domain.com and sign in with your admin credentials.
2. View the user’s current rules
   Run Get-InboxRule -Mailbox user@domain.com to list all rules. Note the rule names and identities.
3. Remove all rules
   Run Get-InboxRule -Mailbox user@domain.com | Remove-InboxRule -Force. This deletes every rule on the server. The -Force parameter skips confirmation prompts.
4. Ask the user to recreate rules in Outlook
   Instruct the user to open Outlook, go to File > Manage Rules & Alerts, and create the rules again. The new rules will have fresh Entry IDs that match the migrated mailbox.
5. Verify rule execution
   Send a test email. Check if the rule runs. You can also run Get-InboxRule -Mailbox user@domain.com again to confirm the rules are present.

If Outlook Still Has Issues After the Main Fix

Outlook Does Not Show the Rules and Alerts Dialog

If the Rules and Alerts dialog is grayed out or missing, the mailbox may be in a disconnected state. Close Outlook, open Control Panel, click Mail, and then click Email Accounts. Select your profile and click Repair. After the repair completes, restart Outlook and try again.

Rules That Move Messages to a Deleted Folder

After migration, a folder that was referenced in a rule may have been renamed or deleted. Open the folder list in Outlook. If the target folder is missing, create it with the exact same name. Then edit the rule in Rules and Alerts and reselect the folder from the folder picker.

Rules That Forward Email to an External Address

Exchange Online has a forwarding limit of 10 recipients per rule. If the rule forwards to more than 10 addresses, the rule fails. Reduce the number of recipients or use a distribution group instead. Edit the rule in OWA to apply the change directly to the server.

Client-Side Rule Cache vs Server-Side Rule Storage: Key Differences

Item	Client-Side Rule Cache	Server-Side Rule Storage
Location	Local file Outlook.srs in %LocalAppData%\Microsoft\Outlook	Hidden message in the mailbox Inbox folder
Persistence after migration	Retains old Entry IDs that break after migration	Copied during migration but may be skipped if corrupted
How to clear	File > Manage Rules & Alerts > Options > Clear Client-Side Rules Cache	PowerShell Remove-InboxRule or delete in OWA
Affects Outlook only	Yes	No, also affects OWA and mobile clients
Best fix after migration	Clear cache first	Delete and recreate rules in OWA

After a mailbox migration, Outlook rules stop working because the local cache and server-side rule store contain stale folder Entry IDs. Clearing the client-side cache in the Rules and Alerts Options dialog forces Outlook to download fresh rules from the server. If that does not work, deleting and recreating the rules in Outlook Web App or using the Remove-InboxRule PowerShell cmdlet resets the server-side rule collection entirely. Before recreating rules, write down the conditions and actions so you can restore them quickly. For administrators, running a Get-InboxRule export before migration provides a backup in case the rule set is lost.