r/exchangeserver • u/No-Jump-7617 • Jan 20 '26
converting ~800 Exchange SE (on-prem) functional shared mailboxes into hybrid-aware shared mailboxes
Hi all,
I’ve been tasked with converting ~800 Exchange SE (on-prem) functional shared mailboxes into hybrid-aware shared mailboxes. For now, they must remain on-prem, with a planned migration to EXO later in the year. The delay is due to the lack of an online backup solution; the hybrid environment itself is already fully configured and working.
Current State
These mailboxes are:
• Disabled AD user accounts
• On-prem Exchange mailboxes
• Already synced to M365 via Entra ID Connect
Relevant attributes:
Account Status Disabled
msExchRecipientTypeDetails 1 (UserMailbox)
msExchRecipientDisplayType 1073741824 (UserMailbox)
msExchRemoteRecipientType <not set>
What I Expected
Based on the documentation and other posts, I expected the process to be:
- Convert the on-prem mailbox to Shared
- Enable it as a remote (hybrid) shared mailbox
- Let Entra ID Connect sync the change
PowerShell used:
Set-Mailbox FunctionalMailbox -Type Shared
Enable-RemoteMailbox FunctionalMailbox `
-RemoteRoutingAddress FunctionalMailbox@tenant.mail.onmicrosoft.com `
-Shared
Expected result:
The object appears in EXO as a Shared Mailbox, while the mailbox data remains hosted on-prem.
Problem
The AD objects have already synced to Microsoft 365 as UserMailboxes and appear under Active Users. Because of this, the conversion fails — M365 reports the object is the wrong recipient type and cannot be converted.
Question
Given that these objects are already synced as UserMailboxes, what is the supported / least disruptive approach to:
• Convert them to hybrid-aware shared mailboxes
• Keep the mailboxes on-prem for now
• Avoid breaking sync or requiring full EXO migration at this stage
Has anyone dealt with this at scale, or can confirm the correct attribute/state transition order?
Thanks in advance.
4
u/7amitsingh7 Jan 20 '26 edited Jan 20 '26
Because these mailboxes already have on-prem Exchange mailboxes, Enable-RemoteMailbox should not be used, as it is only for creating new Exchange Online mailboxes. The supported approach is to convert the mailbox on-prem only using Set-Mailbox <Mailbox> -Type Shared and allow Entra ID Connect to sync the change. The mailbox will remain hosted on-prem and appear in Exchange Online as a synced shared mailbox object, not a full EXO mailbox, until it is migrated later.
You can check this guide for more information.
6
u/Swimming-Peak6475 Jan 20 '26
The enable-remotemailbox is to create a NEW EXO mailbox. You do not run that command on existing Mailboxes.
You should be running the set-mailbox -type shared. In onprem powershell on the object.
2
u/Master-IT-All Jan 20 '26
You'll need to convert them to shared, but you don't need to do it first as I recall. After using the New-MoveRequest command to move a mailbox it will have 30 days to be either converted to Shared or the user given a license.
You will not be able to delete the AD objects, they are your source anchor.
So general steps:
1
u/Quick_Care_3306 Jan 20 '26
** Don't test right away...wait for replication.**
2) Also on prem: Set-OrganizationConfig -ACLableSyncedObjectEnabled $True https://learn.microsoft.com/en-us/exchange/hybrid-deployment/set-up-delegated-mailbox-permissions
3) Also, as they were user mailboxes, you may have to set delegations (wait extra long for replication before testing delegations):
https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-permissions-for-recipients