Treat an FSRM expiration task as a controlled file move

Source facts

Microsoft describes a file-expiration task as moving files that meet selected criteria into an expiration directory, where an administrator can later back up and delete them. A run creates a destination directory grouped by the server that performed the task. The new directory also reflects the task name and run time, while moved files retain their original directory structure. Microsoft documentation.

Applicability

Use this review when designing an FSRM expiration rule. Identify the source paths, selection criteria, data owner, and expiration location. Keep the move decision distinct from a later decision to delete retained files.

DSE recommendation

Have the data owner review examples that should match and examples that must remain in place. Choose a limited pilot scope and confirm the destination can be administered by the intended personnel. Record how users will locate moved material and how an incorrect match will be returned through the approved process. Obtain separate retention and deletion decisions before scheduling subsequent handling.

Verification

After the approved test run, reconcile the moved-file list with the selection examples. Check the destination grouping and retained directory structure, and confirm representative files are readable. Investigate both unexpected moves and expected files left behind. Preserve the rule, run time, and owner acceptance before enabling a recurring expiration schedule.

Official references

Microsoft Learn: Create a File Expiration Task. Source reviewed September 8, 2026.