Priority value out of range: Exchange Online Transport Rule Deployment

Answer to the three questions

1. Ordering when priorities are equal: Exchange Online evaluates transport rules with the same Priority value in the order of their creation timestamp – the oldest rule (earliest Created time) is processed first.
2. Exact upper bound before the warning: The Priority parameter accepts a 32‑bit signed integer. Values in the range 0 to 2,147,483,647 are accepted without warning. Supplying 2,147,483,648 (Int32.MaxValue + 1) or any larger positive number triggers the “Priority value out of range” warning (negative values also trigger the warning). The rule is still created/updated with the supplied value, but the warning indicates the value is outside the supported range.
3. Preserving priority after disable/enable: Disabling a rule with Disable‑TransportRule resets its Priority to 0. Re‑enabling with Enable‑TransportRule does not restore the previous value. To preserve the priority, capture it before disabling and re‑apply it after enabling.

Likely explanation vs. confirmed facts

Likely explanation (based on observed service behavior): The engine stores Priority as a signed 32‑bit integer and uses the Created timestamp as a tie‑breaker when sorting rules for evaluation. Future service updates could adjust the warning threshold or change the tie‑breaker logic.

Confirmed facts (verifiable today):

• Get‑TransportRule | Select Name, Priority, Created shows the current priority and creation time.
• Running Disable‑TransportRule -Identity "RuleName" followed by Get‑TransportRule -Identity "RuleName" yields Priority : 0.
• Setting a priority of 2,147,483,648 produces a warning in the PowerShell console while the rule still appears with that priority in Get‑TransportRule.

Steps to preserve a rule’s priority

1. Capture the current priority:

$rule = Get-TransportRule -Identity "MyRule"
$savedPriority = $rule.Priority

2. Disable the rule (if needed):

Disable-TransportRule -Identity "MyRule"

3. Re‑enable the rule:

Enable-TransportRule -Identity "MyRule"

4. Restore the original priority:

Set-TransportRule -Identity "MyRule" -Priority $savedPriority

5. Verify:

Get-TransportRule -Identity "MyRule" | Select Name, Priority, Created

If you continue to see the “Priority value out of range” warning, verify that the value you are assigning is ≤ 2,147,483,647 and ≥ 0. Adjust the value accordingly and repeat the steps above.