Graph and PowerShell Blog

For some reason after migrating public folders to Office365 the client permissions would not take affect for users despite it showing as set in the admin console. As there were only a few public folders, used mainly for shared address books, I didn't want to spend too much time troubleshooting the issue.

I decided to export the information in the public folders to my own shared mailbox, then delete the public folders and public folder hierarchy and then rectreate them in Office 365 alone. However, after doing this the primary PF mailbox was LockedForMigration.

The resolution was to run the following:

EXO
Get-Mailbox -PublicFolder $(Get-OrganizationConfig).RootPublicFoilderMailbox.HierarchyMailboxGuid.ToString() | Remove-Mailbox -PublicFolder -Confirm:$False -Force:$True

Set-OrganizationConfig -PublicFoldersEnabled:local
Set-OrganizationConfig -RemotePublicFolderMailboxes $null

After this we could create a Public Folder mailbox under the O365 admin console. Newly created public folders had no issues with client permissions and I was able to import the old data from my own mailbox.

Graph and PowerShell Blog	Articles 2024 Advanced Postfix configuration Installing Exchange 2019 in Azure Landing Zone Upgrading PHP on Windows Adding a Postfix server for relay to O365 O365 Integrated Apps troubleshooting Domino and O365 Co-existence Delegate Control in AD App mail relay via HVE Setting up Mail Relay with HVE Getting BIMI certified Orbea Occam SL H30 Installing FreeSat and Saorview Changing broadband provider Replacing a DIN timer on fuseboard Outlook Desktop Notifications stop working Outlook folders keep moving sort order Teams report uploading to SharePoint with Runbooks Teams PowerShell module can't run CS cmd as App 2023 Cannot map new Shared Mailboxes in O365 Renewing an Exchange 2016 certificate Connect to Compliance PowerShell behind a Proxy Sensitivity Label not shown in Outlook Client Room Finder Error in Outlook Teams not showing Rooms Teams unable to open file Unable to review quarantined mails for shared mailbox Set Locale for various Apps Delegate Sent Items placed into external Tenant Overview of Microsoft Support cases When centralized mail sends via O365 Cleaning up your Windows DNS server Set OneDrive for Business Locale O365 Migration Tips Reporting on successful Azure logons IIS Mapi Queue full with NetScaler Secure Office365 reports with a certificate Using Graph to send emails with inline images Visualizing Graph data with Google Charts Keeping a log of NetScaler AlwaysON connections \| About \| Links

Recreate Public Folders in Exchange Online 11-Oct-23 For some reason after migrating public folders to Office365 the client permissions would not take affect for users despite it showing as set in the admin console. As there were only a few public folders, used mainly for shared address books, I didn't want to spend too much time troubleshooting the issue. I decided to export the information in the public folders to my own shared mailbox, then delete the public folders and public folder hierarchy and then rectreate them in Office 365 alone. However, after doing this the primary PF mailbox was LockedForMigration. The resolution was to run the following: EXO Get-Mailbox -PublicFolder $(Get-OrganizationConfig).RootPublicFoilderMailbox.HierarchyMailboxGuid.ToString() \| Remove-Mailbox -PublicFolder -Confirm:$False -Force:$True Set-OrganizationConfig -PublicFoldersEnabled:local Set-OrganizationConfig -RemotePublicFolderMailboxes $null After this we could create a Public Folder mailbox under the O365 admin console. Newly created public folders had no issues with client permissions and I was able to import the old data from my own mailbox.