Home

Error applying retention policy in security & compliance - "Recipient not Found"

%3CLINGO-SUB%20id%3D%22lingo-sub-123264%22%20slang%3D%22en-US%22%3EError%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123264%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20create%20a%20retention%20policy%20in%20the%20Security%20%26amp%3B%20Compliance%20center%2C%20but%20running%20into%20an%20error.%26nbsp%3B%20The%20policy%20seems%20to%20create%20successfully%2C%20but%20after%20a%20while%20if%20I%20open%20the%20details%20it%20will%20show%20a%20warning%20sign%20next%20to%20'1%20distribution%20results%20found'.%26nbsp%3B%20Expanding%20that%20area%2C%20it%20looks%20like%20there%20was%20a%20problem%20applying%20the%20policy%20to%20exchange%2C%20with%20the%20message%20of%20%22recipient%20not%20found%22.%26nbsp%3B%20As%20you%20can%20see%20below%2C%20it's%20not%20terribly%20informative%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20583px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23345i9C11B1D1F93C39E6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20else%20seen%20this%20error%3F%26nbsp%3B%20Do%20you%20know%20what%20causes%20it%2C%20or%20how%20I%20can%20get%20more%20info%20to%20troubleshoot%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CRANT%3EI%20tried%20contacting%20support%20about%20this%20using%20the%20handy%20%22notify%20support%22%20link%20next%20to%20the%20error%2C%20but%20the%20rep%20didn't%20seem%20to%20understand%20what%20my%20goal%20was%2C%20much%20less%20understand%20this%20problem.%26nbsp%3B%20He%20said%20that%20the%20error%20is%20because%20exchange%20mailboxes%20have%20a%20max%20size%20of%20100gb%20and%20if%20I%20set%20a%20retention%20policy%20to%20keep%20everything%20forever%2C%20mailboxes%20will%20be%20over%20100gb%20and%20that%20causes%20this.%26nbsp%3B%20Then%20he%20tried%20to%20steer%20me%20towards%20creating%20a%20retention%20policy%20in%20the%20exchange%20admin%20center%20that%20moves%20content%20over%201%20year%20old%20to%20archive.%26nbsp%3B%20Ugh...%20not%20the%20point%20at%20all.%26nbsp%3B%20%3C%2FRANT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-123264%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECompliance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160684%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160684%22%20slang%3D%22en-US%22%3EYou%20will%20get%20this%20error%20if%20you%20have%20hybrid%20public%20folders%20(public%20folders%20on-premises)%20or%20if%20you%20have%20never%20created%20public%20folders%20either%20-%20like%20the%20example%20about%20migrating%20from%20Google%20by%20%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F235845%22%3E%40angel%3C%2Fa%3E%20above.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20have%20on-premises%20public%20folders%2C%20then%20either%20leave%20the%20retention%20policy%20in%20place%20(and%20showing%20an%20error)%20and%20that%20way%20when%20you%20do%20migrate%20your%20public%20folders%20they%20are%20covered%20from%20day%20one.%20Or%20remove%20public%20folders%20as%20a%20retention%20source.%20See%20%3CA%20href%3D%22https%3A%2F%2Fc7solutions.com%2F2018%2F02%2Foffice-365-retention-policies-and-hybrid-public-folders%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fc7solutions.com%2F2018%2F02%2Foffice-365-retention-policies-and-hybrid-public-folders%3C%2FA%3E%20for%20more.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154625%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154625%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20the%20Powershell%20I%20described%20earlier%20to%20ID%20the%20%22missing%20recipient%22%20and%20correcting%20it%20(turning%20off%20Public%20Folders)%20worked%20for%20me.%20%26nbsp%3BI%20can%20confirm%20all%20of%20the%20users%20in%20our%20tenant%20are%20covered%20by%20the%20retention%20policy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151467%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151467%22%20slang%3D%22en-US%22%3E%3CP%3EObviously%20this%20ppl%20is%20choosing%20to%20al%20folders%20but%20they%20dont%20have%20public%20folders%20so%20this%20cause%20a%20loop%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-144256%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144256%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20definitely%20looks%20like%20improper%20error%20handling%20in%20the%20code...%20Open%20a%20support%20case%20to%20report%20it%20IMO.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-144217%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144217%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20error%2C%20running%20the%20below%20command%20shed%20a%20little%20more%20light%20on%20the%20issue%3A%3C%2FP%3E%0A%3CPRE%3EGet-RetentionCompliancePolicy%20-DistributionDetail%20%7C%20fl%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20relevant%20part%20of%20the%20results%3A%3C%2FP%3E%0A%3CP%3EDistributionStatus%20%3A%20Error%3CBR%20%2F%3EDistributionResults%20%3A%20%7B%5BExchange%5DAllPublicFolderUnderRoot%3ARecipient%20not%20found%3A%20%7D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20disabled%20Public%20Folders%20in%20the%20retention%20policy%2C%20and%20now%20it%20has%20%22On%20(Success)%22%20as%20its%20status.%26nbsp%3B%20I%20wonder%20if%20the%20error%20occurs%20because%20we%20don't%20have%20any%20public%20folders%2C%20so%20the%20null%20trips%20up%20some%20code%20somewhere.%26nbsp%3B%20I%20just%20implemented%20the%20change%2C%20so%20I%20can't%20verify%20that%20the%20mailboxes%20were%20all%20put%20on%20hold.%26nbsp%3B%20At%20least%20the%20retention%20policy%20no%20longer%20has%20an%20error%2C%20so%20that's%20promising.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-141532%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-141532%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20this%20issue%20too.%20And%20to%20eliminate%20the%20hybrid%20I%20tried%20to%20create%20the%20same%20policy%20in%20my%20test%20tenant%20that%20has%20no%20dirsync%20or%20on-prem%20connection%2C%20and%20I%20get%20the%20same%20error.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECreating%20the%20policy%20I%20also%20choose%20%22All%20Locations%22%20but%20it%20seems%20to%20change%20it%20automatically.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20lets%20hear%20from%20someone%20that%20fixed%20this%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137741%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137741%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20this%20same%20issue%20and%20we%20are%20not%20hybrid%20-%20100%25%20cloud%20as%20we%20migrated%20over%20from%20Google.%20My%20case%20is%20open%20and%20the%20support%20tech%20advised%20I%20toggle%20the%20location%20for%20Exchange%20on%2Foff.%20The%20error%20disappeared%20-%20for%20a%20day.%20Now%20it's%20back.%20We%20really%20need%20to%20know%20what%20it%20means%20-%20according%20to%20the%20mouse%20over%20-%20it%20could%20mean%20that%20the%20retention%20policy%20is%20skipping%20over%20the%20location%20(all%20of%20exchange%3F)%20or%20is%20it%20just%20the%20one%20recipient%20not%20found%3F%20Why%20can't%20we%20drill%20for%20details%20to%20see%20which%20mailbox%3F%20My%20support%20person%20is%20also%20investigating%20public%20folders%20-%20which%20I%20find%20laughable%20given%20that%20we%20have%20never%20used%20any%20(once%20again%2C%20coming%20from%20Google)%20and%20don't%20have%20a%20single%20one%20configured.%20Anyone%20have%20any%20progress%20on%20this%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136557%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136557%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20'fully%20migrated'%2C%20but%20of%20course%20once%20you%20go%20hybrid%2C%20there's%20no%20going%20back%2C%20so%20we%20still%20have%20an%20Exchange%202013%20server%20in%20the%20mix.%26nbsp%3B%20All%20of%20our%20mailboxes%20were%20migrated%20a%20year%20or%20more%20ago%2C%20with%20the%20exception%20of%203%20mailboxes%20associated%20with%20our%20on-prem%20exchange%20and%20sharepoint%20administrator%20accounts.%26nbsp%3B%20I%20wouldn't%20expect%20those%20to%20cause%20a%20problem%20for%20the%20retention%20policies%2C%20but%20I%20suppose%20it's%20possible.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOf%20course%2C%20if%20this%20issue%20is%20as%20simple%20as%20a%20few%20specific%20mailboxes%20that%20the%20policy%20failed%20to%20apply%20to%2C%20I%20would%20expect%20that%20support%20could%20have%20identified%20and%20explained%20that%2C%20but.%20.%20.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134976%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134976%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20I%20opened%20a%20case%20today%2C%20and%20though%20the%20support%20rep%20that%20I%20spoke%20to%20hadn't%20seen%20this%20specific%20issue%20before%20first-hand%2C%20some%20of%20his%20colleagues%20had%2C%20and%20they%20speculated%20that%20since%20we're%20mid%20migration%20to%20O365%20(we're%20running%20a%20hybrid%20setup%26nbsp%3Bat%20the%20moment%26nbsp%3Bwith%20Exchange%202010%20on%20prem)%20it%20could%20be%20that%20the%20policy%20isn't%20able%20to%20apply%20itself%20fully%2C%20to%20as%20yet%20un-provisioned%2Fun-migrated%20mailboxes.%20Hence%20the%20brilliantly%20descriptive%20error%20message...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDon't%20know%20if%20this%20stacks%20up%20with%20your%20situations%20too%3F%20or%20if%20you're%20all%20fully%20migrated%2Fconsuming%20O365...%20but%20the%20chap%20has%20provided%20me%20with%20his%20details%2C%20and%20advised%20that%20we%20complete%20our%20migrations%20first%2C%20and%20see%20if%20the%20error%20resolves%20itself%20once%20all%20mailboxes%20are%20provisioned%2Fmigrated%2C%20and%20if%20not%2C%20to%20reach%20out%20to%20him%20for%20further%20investigation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134864%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134864%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%2C%20let%20us%20know%20how%20you%20go%20with%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134122%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134122%22%20slang%3D%22en-US%22%3E%3CP%3EMe%20too%20-%20exactly%20the%20same%20problem...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20%22Notify%20Support%22%20link%20is%20pointless%20-%20it%20looks%20like%20a%20generic%20suggestion%20form.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20plan%20to%20open%20a%20Support%20Case%20today%2C%20so%20if%20I%20get%20anything%20%3CEM%3E%3CSTRONG%3Euseful%20%3C%2FSTRONG%3E%3C%2FEM%3Eby%20way%20of%20an%20explanation%2C%20I'll%20share%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124980%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124980%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124558%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124558%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20creating%20the%20policy%2C%20I%20chose%20the%20option%20to%20apply%20to%20it%20to%20%22%3CSTRONG%3EAll%20Locations.%26nbsp%3B%20Includes%20content%20in%20Exchange%20email%20and%20public%20folders%2C%20Office%20365%20groups%2C%20and%20OneDrive%20and%20SharePoint%20documents%3C%2FSTRONG%3E.%22%20With%20that%20selected%2C%20there%20is%20no%20option%20to%20filter%20by%20mailbox.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124506%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124506%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20apply%20the%20policy%20to%20all%20Exchange%20mailboxes%20or%20just%20selected%20mailboxes%3F%20If%20selected%2C%20do%20all%20the%20selected%20mailboxes%20still%20exist%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123297%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20applying%20retention%20policy%20in%20security%20%26amp%3B%20compliance%20-%20%22Recipient%20not%20Found%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123297%22%20slang%3D%22en-US%22%3E%3CP%3EHavent%20seen%20the%20error%2C%20but%20it%20certainly%20looks%20like%20something%20on%20the%20backend%2C%20problem%20with%20synchronization%20maybe.%20Ask%20the%20support%20guy%20to%20escalate...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Steve Whitcher
Regular Contributor

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 a warning sign next to '1 distribution results found'.  Expanding that area, it looks like there was a problem applying the policy to exchange, with the message of "recipient not found".  As you can see below, it's not terribly informative:

