If you set up a public folder migration the same way you set up mailbox migrations, you may run straight into EWS access denied errors. In MigrationWiz, public folder migration uses a different endpoint configuration than standard mailbox jobs.

For Exchange Online public folder sources, the endpoint must bind to the public folder hierarchy mailbox specifically, not the typical user mailbox EWS endpoint used for mailbox migrations. The source endpoint authenticates to the EWS URL associated with that hierarchy mailbox.

Permissions are different as well. The migration service account needs explicit Full Access to the public folder hierarchy mailbox in Exchange Online. ApplicationImpersonation by itself does not grant public folder access. These are separate RBAC assignments and both must be in place for endpoint validation.

The most common failure pattern is reusing the Exchange Online endpoint that works for user mailbox migrations, pointing the public folder project at it, and then receiving an access denied error. In that situation, the credentials are valid. The missing piece is the RBAC assignment required for public folder hierarchy access.

On the destination side, MigrationWiz supports migrating public folders either to shared mailboxes or to modern Exchange Online public folders. Choose the destination object type before you build the project, because the user mapping configuration is different depending on which option you select.

Are you using a dedicated endpoint that targets the public folder hierarchy mailbox and includes Full Access rights for your MigrationWiz public folder migration?

#BitTitan #MigrationWiz