Home
%3CLINGO-SUB%20id%3D%22lingo-sub-609273%22%20slang%3D%22en-US%22%3EAnnouncing%20the%20Public%20Folder%20Consistency%20Agent%20for%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-609273%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20very%20glad%20to%20announce%20availability%20of%20the%20public%20folder%20consistency%20agent%20for%20public%20folders%20in%20Exchange%20Online.%20What%20is%20this%2C%20you%20ask%3F%20Read%20on!%20The%20agent%20currently%20works%20on%20two%20scenarios%3A%3C%2FP%3E%3CH2%20id%3D%22toc-hId-1759369785%22%20id%3D%22toc-hId-1760056864%22%3EScenario%201%3A%20Stale%20permissions%20on%20public%20folders%3C%2FH2%3EConsider%20a%20scenario%20where%20a%20user%20was%20given%20permissions%20on%20a%20public%20folder%2C%20but%20their%20mailbox%20was%20then%20removed.%20For%20example%3A%20User%20named%20%E2%80%9CFi%E2%80%9D%20is%20assigned%20Editor%20permission%20to%20a%20public%20folder%20called%20Sales%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent1.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent1%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent1%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent1_thumb.jpg%22%20class%3D%22%22%20width%3D%22542%22%20height%3D%22566%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%20The%20mailbox%20for%20%E2%80%9CFi%E2%80%9D%20is%20then%20removed%3B%20this%20could%20be%20either%20because%20the%20mailbox%20was%20removed%20or%20the%20user%20itself%20was%20deleted%20(which%20also%20removes%20the%20mailbox).%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent2.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent2%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent2%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent2_thumb.jpg%22%20class%3D%22%22%20width%3D%22774%22%20height%3D%22153%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%20After%20the%20mailbox%20is%20gone%2C%20the%20previous%20permission%20entry%20from%20the%20public%20folder%20is%20not%20cleaned%20up%20and%20remains%20there%20as%20stale%20entry%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent3.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent3%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent3%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent3_thumb.jpg%22%20class%3D%22%22%20width%3D%22542%22%20height%3D%22566%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%20Such%20stale%20permissions%20were%20a%20cause%20of%20concern%20and%20may%20result%20in%20issues%20like%3A%3CUL%3E%0A%20%20%3CLI%3EOther%20users%20might%20be%20unable%20to%20access%20public%20folders%2C%20even%20though%20they%20have%20the%20right%20permissions%3C%2FLI%3E%0A%20%20%3CLI%3EPermission%20conflicts%3C%2FLI%3E%0A%3C%2FUL%3EThe%20consistency%20agent%20finds%20and%20removes%20such%20stale%20permissions%20from%20public%20folders.%20After%20the%20agent%20removed%20stale%20permission%20on%20our%20sample%20folder%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent4.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent4%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent4%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent4_thumb.jpg%22%20class%3D%22%22%20width%3D%22548%22%20height%3D%22572%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%3CH2%20id%3D%22toc-hId--792787176%22%20id%3D%22toc-hId--792100097%22%3EScenario%202%3A%20Mail%20enabled%20public%20folder%20%E2%80%98content%20mailbox%E2%80%99%20cleanup%3C%2FH2%3EMail%20Enabled%20Public%20Folders%20(MEPF)%20have%20an%20important%20property%20related%20to%20%E2%80%98content%20mailbox%E2%80%99%2C%20which%20must%20be%20pointing%20to%20the%20correct%20public%20folder%20mailbox%20hosting%20the%20actual%20public%20folder%20content.%20The%20content%20mailbox%20property%20is%20crucial%20for%20delivering%20emails%20sent%20to%20the%20MEPF%20to%20a%20correct%20public%20folder.%20We%20have%20seen%20situations%20in%20which%20the%20content%20mailbox%20property%20on%20the%20MEPF%20do%20not%20point%20to%20the%20actual%20public%20folder%20mailbox%20hosting%20the%20public%20folder%20content.%20In%20such%20scenarios%2C%20email%20sent%20to%20MEPF%E2%80%99s%20would%20just%20remain%20in%20queue%20and%20would%20not%20be%20delivered%20correctly.%20The%20consistency%20agent%20verifies%20content%20mailbox%20property%20on%20MEPF%E2%80%99s%20and%20updates%20the%20value%20if%20it%20is%20not%20pointing%20to%20a%20correct%20mailbox.%20In%20the%20following%20example%2C%20public%20folder%20%E2%80%9CPF1%E2%80%9D%20content%20resides%20in%20a%20public%20folder%20mailbox%20M2%2C%20however%2C%20the%20content%20mailbox%20property%20of%20this%20MEPF%20object%20is%20pointing%20to%20a%20public%20folder%20mailbox%20M1%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent5.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent5%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent5%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent5_thumb.jpg%22%20class%3D%22%22%20width%3D%22607%22%20height%3D%22193%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%20After%20the%20MEPF%20object%20is%20updated%20by%20the%20agent%2C%20the%20ContentMailbox%20correctly%20points%20to%20the%20public%20folder%20mailbox%20M2%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent6.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20title%3D%22PFagent6%22%20style%3D%22border%3A%200px%20currentcolor%22%20alt%3D%22PFagent6%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F02%2FPFagent6_thumb.jpg%22%20class%3D%22%22%20width%3D%22604%22%20height%3D%22191%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E%20If%20there%20is%20email%20that%20was%20still%20%E2%80%98queued%20up%E2%80%99%20for%20a%20particular%20folder%2C%20it%20will%20get%20delivered%20after%20the%20correction%20is%20made.%20The%20PF%20consistency%20agent%20is%20already%20at%20work%20for%20your%20tenant%3B%20nothing%20you%20need%20to%20do!%20For%20mail%20enabled%20public%20folders%2C%20the%20agent%20runs%20every%20day%20to%20keep%20the%20MEPF%20updated%20and%20avoid%20any%20mail%20delivery%20issues.%20And%20stale%20permissions%20entries%20are%20checked%20for%20and%20removed%20once%20every%207%20days.%20We%E2%80%99ve%20love%20to%20hear%20your%20feedback!%20Please%20feel%20free%20to%20ask%20any%20questions%20via%20the%20comments%20section%20below.%20%3CSPAN%20class%3D%22author%22%3EPublic%20Folder%20team%3C%2FSPAN%3E%3C%2FLINGO-BODY%3E

