Forum Discussion
Error applying retention policy in security & compliance - "Recipient not Found"
So I opened a case today, and though the support rep that I spoke to hadn't seen this specific issue before first-hand, some of his colleagues had, and they speculated that since we're mid migration to O365 (we're running a hybrid setup at the moment with Exchange 2010 on prem) it could be that the policy isn't able to apply itself fully, to as yet un-provisioned/un-migrated mailboxes. Hence the brilliantly descriptive error message...
Don't know if this stacks up with your situations too? or if you're all fully migrated/consuming O365... but the chap has provided me with his details, and advised that we complete our migrations first, and see if the error resolves itself once all mailboxes are provisioned/migrated, and if not, to reach out to him for further investigation.
We're 'fully migrated', but of course once you go hybrid, there's no going back, so we still have an Exchange 2013 server in the mix. All of our mailboxes were migrated a year or more ago, with the exception of 3 mailboxes associated with our on-prem exchange and sharepoint administrator accounts. I wouldn't expect those to cause a problem for the retention policies, but I suppose it's possible.
Of course, if this issue is as simple as a few specific mailboxes that the policy failed to apply to, I would expect that support could have identified and explained that, but. . .
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.
