Forum Discussion
The question nobody dares to ask! How do you create a new user in a hybrid environment.
- Mar 20, 2017
The best practice is whatever works for your user management workflows. You can create it either way. In a hybrid you can move mailboxes back and forth whether they were created on-prem or in the cloud.
One caveat with New-RemoteMailbox is that it can't do Shared mailboxes. Those you need to create on-prem and then move, or, create in EXO as a user mailbox and then convert to Shared. Either way, same result.
Ivan54 wrote:It gets easier to understand once you've done the hybrid setup ;) Exchange 2013 CU15 hybrid in my case:
Once you've done the hybrid setup, you simply get a new UI option in the exchange admin center (onPrem) under recipients > mailboxes > New Office 365 Mailbox.
Thats it.
Thanks a lot! (edit) apparently I was not aware of that option at the time I wrote the script.
Its good to see that this question isn't really that stupid :).
What i do is the following, i use create user in onprem and mailbox onprem migrate it to office365 and assign license when the customer is gonna use the hybrid server for Maintanance and administration.
When a customer is planning to go all the way to the cloud i use create user sync user assign license. With the assumption the Exchange on-prem environment will be cleaned up.
- Paul CunninghamMar 21, 2017Steel Contributor
Jerry Meyer wrote:When a customer is planning to go all the way to the cloud i use create user sync user assign license. With the assumption the Exchange on-prem environment will be cleaned up.
Your question (and thread title) are about hybrid deployments, which means directory sync is in place + an on-prem Exchange server. What is this second scenario you're throwing into the mix where Exchange will be "cleaned up"?
Keep in mind that with directory sync in place, an on-prem Exchange server is required for managing mail attributes in a supported manner, even without the hybrid configuration.
- Jerry MeyerMar 21, 2017Iron Contributor
O i did not know that. I thought that the Serviceaccounts from the AzureADsync are managing the the writeback from Exchangeonline.
Its just an idea on how to manage users and mailboxes it is not an real customer case at this moment. We have one customer who wants to clean up there onprem Exchange but thats a different topic i think.
- Martin MeranerMar 21, 2017Brass Contributor
Hi,
I would have a follow up question. If I use the New-RemoteMailbox command instead of migrating the user, I see as a difference that the on-premise recipient gets no X500,x500 address, the exchange guid is 00000000-0000-0000-00000000 and the ExchangeVersion is lower (compared to a migrated user). Does that have any consequence if I move the online mailbox back to on-premise (say for insufficient license count)?
The Get-RemoteMailbox address information does also not list x500 addresses, but if I do get-mailbox on O365 online, then I get as said before an X500 entry (uppercase only and as said different OU).
Best
Martin