After a BitTitan cutover, are you confirming that delegates can access shared mailboxes in the destination tenant, or are you assuming Full Access permissions came across automatically?

BitTitan migrates the contents of shared mailboxes from source to destination. Delegate permissions such as Full Access and Send As that exist in the source tenant do not automatically apply to the destination shared mailbox after migration.

To avoid access gaps, configure destination shared mailbox permissions before cutover. The approach is: create the shared mailbox in the destination tenant, assign Exchange Online Full Access permissions to every delegate using destination user accounts, and verify the assignments are in place before the BitTitan migration jobs run for that shared mailbox.

Finding out after cutover that 15 users cannot access a shared mailbox because destination permissions were not set becomes a Hyper Care issue that is completely avoidable. Setting permissions takes about 10 minutes per shared mailbox. Fixing it afterward means updating permissions, waiting for Exchange Online permission propagation, and then validating access for each affected delegate.

If a shared mailbox has a large number of delegates, validate the destination permission setup during the pilot before running the full project.

Are you pre-configuring destination shared mailbox delegate permissions in the destination tenant before your BitTitan cutover runs?

#BitTitan #MigrationWiz