Why does an auto-apply retention policy have to be pushed through powershell weekly?

Occasional Contributor

Our auto-apply retention policy only takes affect when our IT admin pushes it through PowerShell. Once the admin pushes, the policy takes affect the following week. But then it stops applying after that. New files are added, weeks go by, and the policy does not take affect unless we push the policy through PowerShell again. Why is this necessary?

 

Context

In Purview, we are using the auto-apply policy to apply a retention label to all files of content type 0x0101* (query = ContentTypeId:0x0101*). (We found this works for all files, whereas, applying something like "ContentType:Document" doesn't work at all.)

 

Any insight or suggestions would be helpful. Thank you.

0 Replies