How to Assign a Mailbox to a Different User in Exchange Online: Practical Step-by-Step Guide

Assign a mailbox to a different user in Exchange Online requires choosing the right method (granting access, converting to a shared mailbox, or migrating content) and following careful steps to preserve compliance, aliases, and permissions. This guide explains the options, gives step-by-step commands and UI actions, and includes a checklist and practical tips for a smooth transition.

Method overview: When to assign vs. delegate vs. migrate

Choosing how to assign a mailbox depends on business needs. Granting Full Access or Exchange Online mailbox delegation keeps the original mailbox intact and gives another user access. Converting to a shared mailbox is appropriate when no dedicated license should be used by the original account. Reassigning mailbox content to a different user (reassign mailbox Office 365) is a migration-style operation used when a new owner must permanently inherit messages and folders.

assign a mailbox to a different user in Exchange Online — step-by-step methods

Method A: Grant Full Access (fast, reversible)

Best when the original mailbox must remain addressable and the new user needs access.

1. Open Exchange admin center (EAC) or connect via Exchange Online PowerShell.
2. Using PowerShell (recommended for repeatability):

Connect-ExchangeOnline
Add-MailboxPermission -Identity "[email protected]" -User "[email protected]" -AccessRights FullAccess -InheritanceType All

Optionally add Send As permission if the new user must send as the mailbox:

Add-RecipientPermission -Identity "[email protected]" -Trustee "[email protected]" -AccessRights SendAs

Method B: Convert mailbox to Shared (license-saving)

Convert the former user mailbox to a shared mailbox and assign Full Access to the new user. Shared mailboxes do not require a license if size and features meet limits.

1. In EAC: Recipients > Mailboxes > Select mailbox > Convert to shared mailbox.
2. Or PowerShell: Set-Mailbox -Identity "[email protected]" -Type Shared
3. Grant access to the new user as in Method A.

Method C: Migrate mailbox content to a new user (permanent reassignment)

Use this when the mailbox must permanently belong to another account. Options include using eDiscovery > Content search export/import, or PST export/import. This method preserves messages under the target user’s mailbox rather than leaving the original mailbox accessible.

1. Use Compliance Center content search to export mailbox items and import into the new user's mailbox, or use third-party migration tools where permitted.
2. Verify aliases and primary SMTP addresses. Update proxyAddresses and mail attributes as needed.

MAILBOX-REASSIGN Checklist (named framework)

1. Verify ownership, retention and legal hold (preserve evidence for compliance).
2. Confirm mail flow (ensure SMTP addresses, accepted domains are retained).
3. Choose method: delegate, shared conversion, or migrate content.
4. Execute permissions changes or migration during low-impact window.
5. Test access, send/receive, and remove old user license if appropriate.

Short real-world example

Scenario: An employee ([email protected]) leaves and a replacement ([email protected]) must access the mailbox. The organization wants to avoid issuing a license to alice but keep the mailbox accessible. Solution: convert alice’s mailbox to shared and grant bob Full Access.

Commands (Exchange Online PowerShell):

Connect-ExchangeOnline
Set-Mailbox -Identity "[email protected]" -Type Shared
Add-MailboxPermission -Identity "[email protected]" -User "[email protected]" -AccessRights FullAccess -InheritanceType All

Then confirm Bob can open the mailbox in Outlook and send on behalf or send as if required.

Practical tips

• Verify any Litigation Hold, Legal Hold, or eDiscovery holds before removing a mailbox or changing ownership—these settings affect retention and compliance.
• Check proxyAddresses and primarySMTPAddress to avoid breaking mail flow when changing ownership or transferring addresses.
• Use Exchange Online PowerShell (Connect-ExchangeOnline) for repeatable, auditable changes in scripts.
• Document each change in ticketing or change-control systems and test access from a real client (Outlook/OWA).

Trade-offs and common mistakes

Trade-offs

• Granting Full Access is quick and reversible but leaves the original mailbox intact (may be undesired if permanent reassignment is required).
• Converting to a shared mailbox saves a license but shared mailboxes have storage and feature limits and cannot be directly logged into like a user mailbox.
• Migrating content provides a clean ownership transfer but is more labor-intensive and can affect folder permissions and message metadata in some cases.

Common mistakes

• Not checking for holds or retention policies before removing or converting mailboxes.
• Assuming Automapping will always behave as expected; automapping may cause many mailboxes to appear in a user's Outlook and can be disabled by setting Automapping to $false when granting permissions.
• Failing to update address lists, distribution groups, or shared calendars tied to the old mailbox.

Core cluster questions

• How to grant someone Full Access to another mailbox in Exchange Online?
• When should a mailbox be converted to a shared mailbox in Office 365?
• What are the steps to migrate mailbox data between users in Exchange Online?
• How do retention holds affect reassigning or deleting mailboxes?
• How to avoid automapping many mailboxes after granting permissions?

Key references

For official guidance on mailbox permissions and recipient management, consult Microsoft documentation: Exchange Online - Manage mailbox permissions.

Testing and verification

After any change, verify that the new user can open the mailbox in Outlook Web Access (OWA) and that send/receive behavior is correct. Confirm that aliases continue to receive email, and run a quick message trace if mail flow problems appear.

Rollback and auditing

Keep a rollback plan: record PowerShell commands run (or export current settings before making changes). Use the Microsoft 365 Compliance Center audit logs and the Azure AD sign-in logs to review access. Revoke permissions with Remove-MailboxPermission and reassign types with Set-Mailbox as needed.

Additional considerations

When planning to move or reassign mailboxes, consider identity sources (cloud-only vs. Azure AD Connect), group memberships, and whether SMTP address reassignment will affect external systems. If the environment is hybrid (on-prem Exchange + Exchange Online), follow hybrid mailbox guidance and coordinate with Active Directory changes.

FAQ: How can I assign a mailbox to a different user in Exchange Online?

Three main approaches: grant Full Access (delegate), convert the mailbox to a shared mailbox and assign access, or migrate content into another user mailbox. The right approach depends on licensing, compliance, and whether the change must be permanent. Use PowerShell (Add-MailboxPermission, Set-Mailbox) or the Exchange admin center for UI-driven steps.

FAQ: How does Exchange Online mailbox delegation differ from converting to a shared mailbox?

Delegation (Full Access) keeps the mailbox as a user mailbox and simply grants another account access; conversion to a shared mailbox changes the mailbox type so it can often be license-free and is intended for team-managed mailboxes. Delegation is reversible; conversion changes mailbox behavior and storage limits.

FAQ: What permissions are required to reassign mailbox content?

A role with recipient management and compliance privileges is required. For PowerShell operations, the account must be assigned appropriate Exchange roles (e.g., Mail Recipients, Organization Management) and be able to access Compliance Center features for exports.

FAQ: How to avoid automapping when granting Full Access?

Use the PowerShell parameter when adding permissions via Add-MailboxPermission combined with a full Add-MailboxPermission plus setting the user's mailbox to not automap in the user's mailbox configuration (or use Add-MailboxPermission then set the target mailbox's permissions with a specific Delegate option). Alternatively, add permissions via Add-MailboxPermission and configure Outlook to manually open the mailbox.

FAQ: What should be checked before reassigning a mailbox?

Confirm legal holds, retention policies, shared resource links, aliases, licensing implications, and whether the mailbox is hybrid-managed. Back up or export critical data if necessary and document the change for compliance and troubleshooting.