Others

How to Convert a Synced User Mailbox to a Cloud-Only Shared Mailbox in Exchange

Maira Mehtab Oct 19, 2026 868 views

Question details

The user needs to securely convert a synchronized user mailbox to a shared mailbox in a hybrid Exchange Online environment and make it cloud-only without the mailbox being deleted when the on-premises Active Directory object is removed.

How to Convert a Synced User Mailbox to a Cloud-Only Shared Mailbox in Exchange Online

Product: Exchange Online
Device & OS: not provided
Scenario: Managing user mailboxes and licenses in a hybrid Azure AD Connect environment.
Observed behavior: Deleting the on-premises synchronized user automatically deletes the associated Microsoft 365 user and shared mailbox, moving them to a recoverable state instead of leaving them intact in the cloud.

Before you start

Verify your hybrid recipient configuration and ensure you have Exchange Online PowerShell access and appropriate administrative privileges before making directory changes.

Solution 1Recommended

Convert via PowerShell and Remove from Sync Scope

The safest method to convert the mailbox while preserving it in the cloud is to change its type via PowerShell and carefully remove it from the Azure AD Connect sync scope.

In a hybrid environment, the cloud object's lifecycle is tied to the on-premises Active Directory object. By moving the user out of the synchronization scope instead of deleting it immediately, you can convert the mailbox safely.

Convert to Shared Mailbox

Connect to Exchange Online PowerShell and run the command: Set-Mailbox -Identity user@domain.com -Type Shared.

Remove License

Once the mailbox is converted, remove the Microsoft 365 license from the user account, as standard shared mailboxes do not require one.

Modify Sync Scope

Instead of deleting the on-premises Active Directory object, move the user out of the Azure AD Connect synchronization scope (for example, into an unsynchronized Organizational Unit).

Force Synchronization

Force an Azure AD Connect delta synchronization and verify that the Microsoft Entra object remains active as a cloud-only shared mailbox, retaining its permissions and aliases.

Convert via PowerShell and Remove from Sync Scope

Test Environment First: Always test this process with a non-production account and consult the Exchange Hybrid Management team before altering critical synchronized objects.

Solution 2

Convert via On-Premises Exchange Migration

If your environment relies heavily on strict on-premises Exchange recipient management, you should manage the conversion through your local server to avoid sync mismatches.

Free Microsoft Office alternative

Boost Your Team's Productivity with WPS Office

While you manage your Exchange Online and Microsoft 365 hybrid environments, consider equipping your team with WPS Office. It's a lightweight, highly compatible alternative to Microsoft Office that provides robust document, spreadsheet, and presentation tools without the heavy subscription costs.

1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
2. Install the Software: Run the setup file and follow the quick on-screen instructions to complete the lightweight installation.
3. Open Your Documents: Launch WPS Office and immediately start opening and editing your existing Microsoft Office files with perfect compatibility.

Seamlessly open, edit, and save Microsoft Word, Excel, and PowerPoint file formats to maintain workflow continuity.Free to download and use with a highly familiar user interface, ensuring zero learning curve for your team.Lightweight installation that runs smoothly on both modern and legacy hardware.Built-in PDF editing tools for comprehensive document management alongside your email workflows.

microsoft office alternative - wps office

Frequently Asked Questions

Do I need to assign a license to a shared mailbox in Exchange Online?

Generally, shared mailboxes in Exchange Online do not require a separate license if they are under 50 GB. However, if the mailbox exceeds this size or requires in-place archiving features, an Exchange Online Plan 2 license must be assigned.

Why did my shared mailbox disappear when I deleted the local Active Directory user?

In a hybrid environment using Azure AD Connect, the cloud object's lifecycle is directly tied to the on-premises Active Directory object. Deleting the local user signals Azure AD to delete the synchronized cloud identity, which subsequently soft-deletes the associated shared mailbox.

Can I simply convert the mailbox in the Microsoft 365 admin center?

In a strict hybrid setup, converting the mailbox only in the Microsoft 365 admin center can lead to synchronization issues. The on-premises environment will still recognize the account as a regular user mailbox, which is why it's recommended to use Exchange Online PowerShell or perform an on-premises conversion.

Office Quick Solutions