Forum Discussion
Create shared mailbox on Hybrid environment - directly on O365 or onpremises then migrate it to O365
Hi Carlos,
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.
Hi Carlos,
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.
Hi Nuno,
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.
Hi Carlos,
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.
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 sharedbox@domain.mail.onmicrosoft.com (this is used for the automapping).
- Hi Jerry,
All our mailboxes are on O365. But we habd AD and DirSync with Exchange 2010 and just add 2016. So how do i create shared room and equipment mailbox?
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?
Regards
Hi Carlos,
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.
