Missing Owner Permission entry when Creating a Public Folder

A Ska 241 Reputation points
2023-01-17T16:06:17.54+00:00

vDear

For many months (particularly since CU22/23 of Exchange 2016) I have noticed that Users can correctly create Public Folders in Outlook BUT the "Owner" permission is no longer added For the creator user of the folder. This makes it impossible for the creator of the Public Folder to rename or move it.

What could this be due to? Is it a By Design thing?

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,173 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,469 questions
Microsoft Exchange
Microsoft Exchange
Microsoft messaging and collaboration software.
446 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,981 questions
{count} votes

2 answers

Sort by: Most helpful
  1. A Ska 241 Reputation points
    2023-01-23T07:49:49.1766667+00:00

    Dear

    Do you confirm that on your side, this permission is automatically added in ALL the subfolders?

    On my side no Owner permission is created neither adding the user on the parent folder he creates, nor on the subfolders.

    Thank you


  2. A Ska 241 Reputation points
    2023-03-28T09:01:21.38+00:00

    Dears,

    Just a follow up about the argument.

    I added in the msExchPublicFolderMailbox attribute the Primary Public Fodler Mailbox (CN=Mailbox1....) and by doing it, the user is now added as owner to the just created Public folder; it seems that if this attribute isn't populated, the Owner permission is not added.

    What do you think about this? @Kael Yao-MSFT can you please try and reproduce this behaviour in your test envirnonment?Thank you!

    0 comments No comments