Exchange Connection Problems

Fix Exchange Online Mailbox Conversion Errors for Shared Mailboxes

Huda Qurayshi Oct 21, 2026 868 views

Question details

The user is unable to convert a user mailbox to a shared mailbox via the new Exchange admin center or PowerShell.

How to Fix Exchange Online Mailbox Conversion Errors for Shared Mailboxes

Product: Exchange Online
Device & OS: not provided
Scenario: Attempting to convert an existing user mailbox to a shared mailbox within a hybrid environment comprising Microsoft 365 and on-premises Active Directory.
Observed behavior: The conversion fails in the new Exchange admin center, and running a Set-Mailbox command in PowerShell returns an error stating the 'type' parameter cannot be found.

Before you start

Ensure you have the Global Administrator or Exchange Administrator role assigned in Microsoft 365, and verify that your Azure AD Connect synchronization is functioning properly without errors.

Solution 1Recommended

Use the Correct Exchange Online PowerShell Module

Connecting to the latest Exchange Online PowerShell module ensures that all cmdlets and parameters, including those for mailbox conversion, are recognized properly.

The '-Type' parameter error usually occurs when PowerShell is not correctly connected to the modern ExchangeOnlineManagement module, or when a conflicting on-premises module is loaded.

Install or Update the Exchange Online Module

Open PowerShell as an Administrator and run 'Install-Module -Name ExchangeOnlineManagement -Force' to ensure you have the latest version.

Connect to Exchange Online

Run the command 'Connect-ExchangeOnline -UserPrincipalName youradmin@domain.com' and log in with your Global Administrator credentials.

Execute the Conversion Command

Run 'Set-Mailbox -Identity user@domain.com -Type Shared'. If the command is accepted, check the Exchange admin center to confirm the conversion.

Use the Correct Exchange Online PowerShell Module

Hybrid Environment Behavior: In a hybrid setup, sometimes the command succeeds in the background but takes a while to reflect in the UI. If it works without changes later, it may be due to backend sync delays.

Solution 2

Perform the Conversion from On-Premises Active Directory

For hybrid environments, mailboxes originating from on-premises Active Directory should be converted on-premises and synced to the cloud.

Free Microsoft Office alternative

Manage Your Office Documents Seamlessly with WPS Office

While resolving complex Microsoft 365 and Exchange administrative tasks, you can rely on WPS Office for a lightweight, highly compatible alternative for your daily document creation and editing needs.

1. Visit the Official Website: Navigate to the WPS Office website to access the secure download.
2. Download the Installer: Click the 'Free Download' button to get the correct version for your operating system.
3. Install and Open: Run the installer, open WPS Office, and seamlessly load your existing Microsoft Office files.

Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint).Lightweight installation that preserves system resources and runs smoothly.Familiar, tabbed user interface allowing for a seamless transition with zero learning curve.Completely free to download and use for all fundamental productivity tasks.

microsoft office alternative - wps office

Frequently Asked Questions

Why does PowerShell say the '-Type' parameter cannot be found?

This error typically occurs if you are running an outdated PowerShell module, if the session timed out, or if you are accidentally connected to a local Active Directory module instead of the ExchangeOnlineManagement module.

Can I convert a synced user mailbox directly in Microsoft 365?

In many hybrid environments, properties of synced accounts are managed on-premises. Attempting to modify them directly in the Microsoft 365 Exchange admin center may result in errors or sync overwrites. It is best practice to manage these attributes on your local Exchange server.

How long does a mailbox conversion take to appear in the Exchange admin center?

In cloud-only environments, changes usually appear within a few minutes. In hybrid environments, you may need to wait for the Azure AD Connect sync cycle to run (typically every 30 minutes) before the updated status reflects online.

Outlook & Email Problems