Reuse a Deleted User’s UPN and Email Address in Microsoft 365 on Litigation Hold
Question details
Determine whether a new Microsoft 365 user can reuse a former employee’s UPN and email address while the former mailbox remains on Litigation Hold.

- Product
- Microsoft 365, Exchange Online, and Microsoft Purview eDiscovery
- Device & OS
- not provided
- Scenario
- An organization wants to assign a former employee’s sign-in name and email address to a new user without losing access to preserved mailbox data.
- Observed behavior
- The former mailbox needs to remain preserved and distinguishable from the new mailbox in compliance searches.
Confirm that the former mailbox is inactive and preserved by the applicable hold, and check whether the UPN and email address are available. Have an Exchange or compliance administrator record the former mailbox’s Exchange GUID before assigning the identifiers to the new user.
Reuse the UPN and Address After Verifying the Inactive Mailbox
Use this approach when the former mailbox is preserved as an inactive mailbox and the sign-in name and email address are available for reassignment.
Litigation Hold preserves mailbox content, but it does not permanently reserve the former user’s UPN or email address. The inactive mailbox and the new mailbox are separate mailboxes with different Exchange GUIDs.
An address cannot be assigned to two active mail-enabled recipients. If an assignment fails, investigate any existing or soft-deleted object that still holds the identifier before proceeding.
In Exchange Online PowerShell, run Get-Mailbox -InactiveMailboxOnly and identify the former employee’s inactive mailbox. Record its display name, primary SMTP address, Exchange GUID, and other identifying details.
In the Microsoft 365 admin center, check Users > Active users for the intended sign-in name. In the Exchange admin center, check Recipients for an active recipient using the email address; resolve any conflicting assignment before reuse.
In the Microsoft 365 admin center, go to Users > Active users and select Add a user, or select an existing user to update their username. Assign the available email address to the new mailbox through the Exchange admin center.
In Exchange Online PowerShell, run Get-Mailbox -Identity <new-user-UPN> | Format-List DisplayName,PrimarySmtpAddress,ExchangeGuid. Compare and document the new Exchange GUID alongside the former inactive mailbox’s GUID and the date of the transition.

Distinguish the Mailboxes in Microsoft Purview eDiscovery
Use recorded mailbox identities and search criteria to review historical and new-user data without relying on the reused address alone.
Document Mailbox Transitions With WPS Office
WPS Office is a free, lightweight alternative for preparing transition records and review notes in a familiar interface. It supports common Microsoft Office formats for an easier move between applications, but it does not manage Exchange Litigation Hold or Microsoft Purview eDiscovery.

Frequently Asked Questions
Can a new user have the same email address as an inactive mailbox?
Generally, yes. Litigation Hold preserves the former mailbox’s data without permanently reserving its email address. Check the Exchange admin center for active recipient conflicts before assigning the address to the new mailbox.
How can I tell the old and new mailboxes apart?
Record each mailbox’s Exchange GUID. Use Get-Mailbox -InactiveMailboxOnly in Exchange Online PowerShell to identify the former inactive mailbox, and Get-Mailbox -Identity <new-user-UPN> to inspect the new mailbox.
Will a date filter alone separate the mailboxes in eDiscovery?
No. A date filter narrows content but does not confirm the search location. In Microsoft Purview eDiscovery, verify the selected Exchange locations and review result or export metadata against your mailbox records.
What should I do if Microsoft 365 says the UPN or address is already in use?
Check Users > Active users in the Microsoft 365 admin center and Recipients in the Exchange admin center for a conflicting assignment. Also investigate relevant soft-deleted objects before retrying the assignment.




