How to Add Outlook Rules: 2026 Step-by-Step Guide

The fastest path — new Outlook for Windows or Outlook on the web

1. Open the new Outlook for Windows (or sign in at outlook.office.com)
2. Click the Settings gear icon (top right)
3. Choose Mail → Rules
4. Click + Add new rule
5. Name the rule (e.g., “Move finance notifications”)
6. Add a condition — e.g., From: finance@acme.com or Subject includes: Invoice
7. Add an action — e.g., Move to: /Finance folder
8. (Optional) Add an exception — e.g., Except if Importance is High
9. (Optional) Check “Stop processing more rules” if this should be the last rule evaluated for matching messages
10. Click Save

The rule runs automatically on subsequent incoming mail. To also apply it to messages already in your mailbox, hover over the rule in the rules list and click Run now.

The same task across every Outlook surface

Server-side vs client-only rules — which to pick

Server-side rules run on Exchange Online (or Exchange Server) automatically as mail arrives. They apply across every device that accesses the mailbox — desktop, web, mobile — regardless of whether Outlook is open. This is the modern default and the only option in new Outlook / OWA / Outlook mobile.

Client-only rules run only when classic Outlook for Windows is open and connected. They're required for actions that can't execute server-side (e.g., “Play a sound”, “Display a desktop alert”, or actions that depend on the local PC). In classic Outlook, client-only rules show a small computer icon in the rules list.

Rule of thumb: use server-side rules unless you specifically need a client-only action. Server-side rules survive client reinstalls, OS changes, and device switches.

Rules quota and limits

Exchange Online mailboxes have a default 256 KB total rule-size quota per mailbox (not a count of rules). Each rule consumes roughly 1-3 KB depending on complexity, so the practical limit is around 100-200 rules per mailbox. If you hit the quota, Outlook returns “There is not enough space to save your rule.”

If you need more room, your Microsoft 365 admin can raise the quota to the maximum 512 KB via PowerShell:

Set-Mailbox -Identity user@contoso.com -RulesQuota 512KB

For organizations that need rule logic richer than Outlook itself supports — multi-step workflows, calls to external APIs, conditional notifications to Teams, approvals — consider moving the logic into Microsoft Power Automate. Power Automate has higher limits, an extensive connector catalog, and is the supported pattern for enterprise email automation in 2026.

What Microsoft 365 Copilot adds in 2026

In Outlook on the web and new Outlook for Windows with M365 Copilot licensed, the Copilot side pane includes an option to “Help me organize my inbox”. Copilot reviews your recent email patterns and proposes rules — for example, “Move all messages from finance@acme.com to /Finance” or “Categorize newsletters from these 12 senders.” You review each suggestion individually and click to approve before it becomes a rule.

Copilot does not auto-create rules without your confirmation. The feature is part of Microsoft 365 Copilot ($30/user/month add-on in 2026) and respects sensitivity labels, retention policies, and Microsoft Purview governance — Copilot will not suggest actions that violate enforced compliance controls.

How rules interact with Microsoft Purview governance

Outlook rules cannot override Microsoft Purview-enforced controls. If a sensitivity label or retention policy applies to a message, the rule still runs — but actions that would bypass the policy (e.g., “Forward to external address” for a Confidential-labeled message) are blocked at the Exchange transport layer. This is one reason EPC Group recommends Microsoft Purview deployment before opening up broad rule creation to end users in regulated industries.

For more on the Microsoft 365 governance pattern that underpins safe Outlook rule creation at scale, see the Governed AI on Microsoft Framework.

Common Outlook rule patterns enterprises use

• Move newsletters out of inbox — From: any address ending in @newsletter.* → Move to: /Newsletters
• Flag mail from your VIPs — From: leadership distribution list → Flag for follow-up + Mark importance High
• Auto-archive notifications — Subject contains “noreply” OR From: noreply@* → Move to: /Notifications
• Out-of-office routing — Subject contains “urgent” → Forward to backup colleague (paired with auto-reply during PTO)
• Compliance hold filter — From: legal@* → Move to: /Legal-Hold (a folder under Microsoft Purview retention policy)

When Outlook rules are the wrong tool

Stop using Outlook rules and move logic into Microsoft Power Automate when:

• You need to call an external API or webhook
• You need to route a single message to multiple systems (e.g., create a Planner task AND post to Teams AND log to a SharePoint list)
• The condition needs business logic that Outlook can't express (e.g., “if sender is a customer in our CRM AND the message contains a contract attachment”)
• You need approvals before the action runs
• You need shared rules across an entire team or distribution list (rules are per-mailbox; flows can target a shared mailbox or group)

EPC Group's Outlook rule consulting

For enterprise rollouts where Outlook rule governance matters (regulated industries, large multi-tenant environments, or migrations from Lotus Notes/Google Workspace where users carry hundreds of rules into the new tenant), EPC Group runs Outlook rule audits + rule consolidation as part of the broader Microsoft 365 migration practice. See /services/microsoft-365-migrations.