06-13-2017 06:39 PM
06-13-2017 06:39 PM
What is the recommended way to create shared mailboxes for a hybrid environment? There are some issues if you create them directly to O365 - https://support.microsoft.com/en-us/help/3129334/users-in-a-hybrid-deployment-can-t-access-a-shared-...
Create it onpremises then migrate it to O365 is the best practice?
06-13-2017 11:01 PM
If you still have mailboxes on-premises and would like to have access to your shared mailboxes you should create on-premises and then migrate to Office 365.
06-13-2017 11:10 PM
My mailbox is already migrated to O365 from a while a go, but tonight I tested creating to shared mailboxes. One directly on the cloud and the other on-premises (then migrated), after applying the full access permissions on both for my account only the second one is working (including auto mapping)
I was expecting that for both shared mailboxes to work, but apparently the ones created directly on the cloud have some issues with delegation.
So, I assume that create the shared mailboxes on-premises and then migratem is the best solution even if we have all of our user mailboxes migrated.
06-13-2017 11:15 PMSolution
If you have an Hybrid, your autodiscover is pointing to your on-premises Exchange. If you create your Mailbox only in Cloud, your AD and Exchange does not have any propreties of that mailbox, that is the issue.
06-13-2017 11:21 PM
So, I asume that since AAD Connect does not support write-back (only password) then its better to have the objects created first on-premises then moved to O365 in order to avoud such situations.
Or is there a change that could help on this?
06-13-2017 11:29 PM
You can create some Exchange objects on-premises manually to do that but if the mailbox has no data on it, just create a new one, it's faster.
08-30-2017 12:23 AM
What Nuno says is correct, but when you have migrated everything with the hyrbid your autodiscover will propably point towards Office 365 and you exchange hybrid server is just a exchange server for managing purposes. When this is the case the best thing to do is create the shared mailboxes online (just cloud only).
But if you still have users onprem and maybe some online then the method nuno told is the way to go. Also make sure the proxyaddress have firstname.lastname@example.org (this is used for the automapping).
10-31-2017 06:34 AM
The method that works for me is:
1) create a user mailbox in OnPrem Exchange
2) move the user mailbox to office 365
3) Once move is completed, Convert to shared mailbox (either through EAC or EXO PS using set-mailbox -type shared cmd)
4) remove license as it is no longer needed for shared mailbox
5) Assign mailbox delegation to required users
This ensures the mailbox is known between both Exchange onprem and Exchange online realms and doesn't bypass the federation if it's created in the cloud originally. The only Exchange objects that should be recreated in the cloud for a hybrid deployment are DDGs since they can't sync through AAD Connect. Every other EX object should always be created in onprem realm and then synced to EXO via AAD Connect.
12-18-2017 09:15 AM
Other way is creating the Shared Mailbox in On-prem and then migrate it to O365.
This will leave a contact in On-prem (for compatibility for non-migrated users) and the Shared Mailbox will live in O365.
12-19-2017 05:50 AM
12-21-2017 03:23 PM
02-05-2018 08:38 AM
02-05-2018 11:20 PM
We have Hybrid.
We always create user and mailbox on prem then migrate to O365 .
We do this both for regular an shared mailbox.
Never had a problem.
In case regular mailbox is in o365 and needs to be converted to shared mailbox.
We migrate is to onprem convert to shared with the command and then migrate it back to O365.
Dont know if there is any other option?
Would be nice just to convert in O365 !
02-06-2018 01:52 AM
You can convert in Office 365 the shared mailbox on the Exchange Admin Center or Exchange Online Powershell.
You do not need to migrate the mailbox to on-premises.
02-06-2018 01:56 AM
Are you shure that wont give any problems.
We dont have AD write back to onprem...
So i asume just login to exchange online and stet mailbox shared with powershell ?
02-06-2018 02:51 AM
If you do not have AD write back the process is what you describe. Here is the support article with information https://support.microsoft.com/en-us/help/2710029/shared-mailboxes-are-unexpectedly-converted-to-user...
02-06-2018 04:11 AM
I had some hope ...
07-31-2018 07:49 AM
Hello None None,
I have a couple of question regarding your post. Your method for shared mailboxes in Hybrid environment.
Please, let me know at your earliest convenience.
08-06-2018 11:51 PM
Thanks for these instructions.
Used them when I already had the shared mailbox created on the cloud and synced to on-premises AD.
Just ran the powershell command in the exchange console, changed the attributes and ran a delta sync cycle.
08-07-2018 07:25 AM
1. Yes, you can if you have a Exchange 2013 or Exchange 2016 server in your hybrid environment that can create mailboxes straight from the EAC GUI. When you choose new Mailbox, there is an option for Office 365 mailbox, and then choose mailbox type Shared.
You can also use the enable-remote mailbox cmdlet in EMS with the new updates to EX 2013 and 2016 so that it creates a remote shared mailbox right away in the cloud without changing Attributes in AD. refer to https://support.microsoft.com/en-us/help/4133605/cmdlets-to-create-modify-remote-shared-mailbox-in-o...
Exchange 2010 will require either performing the method i mentioned in my previous post or enabling a user remote mailbox from on-prem, changing to shared in EXO, then updating the attributes in AD so that it doesn't change back to a user mailbox. Refer to Draper's response above.
2. Your second question was answered by your third question. Any bulk creation of an Exchange object will require a CSV file fed into EMS or EXO powershell.
3, I don't have a CSV file on hand, but you can find one easily online. Performed a google search and found this. https://gallery.technet.microsoft.com/How-to-Bulk-create-6be6c82f
hope this helps.
09-19-2018 03:33 PM
One thing to add to this: can you just use this command:
New-Remotemailbox email@example.com -Remoteroutingaddress test@.mail.onmicrosoft.com -Shared
I realize that would create a new user account and a new mailbox, is there a reason why the above command should be used? Or am I missing something with that command?
08-29-2019 03:54 AM
I have CU21, In ECP i have option to create user, room and equipment mailbox but not shared mailbox
In Shell option is available.
How we can get shared mailbox option in ECP or GUI