Choose notification or enforcement when creating an FSRM file screen

Source facts

Microsoft distinguishes active file screening, which prevents saving files in blocked groups and can notify administrators, from passive screening, which sends configured notifications without blocking the save. A file screen applies to its selected folder and all subfolders. A template can retain a relationship with derived screens so later template changes can be applied to them. Microsoft documentation.

Applicability

Use this review when creating a screen for a defined file-service policy. Identify the folder tree, file groups, notification recipients, and data owner. Choose the behavior deliberately before configuring the screen.

DSE recommendation

Prepare examples of files that should match and files that should remain unaffected. Have the owner decide whether the first deployment should observe activity or prevent it. Review inherited template relationships alongside the folder scope. Tell support staff what users should experience and who will review the notifications, and preserve the original configuration before enabling enforcement.

Verification

Test matching and nonmatching files in the selected folder and a representative subfolder. Record whether saving was allowed and whether the expected notification arrived. Inspect a location outside the scope to confirm the intended boundary. Reconcile incorrect matches or missing notifications before broadening the screen or switching from passive observation to active blocking.

Official references

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