2026 Outlook Copilot: How to Create Inbox Rules?

Check availability and set the right goal

Before writing a prompt, confirm that Copilot’s rule-management feature appears in the Outlook account and interface you plan to use. Microsoft documents Copilot assistance for creating, viewing, updating, and deleting Outlook rules, but availability can vary by account, version, and rollout stage. The Microsoft guide to Copilot rule management describes the feature and the confirmation step. Check Microsoft’s minimum requirements for Microsoft 365 Copilot as well; don’t assume that seeing Copilot in one Outlook experience means every rule action is enabled in another.

Set a narrow goal before you start: sort future messages that meet a recognizable condition. Don’t begin with “clean up my inbox.” That request mixes two separate jobs—organizing messages already received and deciding what to do with messages that arrive later.

Copilot’s documented rule workflow shows a summary for review before you confirm rule creation. Microsoft describes the resulting rule as applying to future messages, not as an automatic bulk operation on your existing inbox. Keep those boundaries in mind when choosing what to automate.

Can Outlook Copilot help create email rules? Yes, if rule management is available for the account and interface in use. Copilot can assist with creating and managing rules, but the draft still needs a human review. If the feature isn’t present, use the rule controls available in that Outlook version or check Microsoft’s rollout and eligibility guidance rather than assuming your account is misconfigured.

Before creating a rule: write conditions you can verify

A useful rule has two clear parts: a condition that identifies the messages and an action that handles them. Common conditions include a sender, a phrase in the subject, or another identifiable message attribute. Actions can include moving a message to a folder or assigning a category. State both parts in plain language before asking Copilot to draft anything.

For example, a freelancer might ask for messages from a particular client address with a project code in the subject to go to a dedicated project folder. A subscription message could be sorted using its sender or a distinctive subject phrase. These examples are starting points, not universal conditions: the sender may use multiple addresses, and a phrase may also appear in important correspondence.

Avoid instructions such as “move all client mail” unless the rule can identify that mail reliably. A vague label like “client” may not match anything consistently, while a broad phrase like “invoice” could catch messages from several unrelated senders. If the condition can’t be checked against a real example, refine it before asking Copilot to act.

A good prompt names the intended sender or message pattern, the destination, and any important exclusions. For example: “Move messages from this client address with the project code in the subject to the Project folder. Don’t include messages from other senders.” The exclusion only helps if the interface supports that condition; check the resulting draft rather than assuming Copilot interpreted every phrase as a rule condition.

Draft review: inspect the conditions and actions

Ask Copilot for the rule in concrete terms. Then read its summary as if you were checking a form, not approving a general suggestion. Verify the sender or other matching condition, any subject criteria, the action, and the exact folder or category. Microsoft’s Copilot rule instructions explain that a summary is presented before you confirm creation.

How can you check the conditions and actions Copilot drafted? Compare each item in the summary with the request you wrote. Look for conditions that are missing, broadened, or interpreted differently, and confirm that the destination folder or category is the one you meant. If the summary is unclear, don’t confirm it. Rewrite the request to name the specific condition and outcome, then review the revised draft.

Pay particular attention to destinations that do not yet exist. If Copilot refers to a folder or category that isn’t available, decide whether it is appropriate to create it before proceeding. A similar name can still be the wrong destination, and a rule that points to an unintended folder can make messages appear to disappear from the main inbox.

Use this review table to choose what to adjust before confirmation:

Confirmation: create only the rule you reviewed

Confirm only after the summary matches the request. If anything looks off, go back to the prompt and revise it rather than relying on a later cleanup to undo an overbroad rule. The review step matters because a rule can quietly divert mail even when the wording of the original request seemed harmless.

Once confirmed, allow the rule to handle future matching messages. Don’t expect it to sort existing messages automatically. Will a Copilot-created Outlook rule process messages already in the inbox? Microsoft’s documentation describes these rules as applying to future mail; it does not say that creating one automatically reorganizes messages you already received. For older messages, use the relevant Outlook search, folder, or manual organization controls separately.

