Forum Discussion
The question nobody dares to ask! How do you create a new user in a hybrid environment.
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.
You al have some very good answers but the question still is what is best practice. i have done al the scenarios and they al work. But what is the difference between these to options
Create user and mailbox onprem sync user and migrate ,mailbox to o365 assign license
or
Create user sync user to o365 and assign license.
I think the only difference is that when you migrate the mailbox you can migrate it back to onprem when you have a Hybrid. But i am not sure if that is still relevant when you are in Exchange online.
Remember this involves a new user so no legacy mailboxes or anything like that.
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.
Yup, there is no "best" way, you could aim for "fastest" or what works for your requirements. All road lead to rome in this case :)
Paul Cunningham wrote: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.
For the latter, wouldn't that skip the creation of the AD user for the shared mailbox? Sure one might ask why have it.
Martin Meraner wrote:
Paul Cunningham wrote: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.
For the latter, wouldn't that skip the creation of the AD user for the shared mailbox? Sure one might ask why have it.
No. Either New-RemoteMailbox, wait, then convert to Shared in the cloud. Or New-Mailbox with -Shared, and then move to the cloud.
Either way, there's still a user object in AD.