We are very glad to announce availability of the public folder consistency agent for public folders in Exchange Online. What is this, you ask? Read on! The agent currently works on two scenarios:

Scenario 1: Stale permissions on public folders

Consider a scenario where a user was given permissions on a public folder, but their mailbox was then removed. For example: User named “Fi” is assigned Editor permission to a public folder called Sales: PFagent1 The mailbox for “Fi” is then removed; this could be either because the mailbox was removed or the user itself was deleted (which also removes the mailbox). PFagent2 After the mailbox is gone, the previous permission entry from the public folder is not cleaned up and remains there as stale entry: PFagent3 Such stale permissions were a cause of concern and may result in issues like:
  • Other users might be unable to access public folders, even though they have the right permissions
  • Permission conflicts
The consistency agent finds and removes such stale permissions from public folders. After the agent removed stale permission on our sample folder: PFagent4

Scenario 2: Mail enabled public folder ‘content mailbox’ cleanup

Mail Enabled Public Folders (MEPF) have an important property related to ‘content mailbox’, which must be pointing to the correct public folder mailbox hosting the actual public folder content. The content mailbox property is crucial for delivering emails sent to the MEPF to a correct public folder. We have seen situations in which the content mailbox property on the MEPF do not point to the actual public folder mailbox hosting the public folder content. In such scenarios, email sent to MEPF’s would just remain in queue and would not be delivered correctly. The consistency agent verifies content mailbox property on MEPF’s and updates the value if it is not pointing to a correct mailbox. In the following example, public folder “PF1” content resides in a public folder mailbox M2, however, the content mailbox property of this MEPF object is pointing to a public folder mailbox M1: PFagent5 After the MEPF object is updated by the agent, the ContentMailbox correctly points to the public folder mailbox M2: PFagent6 If there is email that was still ‘queued up’ for a particular folder, it will get delivered after the correction is made. The PF consistency agent is already at work for your tenant; nothing you need to do! For mail enabled public folders, the agent runs every day to keep the MEPF updated and avoid any mail delivery issues. And stale permissions entries are checked for and removed once every 7 days. We’ve love to hear your feedback! Please feel free to ask any questions via the comments section below. Public Folder team
4 Comments
Not applicable
Great.

Now we need this for mailboxes.

Removed mailboxes leave a raw SID behind for FullAccess and SendAS permissions.

Same goes for resource mailbox booking permissions.

Probably some more examples could be found.

Not applicable
I agree!
Not applicable
Can we get this for exchange 2016 on premis too?
New Contributor

If you need a on prem version. Give this a bash. 

 

https://github.com/JBines/Get-RecipientPermissions.ps1