How do I migrate mail-enabled Public Folders in hybrid mode?
In the case of a hybrid deployment, the 'mail-enabled' attribute and associated entries for Public Folders may be automatically populated in the Destination (due to DirSync/AADConnect). This causes an issue during the migration where we try to mail-enable the Public Folders, and because the mail-enabled attribute already exists in the Destination, we simply add on to what is already there and add a new email address, but with a '1' appended to the end. This causes unexpected confusion for the User.
In order to resolve this issue, perform the following steps:
- Disable DirSync.
- Connect to the Destination Office 365 tenant with PowerShell.
- Remove the recipient objects for the mail-enabled Public Folders.
Get-MailPublicFolder -ResultSize Unlimited | Remove-SyncMailPublicFolder
- Make sure that all mail-enabled Public Folder recipient objects have been removed; the results should be 0.
Get-MailPublicFolder -ResultSize Unlimited
- Go to the migration project and reset the migration statistics.
- Start a Full migration. This should detect that the mail-enabled Public Folder objects are not present and attempt to create them.
- Once migration completes, verify that everything is correct for the mail-enabled Public Folders.