Forum Discussion
Error applying retention policy in security & compliance - "Recipient not Found"
I'm trying to create a retention policy in the Security & Compliance center, but running into an error. The policy seems to create successfully, but after a while if I open the details it will show ...
I have this same issue and we are not hybrid - 100% cloud as we migrated over from Google. My case is open and the support tech advised I toggle the location for Exchange on/off. The error disappeared - for a day. Now it's back. We really need to know what it means - according to the mouse over - it could mean that the retention policy is skipping over the location (all of exchange?) or is it just the one recipient not found? Why can't we drill for details to see which mailbox? My support person is also investigating public folders - which I find laughable given that we have never used any (once again, coming from Google) and don't have a single one configured. Anyone have any progress on this?
I have this issue too. And to eliminate the hybrid I tried to create the same policy in my test tenant that has no dirsync or on-prem connection, and I get the same error.
Creating the policy I also choose "All Locations" but it seems to change it automatically.
So lets hear from someone that fixed this :)
Using the Powershell I described earlier to ID the "missing recipient" and correcting it (turning off Public Folders) worked for me. I can confirm all of the users in our tenant are covered by the retention policy.
I can also see the status as On(success) but how did you confirm that all users have got this policy ? When i run "Get-Mailbox eu1|select retentionholdenabled" the result shows as false.
Is there any other place we can check to validate that its worked ?- If you set a policy for all users it will not appear on the actual mailbox, but in the organisation settings instead
- You will get this error if you have hybrid public folders (public folders on-premises) or if you have never created public folders either - like the example about migrating from Google by @Angel above.
If you have on-premises public folders, then either leave the retention policy in place (and showing an error) and that way when you do migrate your public folders they are covered from day one. Or remove public folders as a retention source. See https://c7solutions.com/2018/02/office-365-retention-policies-and-hybrid-public-folders for more.