Outlook rule behavior and management controls can differ between clients and account types. Microsoft’s Outlook rules guide covers rule management across Outlook experiences. Follow the instructions that match the interface and account you actually use instead of applying a step from a different version by assumption.

After confirmation: test a new message

Test the rule with a low-risk message that should match it. Check whether the message arrives, whether the condition appears to match, and whether Outlook places it in the intended folder or applies the intended category. If a suitable test message is not available, wait for a routine message that meets the condition rather than sending something sensitive just to test the rule.

A simple verification log helps when several rules affect the same project or sender. Note the condition, intended action, destination, and whether the test message was handled as expected. This is a small operational record, not a requirement of Outlook; it makes later troubleshooting easier when a sender changes address or a subject format changes.

Don’t respond to one missed message by widening the condition immediately. First compare the message’s actual sender, subject, and other relevant details with the saved rule. Otherwise, a change meant to catch one exception may send unrelated mail to the same destination.

Maintenance: edit, disable, or remove a rule

When sorting goes wrong, inspect the saved rule before changing it. Check whether it is enabled, whether its conditions still match the messages you want, and whether its action still points to the right folder or category. If the message didn’t meet the rule’s conditions, the correct fix may be a more precise condition—not a broader one.

Edit a rule when the intended sorting job is still valid but a condition or destination has changed. Disable it temporarily when you need to stop its effect while investigating. Delete it when the workflow is no longer useful. The available controls and navigation can differ by Outlook interface, so use Microsoft’s rules management instructions for the version in use.

A rule is only one layer of inbox management. It can organize messages after they reach an account, but it does not give a service a new address to send to. If the original condition depends on a sender’s address, a sender change can also make the rule stop matching. Revisit rules when a client changes its sending address, a project ends, or a folder structure changes.

Long-term setup: rules and aliases do different jobs

Outlook rules and email aliases solve different problems. A rule decides what Outlook does with mail after it arrives. An alias provides a distinct address for a particular purpose, while messages sent to that address can still be handled within a broader mailbox setup. An alias is useful when you want separate entry points for clients, projects, or subscriptions; a rule is useful when you want matching messages sorted after delivery.

What should rules and email aliases manage? Use rules for classification and movement inside an inbox. Use an alias when the address itself should distinguish a use, such as a project or a long-term subscription. If a particular address starts receiving unwanted mail, moving messages to another folder is not the same as disabling that address. Whether an alias can be disabled or managed in a particular way depends on the email service that provides it.

For a long-running client relationship, a persistent alias can keep the address used for that client distinct from a personal address; an Outlook rule can then sort the messages. For a brief trial or signup, a temporary address may be more appropriate than creating a permanent alias. For banking, government, payment, account recovery, or any service that must reach you over time, use an address you can reliably access and recover.

If you’re comparing temporary and longer-term inbox use, HideRelay’s inbox and sandbox guide explains the distinction, and its email terminology guide can help clarify alias and forwarding terms. Check the current HideRelay service page for availability and handling details rather than assuming a temporary address behaves like a permanent alias.

To create the rule, use this compact decision sequence:

• If the goal is to sort future mail already arriving in Outlook, create a narrowly defined rule and test it.
• If the goal is to give a particular project or service a distinct address over time, consider an alias and then use a rule for sorting.
• If the goal is a short-lived signup or test, consider a temporary email address instead of adding another permanent route to the main inbox.
• If reliable long-term access or replies are essential, use an address and mailbox you control over time.

After verifying Outlook’s rule with a low-risk message, choose the address layer separately. For a one-off registration or test, HideRelay can provide an immediately usable temporary inbox without requiring signup, helping keep a primary address out of a short-term form and reducing unwanted follow-up mail there. For ongoing client correspondence or important account recovery, keep using a durable address or alias you can manage.