In-Place Restore: Exchange
An in-place Exchange restore writes a backed-up email message back into a live mailbox folder, and the target mailbox does not have to be the one the message was originally backed up from.
What an in-place Exchange restore does
An in-place Exchange restore takes a single backed-up message and posts it into a specified mailbox and folder as a new message.
You choose the message to restore, then choose the destination mailbox and folder. The restore is queued and runs in the background, and BYOVault reports back when it completes or fails.
Cross-mailbox restore is real, not a special mode
The target mailbox and folder are not derived from the backed-up message’s original location. They are independent choices you make when starting the restore.
In the operator dashboard, the restore dialog pre-fills the target mailbox with the original mailbox as a convenience default, but this field is editable — any other mailbox in the tenant can be chosen instead before submitting the restore.
This is how you recover a departed or renamed user’s mail into a different, still-active mailbox: back up the departed user’s mailbox as normal, then restore individual messages into a manager’s or replacement employee’s mailbox instead of the original one.
The destination folder is selected from a fixed list in the operator dashboard, and defaults to Inbox:
- Inbox
- Sent Items
- Drafts
- Deleted Items
- Archive
This selection, too, is independent of the folder the message originally lived in at backup time; a message backed up from a custom or deeply-nested folder can be restored into any of these five well-known folders in the target mailbox.
What is restored, and what is not
Restoring a message creates a new message in the destination folder. Sender, recipients, subject, body, timestamps, and flags are all preserved.
Read-only system fields — such as the message’s original ID or its original parent folder — are not carried over, since these are assigned fresh by Exchange when the new message is created.
The restored message has a new message ID; it does not overwrite or resurrect the original message even if that original still exists in its source mailbox.
Restoring a specific version
Exchange messages are backed up the same way files are: each backup run that captures a changed copy of a message keeps it as its own independent version, so multiple versions of the same item can exist. Exchange-inject restores whichever version you select, with no assumption that the most recent one is what you want. The version to restore is chosen upstream in the version browser described in Version History.
Job outcome
A completed job records the new message’s subject and the folder it was restored into. A failed job records the error message directly, and both outcomes trigger the same restore-completion notification, with a status of completed or failed.
Permissions required
Exchange-inject requires the Mail.ReadWrite application permission granted in the customer’s Microsoft 365 tenant, in addition to the Mail.Read permission already required to back mail up. See Restore Permissions & Scopes for the full permission table and what each one actually authorizes.