Update 09/15/2016: We have removed the content of this blog post because the relevant content has now been migrated to TechNet. Please go here for the latest information on this subject.
one: Do not only takeover the SMTP address(es), also take over the "old" LegacyExchangeDN as X400 Alias address to the new mailbox (leave that LegacyDN as is). This will suppress NDR messages when other users who wrote to that deleted mailbox before and/or
have that mailbox in their contacts folder.
What happens to the soft deleted mailbox after the New-MailboxRestoreRequest cmdlet is run? Is it empty? Could it be merged again to another mailbox?
What about RMS protected messages ?
the non-existing recipient. Would be great to see documented guidelines on that as well as part of this updated approach. Thanks!
your corrupted, damaged, deleted, inaccessible etc EDB files. Try its DEMO Version from here: -
- It didn't failed when I have tried to merge the same soft deleted mailbox to another mailbox
- You must add -AllowLegacyDNMismatch if you merge to a new account
New-MailboxRestoreRequest : The term 'New-MailboxRestoreRequest' is not recognized as the name of a cmdlet, function. I am a global admin with Organization Management permission.
have identity provisioning conflicts and other issues arise where this function is invaluable. Having to merge mailboxes rather than just reattaching them is less desirable in these cases. Does the exchange online team have any plans to allow a soft deleted
mailbox to just be 'attached' to another user rather than merged? Either that or return some similar functionality like Get-RemovedMailbox? How are we to deal with mailboxes that are removed after a Remove-MSOLUser -RemoveFromReycleBin?