Add a switch to the Enable-RemoteMailbox command on Hybrid servers for Remote Shared Mailboxes
Customers with Hybrid server can link the on-prem AD users and rooms to their matching Office 365 mailboxes using the Enable-RemoteMailbox shell command. There is currently no switch to do the same with Shared Mailboxes. Please add a -Shared switch so that this same process can be used to link the remote shared mailboxes.
Seriously ridiculous that this has not been addressed. There is no technical reason for this to still be an issue.
Jeremy Bradshaw commented
Still only 174 votes. I don't understand. At least please tell us why this is possible for Room/Equipment mailboxes but not Shared mailboxes. What is the difference that merits Shared mailboxes being left out from this capability.
Has this process improved at all?
I support this idea.
This is a ridiculous situation and that the Exchange Team has left it this way for so many years now is almost unbelievable. Let's get it fixed!
Any updates on if this suggestion will be seriously considered?
IT should just be another option for the -Type switch... there is already -Type Room and -Type Equipment, so there should be a -Type Shared. Room and Equipment mailboxes are just sub-types of Shared mailboxes. Also, not just the PowerShell, but fix the EAC to handle the proper mechanisms for new mailboxes with existing users for all mailbox types. You require an on-premises Exchange server to exist if you're doing directory synchronization, why not add the features that less skilled customers can benefit from?
Patrick Alphonso commented
I cannot beleive why this still doesn't exist. Why do we have to create mailboxes on premise and then migrate them eludes me completely. Yes, it can be scripted but I don't like fixing things with scripts when I beleive it should be there to start with.
Terry Munro commented
C'mon Microsoft. I am currently creating scripts to automate creation of Hybrid RemoteMailboxes and discovered that the official process from Microsoft is to create a local shared mailbox and then migrate.
How is this supposed to happen in a Hybrid Environment with CAS only servers (no local MBX servers) ?
Please add this functionality.
Jeremy Bradshaw commented
+1 for this. It is vital. I would at least like to see the clear explanation for why it is not possible already. There must be some reason. What is it?
Chase Roth commented
This definitely needs to be done. My goodness, I just went to set up a Shared mailbox and the switch was missing! I couldn't believe it. -Equipment and -Room are there, but not -Shared ...CRAZY! Now I have to do the dance Juho mentioned, as you can't flip to a Shared mailbox in O365 or it will revert back. See Microsoft article: https://support.microsoft.com/en-us/help/2710029/shared-mailboxes-are-unexpectedly-converted-to-user-mailboxes-after-directory-synchronization-runs-in-an-exchange-hybrid-deployment
Juho Lehto commented
I am responsible for producing automation tools for our clients and this is one of the major stumbling points in our automation tools.
Up until now we've had following process:
1) Create a new mailbox to on-premises Exchange with New-Mailbox-cmdlet and Shared-switch.
2) Manually run Directory Syncronization and wait for the user to appear in the cloud.
3) Start a move request from on-premises to Office 365 with New-MoveRequest-cmdlet.
4) Wait for the move request to complete and then remove the move request.
Can I just say that while this process works, it takes unnecessarily long to complete compared to creating equipment and room mailboxes straight with New-RemoteMailbox-cmdlet.
Our Office 365 project people decided that with the switch to the new AADS, we no longer could manually run directory synchronization. This threw a major wrench into creating shared mailboxes, which is pretty much the only thing that requires manual synchronization to work as a part of process automation,
The only option here is to add additional monitoring process to see when user object has been synced to the cloud and then start and finish the move request. Even if shared mailboxes were to be created as resource mailboxes, they still need to be changed to shared mailboxes after user and mailbox objects have been synced to the cloud.
It is unbelievable that not even Exchange 2016 has Shared-switch for New-RemoteMailbox cmdlet. Can you pretty please do something about this and update Exchange 2010-2016 cmdlets accordingly.