Forum Discussion
Error applying retention policy in security & compliance - "Recipient not Found"
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?