When you use Copilot in Outlook alongside Inbox Rules, the order in which these two systems process incoming email can cause unexpected results. Copilot may summarize or suggest actions on messages that have not yet been moved, flagged, or deleted by your rules. This article explains the technical sequence of how Outlook applies rules and then triggers Copilot. You will learn the exact execution order and how to design rules that work reliably with Copilot.
Key Takeaways: Copilot and Inbox Rules Order of Execution
- Server-side rules run before Copilot processes any email: Copilot sees only the messages that survive server-side rule actions like move or delete.
- Client-side rules run after Copilot has already analyzed the message: Copilot may generate summaries or suggestions that become stale if a client-side rule later moves or deletes the email.
- Copilot processes messages in the Inbox folder only: If a rule moves a message to a subfolder, Copilot will not process it unless that folder is part of a Copilot-enabled scope.
How Outlook Inbox Rules and Copilot Interact
Outlook Inbox Rules are automated actions that run when a new email arrives. They can move messages to folders, delete them, forward them, or flag them. Copilot in Outlook is an AI assistant that reads email content to provide summaries, suggest replies, and draft meeting requests. Both systems operate on the same incoming messages, but they do not run at the same time.
The execution order is determined by where the rule runs. Outlook supports two types of rules: server-side rules and client-side rules. Server-side rules run on the Exchange Online server before the message reaches your mailbox. Client-side rules run on your local machine after the message has been downloaded. Copilot processes messages after server-side rules but before client-side rules.
Server-Side Rule Execution
Server-side rules are the default for most rules in Exchange Online. They execute on the server as soon as the email arrives. Actions such as move to folder, delete, forward, and reply with a template run here. Copilot does not see messages that are deleted or moved out of the Inbox by a server-side rule. This means if you have a rule that moves all newsletter emails to a Newsletters folder, Copilot will never process those newsletter emails.
Client-Side Rule Execution
Client-side rules run only when Outlook is open and connected to the Exchange server. They execute after the message has been delivered to your Inbox and after Copilot has already scanned the message. Common client-side actions include moving messages based on custom conditions, playing a sound, or displaying a desktop alert. Because Copilot runs first, it may produce a summary or a suggested reply for a message that your client-side rule later moves to a different folder. The Copilot-generated content then becomes orphaned in the Inbox context.
Steps to Verify and Adjust Rule Execution Order
- Open Outlook and go to Rules settings
In Outlook on the web, select Settings gear icon, then View all Outlook settings. Choose Mail, then Rules. In the Outlook desktop app, select File, Manage Rules and Alerts. - Identify each rule type
Look at the rule description. If the rule uses actions like move, delete, or forward, it is likely a server-side rule. If it uses actions like play a sound or display a notification, it is a client-side rule. Rules that move messages to a folder on a local PST file are also client-side. - Reorder server-side rules
In the Rules list, use the Move Up and Move Down buttons to change the order of server-side rules. The first matching server-side rule stops processing. Copilot will only see messages that survive all server-side rules. - Convert client-side rules to server-side when possible
If a client-side rule moves messages to a folder in your mailbox, recreate it as a server-side rule. Server-side rules use the same conditions but run before Copilot. To convert, delete the client-side rule and create a new rule with the same conditions but without client-side-only actions. - Test with a sample email
Send a test email that matches your rule conditions. Check whether Copilot generates a summary or suggestion. Then check the folder where the rule should have moved the message. If Copilot processed the message and the rule moved it, the rule is client-side. If the message moved and Copilot has no record of it, the rule is server-side.
If Copilot and Inbox Rules Produce Conflicting Results
Copilot Summarizes a Message That Was Moved by a Rule
This happens when a client-side rule moves the message after Copilot has already processed it. The Copilot summary remains in the Inbox conversation view until you refresh or manually remove it. To fix this, convert the client-side rule to a server-side rule. If conversion is not possible because the rule uses client-side-only actions, move those actions to a second rule that runs after Copilot has finished.
Copilot Does Not Process Messages That Should Be Summarized
If a server-side rule moves messages out of the Inbox before Copilot can read them, Copilot will never see those messages. To allow Copilot to process specific messages, create an exception in the server-side rule that prevents the move action for messages you want Copilot to handle. Alternatively, change the rule to copy the message instead of moving it, or set the rule to run after Copilot by converting it to a client-side rule.
Copilot Suggests Actions on Messages That Were Already Deleted by a Rule
This indicates the rule is client-side and runs after Copilot. The Copilot suggestion is based on the message content before deletion. To prevent this, change the rule to server-side so the deletion happens before Copilot sees the message. If you need the rule to remain client-side, disable Copilot for that specific message type by creating a rule that marks the message with a category that Copilot ignores.
Server-Side Rules vs Client-Side Rules: Key Differences for Copilot Users
| Item | Server-Side Rules | Client-Side Rules |
|---|---|---|
| Execution location | Exchange Online server | Local Outlook client |
| Execution timing relative to Copilot | Before Copilot processes the message | After Copilot processes the message |
| Copilot sees the message | Only if the rule does not move or delete it | Always, regardless of rule actions |
| Actions supported | Move, delete, forward, reply with template, mark as read | All server-side actions plus play sound, display notification, run script, move to PST folder |
| Requires Outlook to be running | No | Yes |
Understanding this table helps you decide which rule type to use for each scenario. If you want Copilot to ignore certain messages, use a server-side rule to move or delete them. If you want Copilot to process all messages and then apply a local action, use a client-side rule.
Now you can design Inbox Rules that work predictably with Copilot in Outlook. Check your existing rules and convert any client-side rules that move or delete messages to server-side rules. For rules that must remain client-side, add a note in the rule description so you remember that Copilot will process the message first. A practical next step is to test a rule that moves vendor emails to a Vendor folder and verify that Copilot does not generate summaries for those messages.