Fix Exchange Online Cannot Rename or Delete Public Folders
Question details
A user with Owner or Publishing Editor roles is unable to rename or delete Exchange Online public folders despite being able to create and modify items within them.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Managing an Exchange Online cloud-only environment where specific owners need to rename or delete existing public folders.
- Observed behavior
- The user successfully creates and modifies items, but attempting to rename or delete the folder itself fails. The issue persists even after waiting for propagation delays and recreating the user profile.
Ensure you have Exchange Administrator credentials and access to the Exchange Online PowerShell module to verify and modify client permissions.
Verify and Reassign Custom Permissions via Exchange Online PowerShell
Use PowerShell to review exact folder permissions and assign explicit custom permissions that guarantee folder deletion and renaming rights.
While default roles like Publishing Editor allow extensive item management, they may not explicitly grant top-level folder management actions. Removing default roles and reassigning targeted custom permissions can resolve these specific access bottlenecks.
Open PowerShell as an administrator and run 'Connect-ExchangeOnline' to authenticate with your tenant.
Run the command 'Get-PublicFolderClientPermission -Identity "\YourFolder"' to check the specific rights assigned to the affected user.
Execute 'Remove-PublicFolderClientPermission -Identity "\YourFolder" -User "user@domain.com"' to strip the non-functional Owner or Publishing Editor role.
Run 'Add-PublicFolderClientPermission -Identity "\YourFolder" -User "user@domain.com" -AccessRights FolderVisible, EditAllItems, DeleteAllItems, CreateItems, FolderContact, Owner' to explicitly force full rights.
Check Folder Creator and EAC Custom Permissions
Identify the original folder creator and adjust settings via the Exchange Admin Center (EAC) for administrators uncomfortable with PowerShell.
Need a Hassle-Free Office Alternative? Try WPS Office
While managing complex Exchange environments can require extensive troubleshooting, your document productivity shouldn't. WPS Office provides a free, lightweight, and fully compatible alternative to Microsoft Office for your daily tasks.
- 1. Download the Installer: Visit the official WPS website and download the free installation package for your operating system.
- 2. Quick Installation: Run the installer and follow the lightweight setup wizard to get started in minutes.
- 3. Edit Your Office Files: Open your existing Microsoft Office documents, spreadsheets, and presentations directly without any format conversion.
Frequently Asked Questions
Why can a Publishing Editor delete items but not the folder?
The Publishing Editor role is designed to manage the content inside the folder. It grants permissions to read, create, modify, and delete items and subfolders, but it does not inherently provide the administrative right to delete or rename the parent public folder itself.
How long does it take for public folder permission changes to apply?
In Exchange Online, permission changes are subject to backend replication cycles. It typically takes anywhere from 15 minutes to a few hours for new public folder permissions to fully propagate across the cloud environment.
Can multiple users be Owners of an Exchange public folder?
Yes, multiple users can be assigned the Owner role for a single public folder. However, administrative actions like renaming might fail if there are conflicting custom permissions, caching issues on the client side, or if the user was not the original creator of the folder.
Is there a script to diagnose public folder permission errors?
Microsoft provides standard public folder permission scripts via PowerShell. If a script executes without producing an error but the user still lacks access, it often indicates a mismatch between the assigned role (like Publishing Editor) and the specific administrative action (renaming) being attempted.
