Outlook Rule Fires for Internal Mail But Not External: Account Scope Fix

You created an Outlook rule to move, flag, or forward messages, but it only runs when the sender is inside your company. External messages from customers, vendors, or public domains pass through the rule without any action being taken. This happens because the rule is configured to apply only to messages sent to or from a specific email account, and the condition does not match external senders. This article explains why the account scope setting causes this behavior and provides the exact steps to remove the account restriction so your rule processes both internal and external email.

Why an Outlook Rule Only Fires for Internal Mail

Outlook allows rules to be scoped to a specific email account when you have multiple accounts configured in one profile. For example, if you have your corporate account and a personal Outlook.com account, a rule can be set to act only on messages sent to or from the corporate account. This account-scope condition is applied automatically when you create a rule using the “Apply this rule after the message arrives from” wizard step and select a specific account from the dropdown.

The problem occurs when the rule is meant to handle all incoming messages but was accidentally created with the account condition. Internal messages that match the account condition pass through the rule correctly. External messages, which are still received by the same account, are evaluated by Outlook as not matching the account scope condition. As a result, the rule does not fire for external senders.

This is not a bug. It is a deliberate design to let users apply different rules to different accounts. The fix is to edit the rule and remove the account condition entirely.

Steps to Remove the Account Scope from a Rule

The following steps will remove the account condition from an existing rule. After this change, the rule will apply to all messages regardless of the sender’s domain or the account that received the message.

1. Open the Rules and Alerts dialog
   In Outlook, go to File > Manage Rules & Alerts. This opens the Rules and Alerts window where all rules are listed.
2. Select the problem rule
   Click the rule that fires only for internal mail. The rule name appears in the list. Do not double-click it yet.
3. Click Change Rule then Rule Settings
   On the toolbar above the rule list, click Change Rule > Rule Settings. The Rules Wizard opens and shows all conditions currently set for the rule.
4. Locate the account condition
   In the Step 1: Select condition(s) list, look for “from” or “sent to” a specific account. This condition is checked if the rule was scoped to an account. You may see it as “from a specific account” or “sent to a specific account” depending on how the rule was created.
5. Uncheck the account condition
   Uncheck the box next to “from” or “sent to” a specific account. Do not change any other conditions.
6. Click Next and confirm actions
   Click Next. The wizard moves to the actions step. Verify that the action you want (move, flag, forward, etc.) is still selected. Click Next again to reach the exceptions step. Review or skip exceptions, then click Next.
7. Name and finish the rule
   On the final page, confirm the rule name and check the box Turn on this rule. Click Finish. The rule now applies to all messages received by any account in your profile.

If the Rule Still Does Not Process External Mail

Rule is set to run only on this computer

Some rules are marked as client-only, meaning they run only when Outlook is open on your computer. If you use Outlook Web Access or another device, the rule may not run there. Client-only rules have a small icon of a computer next to them in the Rules and Alerts list. To change this, edit the rule and uncheck “on this computer only” if you want the rule to run on the Exchange server. Note that some rule actions like “play a sound” cannot run server-side.

Rule has an exception that blocks external mail

If the rule has an exception like “except if the sender is inside my organization”, it will skip all internal messages and only process external ones. This is the opposite of what you want. Check the exceptions step in the Rules Wizard and remove any exception that filters by sender domain or organization membership.

Multiple rules are conflicting

Outlook processes rules in the order they appear in the list. If a rule earlier in the list moves or deletes a message before your rule runs, your rule never gets a chance to act. Drag your rule to the top of the list in the Rules and Alerts window. If you want to test without changing order, temporarily disable all other rules and test again.

Account-Scoped Rule vs Server-Side Rule: Key Differences

Item	Account-Scoped Rule	Server-Side Rule (Exchange)
Scope	Applies only to messages sent to or from a specific email account	Applies to all messages in the mailbox regardless of account
Location	Stored in the Outlook client on your computer	Stored on the Exchange server
Run condition	Runs only when Outlook is open	Runs even when Outlook is closed
Supported actions	All actions including sounds and desktop alerts	Limited to move, copy, delete, forward, and reply actions
Common fix	Remove the account condition in Rules Wizard	No account condition exists; focus on conditions and exceptions instead

The table above shows that account-scoped rules are client-only and limited to one account. Server-side rules are broader but have fewer action options. If you need a rule to run on all messages and work when Outlook is closed, consider converting the rule to a server-side rule by removing the account condition and any client-only actions like “play a sound.”

After removing the account scope, you can now create rules that process both internal and external email without restriction. For future rules, avoid selecting a specific account in the first step of the Rules Wizard unless you intentionally want to limit the rule to one account. Use the Ctrl+Shift+L shortcut to open the Rules and Alerts window quickly and review any new rule before activating it.