image.png

 

Has anyone else seen this error?  Do you know what causes it, or how I can get more info to troubleshoot?  

 

<rant>I tried contacting support about this using the handy "notify support" link next to the error, but the rep didn't seem to understand what my goal was, much less understand this problem.  He said that the error is because exchange mailboxes have a max size of 100gb and if I set a retention policy to keep everything forever, mailboxes will be over 100gb and that causes this.  Then he tried to steer me towards creating a retention policy in the exchange admin center that moves content over 1 year old to archive.  Ugh... not the point at all.  </rant>

15 Replies

Havent seen the error, but it certainly looks like something on the backend, problem with synchronization maybe. Ask the support guy to escalate...

Did you apply the policy to all Exchange mailboxes or just selected mailboxes? If selected, do all the selected mailboxes still exist?

When creating the policy, I chose the option to apply to it to "All Locations.  Includes content in Exchange email and public folders, Office 365 groups, and OneDrive and SharePoint documents." With that selected, there is no option to filter by mailbox. 

 

 

Me too - exactly the same problem...

 

The "Notify Support" link is pointless - it looks like a generic suggestion form.

 

I plan to open a Support Case today, so if I get anything useful by way of an explanation, I'll share it.

Same here, let us know how you go with support.

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 :)

I have the same error, running the below command shed a little more light on the issue:

Get-RetentionCompliancePolicy -DistributionDetail | fl

 

The relevant part of the results:

DistributionStatus : Error
DistributionResults : {[Exchange]AllPublicFolderUnderRoot:Recipient not found: }

 

I disabled Public Folders in the retention policy, and now it has "On (Success)" as its status.  I wonder if the error occurs because we don't have any public folders, so the null trips up some code somewhere.  I just implemented the change, so I can't verify that the mailboxes were all put on hold.  At least the retention policy no longer has an error, so that's promising.

 

That definitely looks like improper error handling in the code... Open a support case to report it IMO.

Obviously this ppl is choosing to al folders but they dont have public folders so this cause a loop

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.

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.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies