Why does an auto-apply retention policy have to be pushed through powershell weekly?
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.
Accessing Content explorer data via SPN
Hi all, I am trying to get all the data from Content explorer for SITs matched files using https://learn.microsoft.com/en-us/powershell/module/exchange/export-contentexplorerdata?view=exchange-ps. I can run the command(Export-ContentExplorerData) when using User-Principle login but having issues while running it on SPN. For SPN Permissions, we followed the steps here https://learn.microsoft.com/en-us/powershell/exchange/app-only-auth-powershell-v2?view=exchange-ps assigned all the permissions on the page but still having issues when running the script. One of the permission for SPN that seems mandatory is Content Explorer Content viewer. Now in purview portal, we are not able to assign this permissions to SPN as it throws an errror "Adding SPN to purview role groups is not supported" Can we run this command(Export-ContentExplorerData) based on SPN(using application permission)? if yes what are the permission we need to assign to that SPN. Thanks in advance