Decide whether an FSRM classification rule may replace existing values

Source facts

An FSRM classification rule assigns one property. By default, Microsoft’s procedure leaves files that already have a property value unchanged. Enabling re-evaluation introduces a choice between replacing an existing value and aggregating the new result with it. Microsoft’s Boolean example shows that aggregation can retain Yes when a rule proposes No, while overwrite changes it to No. Microsoft documentation.

Applicability

Identify the property, existing values, rule scope, classifier, and downstream consumers. Ask the data owner whether an earlier classification is authoritative, provisional, or intended to be combined with later evaluation.

DSE recommendation

Prepare example files representing an unset property, a matching existing value, and a conflicting value. Agree on the desired result for each before selecting overwrite or aggregation. Record the rule’s scope and enabled state and have the owner review any planned replacement of existing labels.

Verification

Run the approved examples through classification and compare the actual property values with the decision table. Re-run the process to inspect re-evaluation behavior. Preserve before-and-after values and resolve any unexpected aggregation result before expanding the rule to additional folders or using its output for another action.

Official references

Microsoft Learn: Create an Automatic Classification Rule. Source reviewed September 8, 2026.