August 2026 · Henry Bravo

Why Do My Outlook Rules Keep Turning Off?

Rules that deactivate themselves — sometimes daily — are one of the most frustrating Outlook problems, because nothing looks broken. Here is what is actually happening, and how to tell which of the three causes applies to you.

Outlook rules turn themselves off for three distinct reasons, and each needs a different fix. The most common by far is the mailbox rules quota: Exchange gives each mailbox a fixed budget for the combined size of all its rules — 256 KB on Exchange Online, and 64 KB by default on Exchange Server 2007 and later — and disabled rules still count against it. When you exceed the budget, Exchange deactivates rules and Outlook reports “One or more rules couldn’t be uploaded to Exchange server and have been deactivated.” The second cause is a client-only rule that cannot be stored on the server at all. The third is the same rule existing on two computers and conflicting. This guide shows you how to tell which one you have.

The Error Message, and What It Actually Means

When Outlook disables a rule on its own, the message you see is:

One or more rules couldn’t be uploaded to Exchange server and have been deactivated. This could be because some of the parameters aren’t supported or there’s insufficient space to store all your rules.

That single message covers two completely different problems, which is why it is so unhelpful. “Some of the parameters aren’t supported” means the rule is client-only and cannot live on the server. “Insufficient space” means you are over the rules quota. Everything below is about telling those two apart.

Cause 1: You Are Over the Rules Quota

Exchange stores your rules inside your mailbox, and it caps the total size of that set. The cap is per mailbox:

Exchange Online (Microsoft 365): 256 KB.
Exchange Server 2007 and later: 64 KB by default, raisable by an administrator to a maximum of 256 KB.
Exchange Server 2003: 32 KB, fixed.

The important thing about that number is that it is a size, not a count. There is no maximum number of rules in Outlook. Ten rules can exhaust the quota while another person runs sixty without trouble, because what consumes the budget is the content of each rule — its name, every condition, every action, and in particular every email address or keyword you have listed inside it.

A rule that says “move mail from newsletters@example.com to Newsletters” is tiny. A rule that says “move mail from any of these 180 addresses to Clients” is not, because all 180 addresses are stored in the rule.

The trap: disabled rules still count

Unchecking a rule in Manage Rules & Alerts does not free any quota. The rule is still stored in the mailbox and still counts against the budget. People routinely disable half their rules to make room, see no improvement, and conclude the quota is not the problem. Delete old rules rather than disabling them.

How to check your quota

If you have Exchange administrator access, this reads the current setting:

Get-Mailbox you@example.com | FL displayname,rulesquota

And this raises it, where the server allows:

Set-Mailbox you@example.com -RulesQuota:256kb

If you are on Exchange Online you are already at 256 KB, which is the ceiling. There is nothing further to raise, and the only way forward is a smaller rule set.

How to make the set smaller

Delete rules you no longer use — the only action that actually reclaims space.
Shorten rule names. This sounds trivial and is not: the name is stored with the rule, and a set of long descriptive names adds up.
Combine similar rules. Three rules that each move one sender to the same folder can become one rule with three senders, which is smaller than three separate rule structures.
Trim long address and keyword lists. These dominate the size of most oversized rule sets. Where a domain works instead of twenty individual addresses at that domain, use the domain.
If a rule files into a .pst, move the .pst somewhere with a short path. The full path is stored inside the rule, so C:\archive.pst costs less than a deeply nested folder under your user profile.

Cause 2: The Rule Is Client-Only

Some rules cannot run on the server at all, because they do things only the Outlook application can do. Outlook marks these (client-only) in the rules list, and they run only while Outlook is open on that machine.

A rule becomes client-only as soon as it uses any of these:

Play a sound, or display a Desktop Alert
Print a message
Run a script
Start an application
Move or copy into a local .pst file rather than a mailbox folder
Any rule with on this machine only ticked

If a client-only rule keeps deactivating, the fix is to remove whichever condition or action forces it client-side — most often by filing into a mailbox folder instead of a .pst, or by clearing on this machine only. We cover the distinction in detail in client-only vs server-side Outlook rules.

Cause 3: The Same Rule on Two Computers

If you use Outlook on more than one machine and you have client-only rules pointing at local files — a .pst on your desktop that does not exist on your laptop — the two copies of the rule set conflict. Each machine tries to reconcile a rule that references something the other cannot see, and rules get deactivated in the process.

This one is easy to recognise: the rules break when you switch machines, and re-enabling them on one computer breaks them on the other. The fix is to stop referencing local resources in rules you want to work everywhere.

Which One Is Yours?

Several rules deactivated at once, and it recurs after you re-enable them → quota. Go to Cause 1.
One specific rule will not stay on, and it plays a sound, runs a script, or files into a .pst → client-only. Go to Cause 2.
Rules work on one computer and break on the other → conflict. Go to Cause 3.
Rules stay enabled but do not fire → this is a different problem: the rule is enabled but never matching, or it is client-only and Outlook is closed. That is not covered here; see Outlook rules alternatives for the wider picture.

The Part Nobody Mentions

Every fix above makes your rule set smaller. None of them make it stop growing. The quota is fixed, your mail is not, and a rule set that files mail accurately has to expand every time a new client, project or sender appears — which is exactly why people end up with 180 addresses inside one rule in the first place.

That is the structural problem with rules as a filing system: they only handle mail whose pattern you predicted in advance, and the cost of predicting more of it is paid in quota you cannot buy more of.

Folder Suggest takes the other approach — it reads each email and suggests the right folder from your existing structure, so there is no rule set to maintain and nothing to hit a quota. The AI runs on your own device and no email content leaves your machine.

Add to Outlook

Frequently Asked Questions

Why do my Outlook rules turn off every day?
A rule that disables itself repeatedly, rather than once, almost always points at the rules quota. Outlook tries to re-upload your rule set to Exchange, the set does not fit, and the server deactivates whatever pushed it over. It looks daily because it happens each time Outlook syncs the rule set. Reducing the total size of your rules is the fix; re-enabling the rule without reducing anything just repeats the cycle.

Do disabled rules still count toward the Outlook rules limit?
Yes. This is the single most common reason people cannot work out why they are over the limit. A rule that is unchecked in Manage Rules & Alerts is still stored in the mailbox and still consumes quota. Deleting old rules frees space; disabling them does not.

How do I check my current Outlook rules quota?
An Exchange administrator can run Get-Mailbox you@example.com | FL displayname,rulesquota in Exchange Online PowerShell. Without admin access there is no supported way to read the number from the Outlook client, which is why the symptom usually gets diagnosed from the error message instead.

Can my administrator increase the Outlook rules limit?
Up to a point. On Exchange Server 2007 and later the default is 64 KB and an administrator can raise it with Set-Mailbox -RulesQuota, but 256 KB is the ceiling and cannot be exceeded. On Exchange Online the quota is already 256 KB, so there is no more headroom available and the only remaining option is to make the rule set smaller.