Resolve folder and file-ID scope gaps before migrating Cloud Apps file policies

Source facts

Microsoft’s migration mapping does not preserve every file-policy condition. A parent-folder condition maps only partially to SharePoint site scope, with no folder-level equivalent. File ID has no supported condition mapping. The automated migration tool classifies policies by readiness and presents payload warnings for fields needing manual attention. These are scope differences to resolve, not merely renamed settings. Microsoft Learn.

Applicability

Use this review for existing Cloud Apps file policies being translated into Purview rules. Inspect the original conditions themselves rather than relying on a policy name or migration count. Check the source’s current tool eligibility separately; this brief does not assume that every app or environment supports automated migration.

DSE recommendation

Escalate each unsupported or broadened location condition as a protection-design decision before accepting the migrated policy. Give the data owner a concrete comparison: the originally selected folder or file, the proposed target site or content condition, and the files that would newly enter or leave scope. Record an explicit alternative for a file-ID rule instead of silently dropping that condition.

Verification

Compare representative files inside the original folder, elsewhere in the same site, and outside the proposed site. Include a file formerly selected only by its identifier. Review the target rule and its observed matches against the approved boundary. Preserve unresolved differences as migration exceptions; a successfully created policy is not the acceptance result for this scope review.

Official references

Microsoft Learn: Migrate file policies to Microsoft Purview. Source reviewed September 9, 2026.